March 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Closed: (HHH-1052) Allow CalendarType.set to accept Date objects

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1052?page=c... ] Steve Ebersole closed HHH-1052. ------------------------------- Closing stale resolved issues > Allow CalendarType.set to accept Date objects > --------------------------------------------- > > Key: HHH-1052 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1052 > Project: Hibernate Core > Issue Type: Improvement > Components: core > Affects Versions: 3.1 rc 1 > Environment: Hibernate 3.1RC1, MySQL 4.1, Windows XP > Reporter: Adam Greene > Priority: Minor > Original Estimate: 5m > Remaining Estimate: 5m > > CalendarType.set expects only Calendar objects as input. But when you are building Criterias with complex requirements, you many times use a Calendar object to do the calculations, and it would be nice to be able to pass Calendar.getTime() (which returns java.util.Date) to the Restrictions methods, because otherwise you end up passing the same Calendar object two seperate calls and you change the values in between calls, resulting in possible unexpected behaviour. > Example (though a bit contrived does show what I am talking about): > Calendar startcal = Calendar.getInstance(); > Calendar endcal = Calendar.getInstance(); > startcal.set(Calendar.DAY_OF_MONTH, 1); > endcal.set(Calendar.DAY_OF_MONTH, 10); > Criterion startin = Restrictions.between("start", startcal, endcal); > startcal.set(Calendar.DAY_OF_MONTH, 10); > endcal.set(Calendar.DAY_OF_MONTH, 30); > Criterion endin = Restrictions.between("end", startcal, endcal); > This might cause unexpected behaviour, but : > Criterion startin = Restrictions.between("start", startcal.getTime(), endcal.getTime()); > startcal.set(Calendar.DAY_OF_MONTH, 10); > endcal.set(Calendar.DAY_OF_MONTH, 30); > Criterion endin = Restrictions.between("end", startcal.getTime(), endcal.getTime()); > would not cause problems. -- 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, 1 month

1
0
0 / 0

[Hibernate-JIRA] Closed: (HHH-1121) CLONE -Oracle 10G: Could not locate TransactionManager

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1121?page=c... ] Steve Ebersole closed HHH-1121. ------------------------------- Closing stale resolved issues > CLONE -Oracle 10G: Could not locate TransactionManager > ------------------------------------------------------ > > Key: HHH-1121 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1121 > Project: Hibernate Core > Issue Type: Improvement > Environment: Oracle App Server (Orion based) > Reporter: Steve Ebersole > Priority: Minor > > The current OrionTransactionManagerLookup, shipped with Hibernate, indicates that the transaction manager is published at JNDI namespace 'java:comp/UserTransaction'. This was the case for OC4J 903 - 904 but Oracle changed the location in OC4J 10G. The new (and hidden) location is available in the uploaded OC4JTransactionManagerLookup class which have been succesfully tested on OC4J 903, 904 and 10G. > Cheers. > PS: please email me if I can contribute to your project. My expertise is EJB3 (EntityManager) and Oracle App Server. -- 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, 1 month

1
0
0 / 0

[Hibernate-JIRA] Closed: (HHH-1019) Native SQL return-property mapping doesn't support dot-syntax in return-property for components

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1019?page=c... ] Steve Ebersole closed HHH-1019. ------------------------------- Closing stale resolved issues > Native SQL return-property mapping doesn't support dot-syntax in return-property for components > ----------------------------------------------------------------------------------------------- > > Key: HHH-1019 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1019 > Project: Hibernate Core > Issue Type: Improvement > Components: core > Reporter: Christian Bauer > Assignee: Emmanuel Bernard > Priority: Blocker > Fix For: 3.1.1 > > > This is a SQL/SP mapping: > <return-property name="billingAddress.street" column="BILLING_STREET"/> > It refers to a property in a <join> table: > <join table="BILLING_ADDRESS" optional="true"> > <key column="USER_ID"/> > <component name="billingAddress" class="Address"> > <property name="street" > type="string" > column="STREET" > length="255"/> > ... > Calling/loading with this SQL mapping fails, as Hibernate always tries to use "STREET" with the resultset instead of "BILLING_STREET". -- 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, 1 month

1
0
0 / 0

