December 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-3640) Some standard SQL functions are not implemented in Sybase

by Juraci Paixao Krohling (JIRA)

Some standard SQL functions are not implemented in Sybase --------------------------------------------------------- Key: HHH-3640 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3640 Project: Hibernate Core Issue Type: Improvement Components: testsuite Environment: Sybase ASE 15.0.2 Reporter: Juraci Paixao Krohling Assignee: Juraci Paixao Krohling Attachments: ASTParserLoadingTest.java.diff Some standard SQL functions are not implemented in Sybase, like "mod" * , bit_length, trim. Thus, the tests which uses these functions needs to be evicted. ASTParserLoadingTest, contains "trim(trailing '_' column) ... " , mod(x,y) and bit_length -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

2
10
0 / 0

[Hibernate-JIRA] Created: (HHH-3599) Materializing proxy fails non-deterministic with "[-4000] (at 10): Unknown result table"

by Dirk Lachowski (JIRA)

Materializing proxy fails non-deterministic with "[-4000] (at 10): Unknown result table" ---------------------------------------------------------------------------------------- Key: HHH-3599 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3599 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.3.1 Environment: MaxDB 7.6.05.09, Linux, JDBC Reporter: Dirk Lachowski We have a quite simple domain object: @Entity @Table(name = "cc_user_assignment") @org.hibernate.annotations.Proxy(lazy = true) public class CostCenterUserAssignment { private Long id; private Contact contact; private Set<CostCenter> costCenter = new HashSet<CostCenter>(); private CostCenter defaultCostCenter; @ManyToMany @JoinTable(name = "j_cc_user2user", joinColumns = { @JoinColumn(name = "user_assignment_id") }, inverseJoinColumns = @JoinColumn(name = "cost_center_id")) public Set<CostCenter> getCostCenter() { return costCenter; } public void removeCostCenter(CostCenter ccRemove) { costCenter.remove(ccRemove); } } Most of the time the call to "removeCostCenter()" succeeds, but now we have a non-reproducible situation where the call to costCenter.remove(ccRemove) fails. It seems to be data-dependend as it occurs in one of our productive systems. There it is reproducible for one set of data. First we thought it is dependent on the data-size but we are not able to reproduce it by simply creating another dataset of the same size. The select created for the proxy-materializing is: select costcenter0_.user_assignment_id as user1_10_, costcenter0_.cost_center_id as cost2_10_, costcenter1_.id as id169_0_, costcenter1_.accountNumber as accountN2_169_0_, costcenter1_.balance as balance169_0_, costcenter1_.balance_currency as balance4_169_0_, costcenter1_.budget as budget169_0_, costcenter1_.budget_currency as budget6_169_0_, costcenter1_.budgetExcessAllowed as budgetEx7_169_0_, costcenter1_.bdg_extra as bdg8_169_0_, costcenter1_.bdg_extra_currency as bdg9_169_0_, costcenter1_.budgetPeriod as budgetP10_169_0_, costcenter1_.customer_id as customer13_169_0_, costcenter1_.manager_id as manager14_169_0_, costcenter1_.name as name169_0_, costcenter1_.transferBudget as transfe12_169_0_, customer2_.id as id167_1_, customer2_.accountId as accountId167_1_, customer2_.addr_id as addr16_167_1_, customer2_.attribute01 as attribute3_167_1_, customer2_.attribute02 as attribute4_167_1_, customer2_.attribute03 as attribute5_167_1_, customer2_.attribute04 as attribute6_167_1_, customer2_.attribute05 as attribute7_167_1_, customer2_.attribute06 as attribute8_167_1_, customer2_.attribute07 as attribute9_167_1_, customer2_.attribute08 as attribute10_167_1_, customer2_.attribute09 as attribute11_167_1_, customer2_.attribute10 as attribute12_167_1_, customer2_.delivery_lock_id as delivery17_167_1_, customer2_.externalAccountId1 as externa13_167_1_, customer2_.externalAccountId2 as externa14_167_1_, customer2_.owner_id as owner18_167_1_, customer2_.pricelist_id as pricelist19_167_1_, customer2_.pricingSchemaName as pricing15_167_1_, address3_.id as id165_2_, address3_.city as city165_2_, address3_.country_id as country16_165_2_, address3_.fax as fax165_2_, address3_.fon as fon165_2_, address3_.houseNumber as houseNum5_165_2_, address3_.mail as mail165_2_, address3_.name1 as name7_165_2_, address3_.name2 as name8_165_2_, address3_.name3 as name9_165_2_, address3_.name4 as name10_165_2_, address3_.postbox as postbox165_2_, address3_.postcode as postcode165_2_, address3_.postcodeCompany as postcod13_165_2_, address3_.postcodePostbox as postcod14_165_2_, address3_.street as street165_2_, address3_.title_id as title17_165_2_, country4_.id as id159_3_, country4_.isoCode as isoCode159_3_, country4_.name as name159_3_, title5_.id as id163_4_, title5_.isOrganization as isOrgani2_163_4_, title5_.name as name163_4_, deliverylo6_.id as id191_5_, deliverylo6_.autoDeliveryLock as autoDeli2_191_5_, deliverylo6_.description as descript3_191_5_, deliverylo6_.messageLock as messageL4_191_5_, deliverylo6_.name as name191_5_, deliverylo6_.orderLock as orderLock191_5_, deliverylo6_.reservationLock as reservat7_191_5_, pricelistt7_.id as id175_6_, pricelistt7_.description as descript2_175_6_, pricelistt7_.name as name175_6_, contact8_.id as id166_7_, contact8_.customer_id as customer12_166_7_, contact8_.firstName as firstName166_7_, contact8_.ignoreAssortment as ignoreAs3_166_7_, contact8_.lastName as lastName166_7_, contact8_.officeFax as officeFax166_7_, contact8_.officeMail as officeMail166_7_, contact8_.officeMobile as officeMo7_166_7_, contact8_.officePhone as officePh8_166_7_, contact8_.role as role166_7_, contact8_.title_id as title13_166_7_, contact8_.webPassword as webPass10_166_7_, contact8_.webUserName as webUser11_166_7_, customer9_.id as id167_8_, customer9_.accountId as accountId167_8_, customer9_.addr_id as addr16_167_8_, customer9_.attribute01 as attribute3_167_8_, customer9_.attribute02 as attribute4_167_8_, customer9_.attribute03 as attribute5_167_8_, customer9_.attribute04 as attribute6_167_8_, customer9_.attribute05 as attribute7_167_8_, customer9_.attribute06 as attribute8_167_8_, customer9_.attribute07 as attribute9_167_8_, customer9_.attribute08 as attribute10_167_8_, customer9_.attribute09 as attribute11_167_8_, customer9_.attribute10 as attribute12_167_8_, customer9_.delivery_lock_id as delivery17_167_8_, customer9_.externalAccountId1 as externa13_167_8_, customer9_.externalAccountId2 as externa14_167_8_, customer9_.owner_id as owner18_167_8_, customer9_.pricelist_id as pricelist19_167_8_, customer9_.pricingSchemaName as pricing15_167_8_, title10_.id as id163_9_, title10_.isOrganization as isOrgani2_163_9_, title10_.name as name163_9_ from j_cc_user2user costcenter0_, cost_center costcenter1_, KNA1 customer2_, ADDR address3_, C005 country4_, CSAD3 title5_, delivery_lock deliverylo6_, sd_pr_prltype pricelistt7_, KNVK contact8_, KNA1 customer9_, CSAD3 title10_ where costcenter0_.cost_center_id=costcenter1_.id(+) and costcenter1_.customer_id=customer2_.id(+) and customer2_.addr_id=address3_.id(+) and address3_.country_id=country4_.id(+) and address3_.title_id=title5_.id(+) and customer2_.delivery_lock_id=deliverylo6_.id(+) and customer2_.pricelist_id=pricelistt7_.id(+) and costcenter1_.manager_id=contact8_.id(+) and contact8_.customer_id=customer9_.id(+) and contact8_.title_id=title10_.id(+) and costcenter0_.user_assignment_id=? The same query can be successfully submitted using database studio. Maybe it's related to this: http://osdir.com/ml/db.maxdb/2004-10/msg00199.html A full stack trace is available here: http://jira.lacho.net/jira/browse/ES-579 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3650) TableGenerator doesn't marks the "primary key" as not null, causing errors in some RDBMS's which expects the PK to be not-null

by Juraci Paixao Krohling (JIRA)

TableGenerator doesn't marks the "primary key" as not null, causing errors in some RDBMS's which expects the PK to be not-null ------------------------------------------------------------------------------------------------------------------------------ Key: HHH-3650 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3650 Project: Hibernate Core Issue Type: Patch Components: core Environment: DB2v82 and Branch_3_3 and trunk Reporter: Juraci Paixao Krohling Assignee: Juraci Paixao Krohling Attachments: TableGenerator.java.diff Some RDBMS's requires that the primary key columns be not-null. This causes some tests which relies on the org.hibernate.id.enhanced.TableGenerator to fail on error. The attached patch adds the string "not null" to the table creation statement. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

2
7
0 / 0

[Hibernate-JIRA] Created: (HHH-3275) Allow pluggable tuplizers for composite elements

by Chris Bredesen (JIRA)

Allow pluggable tuplizers for composite elements ------------------------------------------------ Key: HHH-3275 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3275 Project: Hibernate3 Issue Type: Improvement Components: metamodel Reporter: Chris Bredesen Priority: Minor By looking at the hibernate-mapping DTD, it does not seem possible to define a tuplizer for a composite-element. However, composite elements have component semantics, so if Hibernate allows pluggable tuplizer for components, one would expect the same thing about composite elements. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