[Hibernate-JIRA] Closed: (HBX-313) hibernate tools stuck when retrieving data from database after adding/removing mapping properties

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-313?page=co... ] Steve Ebersole closed HBX-313. ------------------------------ Closing stale resolved issues > hibernate tools stuck when retrieving data from database after adding/removing mapping properties > ------------------------------------------------------------------------------------------------- > > Key: HBX-313 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-313 > Project: Hibernate Tools > Issue Type: Bug > Affects Versions: 3.0alpha4 > Environment: eclipse 3.1RC3 (plain install, no other plugin than hibernate tools alpha4a), database: CA Ingres 2.6, jdk1.5update3 > Reporter: Patrik Meisinger > Fix For: 3.1alpha5 > > > there's a problem when adding/removing mapping properties to the mapping file (sometable.hbm.xml). > the hibernate tools stuck when i do the following steps: > (i assume that a java project and a java-file representing a table in the db exists in eclipse) > 1. create a hibernate-configuration file using the hibernate-tools-wizard (right click on the eclipse project->new->other->hibernate config file) > 2. create a hibernate-mapping-file for out of an empty xml-file (eclipse: file->new->file somefile.hbm.xml) > 3. add some properties and an id to the mapping file (save the file) > 4. create a hibernate console configuratin using the hibernate-tools-wizard (right click on the eclipse project->new->other->hibernate console config) with the following data: name is the eclipse project name and classpath with jdbc-driver from ingres and the bin-folder of the project (exact in this order) > 5. switch to hibernate console perspective > 6. right click on console config->create session factory > 7. expand "mapped entities" > 8. double click on the mapped entity to retrieve data from the database > 9. data is now shown in the "query result" view from the hibernate perspective > 10. right click on console config->close session factory > 11. switch back to java perspective and add or remove a property in the somefile.hbm.xml-mapping-file > 12. switch back to hibernate console perspective > 13. right click on console config->create session factory > 14. expand "mapped entities" > 15. double click on the mapped entity to retrieve data from the database. STUCK. you never get a result from the database because something causes eclipse/hibernate-plugin to stuck. > the problem is reproduceable with the steps above: 5 tries out of 5 (even more) > the problem occurs in eclipse 3.1RC2, too. > possible workaround: restarting eclipse after editing the properties, but this is not satisfying. > another problem in this relation is to add a <one-to-one>-mapping instead of adding/removing a property (i haven't tried <one-to-many> at this time). same steps as above except step 11. step 11 in this case is "switch back to java perspective and add a <one-to-one> mapping in the somefile.hbm.xml-mapping-file. > the problem is reproduceable with the steps above: 5 tries out of 5 (even more) > the problem occurs in eclipse 3.1RC2, too. > possible workaround: none known. > regards > patrik -- 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, 1 month

1
0
0 / 0

[Hibernate-JIRA] Closed: (HHH-947) Allow nullable columns in a composite-id

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-947?page=co... ] Steve Ebersole closed HHH-947. ------------------------------ Closing stale resolved issues > Allow nullable columns in a composite-id > ---------------------------------------- > > Key: HHH-947 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-947 > Project: Hibernate Core > Issue Type: Improvement > Components: core > Environment: Hibernate 3.0.5, Oracle 9.2 > Reporter: Patrick Higgins > > We have some tables that don't have a primary key, but do have a unique index with nullable columns in it. This is a conceptually broken data model, but code maintains the semantics that NULL = NULL which the database does not enforce. Mapping these tables with Hibernate 3 does not work because any record with a NULL value in a composite-id field returns a null in query results. I have not looked at INSERT/UPDATE behavior, but it is likely broken, too. > It seems that Hibernate should be able to maintain the semantics that NULL = NULL, as well. -- 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, 1 month

1
0
0 / 0

[Hibernate-JIRA] Closed: (HHH-1073) InformixDialect can't populate inserted serial(4)

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1073?page=c... ] Steve Ebersole closed HHH-1073. ------------------------------- Closing stale resolved issues > InformixDialect can't populate inserted serial(4) > ------------------------------------------------- > > Key: HHH-1073 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1073 > Project: Hibernate Core > Issue Type: Bug > Affects Versions: 3.1 rc2 > Environment: Informix 9.4 UC 3, Hibernate 3 RC2, three seperate informix drivers > Reporter: Dennis C. Byrne > > Informix has serial(4) and serial(8) instead of identity fields. The correct way to get the last assigned id is to fire "select dbinfo('serial8') from systables where tabid=1" after an insert of a serial(8) record, or "select dbinfo('sqlca.sqlerrd1') from systables where tabid=1" from a serial(4) record. > The expression 'type==Types.BIGINT', in InformixDialect.getIdentitySelectString(), will always evaluate to true, regardless of whether the serial field is 4 or 8. Hibernate will consequently use "select dbinfo('serial8') from systables where tabid=1" for both 4 and 8. > We have observed a similar problem w/ third party GIS software. There is another application developed by someone here who has informed me that he does not have this problem, but that application was written in H2. > A workaround for this is to override InformixDialect.getIdentitySelectString() and force it to always return "select dbinfo('sqlca.sqlerrd1') from systables where tabid=1". This however means the app would have errors w/ serial(8). -- 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, 1 month