4
14
0 / 0

[Hibernate-JIRA] Created: (HHH-3607) Adding primary key to TableGenerator causes problem on DB2

by Neale Swinnerton (JIRA)

Adding primary key to TableGenerator causes problem on DB2 ---------------------------------------------------------- Key: HHH-3607 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3607 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1 Environment: hibernate 3.3.1.GA, Database server = DB2/LINUXX8664 9.1.5 Reporter: Neale Swinnerton Attachments: not-null.patch The change made in HHH-2686 to add a primary key to the generator table doesn't work on DB2, because there isn't a not null clause on the primary key column. attached patch adds the not null clause. I believe this should be portable across all DBs? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3438) Could not check JTA transaction; nested exception is java.lang.StackOverflowError

by Jara Cesnek (JIRA)

Could not check JTA transaction; nested exception is java.lang.StackOverflowError --------------------------------------------------------------------------------- Key: HHH-3438 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3438 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.3.0.GA Reporter: Jara Cesnek This code cause infinite loop. Moreover still dont work with JOTM. HHH-3358 protected UserTransaction *getUserTransaction*() { log.trace( "Attempting to locate UserTransaction via JNDI [{}]", getUserTransactionName() ); try { UserTransaction ut = ( UserTransaction ) getInitialContext().lookup( getUserTransactionName() ); if ( ut == null ) { throw new TransactionException( "Naming service lookup for UserTransaction returned null [" + getUserTransactionName() +"]" ); } log.trace( "Obtained UserTransaction" ); return ut; } catch ( NamingException ne ) { throw new TransactionException( "Could not find UserTransaction in JNDI [" + *getUserTransaction()* + "]", ne ); } } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

4
4
0 / 0

[Hibernate-JIRA] Created: (BVAL-69) The default MessageResolver now handles Locale

by Emmanuel Bernard (JIRA)

The default MessageResolver now handles Locale ---------------------------------------------- Key: BVAL-69 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-69 Project: Bean Validation Issue Type: New Feature Components: ri-general Reporter: Emmanuel Bernard Fix For: 1.0 public draft This is not the case of the actual implementation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-2921) Polymorphic query breaks if entity proxy already exists in session

by Johan Hoogenboezem (JIRA)

Polymorphic query breaks if entity proxy already exists in session ------------------------------------------------------------------ Key: HHH-2921 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2921 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.5 Environment: 3.2.5, PostgreSQL 8.1.2, jdk1.5.0_08, Windows XP Reporter: Johan Hoogenboezem I posted to the user forum about this on Oct 26 (http://forum.hibernate.org/viewtopic.php?t=980752). I've had no reply. This is a serious hassle for me, so I submit it as a bug. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HBX-1091) Cannot open with Hibernate 3.0 XML Editor in Eclipse

by sbgoh (JIRA)

Cannot open with Hibernate 3.0 XML Editor in Eclipse ---------------------------------------------------- Key: HBX-1091 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1091 Project: Hibernate Tools Issue Type: Task Components: eclipse Affects Versions: 3.2.cr1 Environment: Hibernate version: 3.0 Database platform: Oracle 9i Reporter: sbgoh Hi, I have include the hibernate tools plugins in Eclipse 3.3.2. However, I can't open the map file (.hbm.xml) with Hibernate 3.0 XML Editor. Is there any other settings required to activate this editor? Thanks in advance. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HBX-770) Consider integration/union between Eclipse Dali and Hibernate Tools

by Diego Pires Plentz (JIRA)

Consider integration/union between Eclipse Dali and Hibernate Tools ------------------------------------------------------------------- Key: HBX-770 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-770 Project: Hibernate Tools Type: Improvement Reporter: Diego Pires Plentz What about? Consider integration/union between Eclipse Dali and Hibernate Tools. An official Hibernate project, fully integrated with an oficial Eclipse project. http://www.eclipse.org/dali/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues December 2008