1
0
0 / 0

[Hibernate-JIRA] Closed: (HHH-1224) Problems with comparator class

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1224?page=c... ] Steve Ebersole closed HHH-1224. ------------------------------- Closing stale resolved issues > Problems with comparator class > ------------------------------ > > Key: HHH-1224 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1224 > Project: Hibernate Core > Issue Type: Bug > Affects Versions: 3.1 rc3 > Environment: MSSQL > Reporter: Zoran Bogatinoski > > The class org.hibernate.mapping.collection, the method getComparator has a bug. The first line: > if(comparator!=null && comparatorClassName!=null) { > ... should be: > if(comparator==null && comparatorClassName!=null) { > Kind Regards, > Zoran Bogatinoski -- 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, 1 month

1
0
0 / 0

[Hibernate-JIRA] Closed: (HHH-1588) delay inserts for insert-generated-identifiers outside transaction

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1588?page=c... ] Steve Ebersole closed HHH-1588. ------------------------------- Closing stale resolved issues > delay inserts for insert-generated-identifiers outside transaction > ------------------------------------------------------------------ > > Key: HHH-1588 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1588 > Project: Hibernate Core > Issue Type: Improvement > Components: core > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Fix For: 3.2.0 cr1 > > > Currently, when an entity with some form of PostInsertIdentifierGenerator key generator (IDENTITY, select) is saved or persisted the insert happens immediately. This is done in order to know the generated id value because the legacy save() method requires it for a return value (plus proper hashing etc within the PersistenceContext). > For EJB3, the persist() method does not dictate the generated id value to be returned and allows the provider to schedule the id-generation and insertion at a later point in time. However, it also requires that when an entity is persist()ed either directly or through cascade outside of a transaction, that the insert needs to be delayed until: > (1) we join a transaction and a normal flush executes the pending actions > (2) an explicit flush occurs -- 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, 1 month

1
0
0 / 0

[Hibernate-JIRA] Closed: (HHH-449) korean hibernate reference manual

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-449?page=co... ] Steve Ebersole closed HHH-449. ------------------------------ Closing stale resolved issues > korean hibernate reference manual > --------------------------------- > > Key: HHH-449 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-449 > Project: Hibernate Core > Issue Type: New Feature > Components: documentation > Affects Versions: 3.0.2 > Reporter: DongGuk Lee > Assignee: Justen Stepka > Fix For: 3.1 rc3 > > Attachments: hibernate3.0.2-reference-doc-kr.zip > > > Hello, this is DongGuk Lee, a Korean developer. > I just translated this reference document into Korean. > I want you to upload this to your homepage. > Could you please do that? > If you do so, many Korean developers will be delighted. -- 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, 1 month

1
0
0 / 0

[Hibernate-JIRA] Closed: (HHH-1160) Incorrect use of getGeneratedKey() for Oracle

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1160?page=c... ] Steve Ebersole closed HHH-1160. ------------------------------- Closing stale resolved issues > Incorrect use of getGeneratedKey() for Oracle > --------------------------------------------- > > Key: HHH-1160 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1160 > Project: Hibernate Core > Issue Type: Bug > Components: core > Environment: Oracle Driver 10.2.0.1.0 > Oracle DB 9.2.0.6.0 > Reporter: Emmanuel Bernard > Assignee: Steve Ebersole > Fix For: 3.1 rc3 > > > The problem is that Oracle's getGeneratedKeys() returns a rowID. This is Oracle's internal unique representation of a row and can not be represented as a long which is why the exception is thrown. This is within the spec for getGeneratedKeys(). To make getGeneratedKeys() work for any database, the PreparedStatement object must be created with the method that takes a String[] of columns to return from getGeneratedKeys(). This is the change that is made in Jira ticket "JBAS-2399" to make getGeneratedKeys() work for Oracle with EJB2.1. -- 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, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues March 2011