May 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-4647) Problems with @JoinColumn referencedColumnName and quoted column and table names

by Peter Brant (JIRA)

Problems with @JoinColumn referencedColumnName and quoted column and table names -------------------------------------------------------------------------------- Key: HHH-4647 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4647 Project: Hibernate Core Issue Type: Bug Components: annotations, core Affects Versions: 3.5.0-Beta-2 Environment: current CVS, not database platform dependent Reporter: Peter Brant Attachments: hibernate-annotations.patch, hibernate-core.patch, test-case.zip There are really two separate issues here, but the test case reduction and patches are so small (and involve related functionality) they are combined. #1: A referencedColumnName that references a quoted target column cannot be found. The test case is app.TestReferencedColumnName#testQuotedReferencedColumnName(). The patch is hibernate-annotations.patch. #2: An invalid referencedColumnName (including the unquoted version of a valid column) results in an infinite loop in o.h.c.Configuration$MappingsImpl#getPhysicalColumnName(). The test case is app.TestReferencedColumnName#testInvalidReferencedColumnNameOnQuotedTable. The patch is hibernate-core.patch. It looks like the same issue exists with getLogicalColumnName(), but I'm not sure where this is used (i.e. how to test it) so I left it alone. -- 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
10
0 / 0

[Hibernate-JIRA] Created: (HHH-3694) ResultTransformer not used when scroll() is used on a named SQLQuery

by Oscar Pearce (JIRA)

ResultTransformer not used when scroll() is used on a named SQLQuery -------------------------------------------------------------------- Key: HHH-3694 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3694 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.3.1 Environment: Hibernate Core 3.3.1, PostgreSQL 8.1, HSQLDB 1.8 Reporter: Oscar Pearce Priority: Minor Attachments: sqlqueryrestrans.zip If a ResultTransformer is set on a named SQLQuery, and then scroll() is used on the query, the ResultTransformer is never used. The unit test in the attached Maven project shows this. The fix seems simple - a one-line change in org.hibernate.loader.custom.CustomLoader#getHolderInstantiator(ResultTransformer resultTransformer, String[] queryReturnAliases). The sense of the test of resultTransformer against null should be reversed. -- 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

5
16
0 / 0

[Hibernate-JIRA] Created: (HHH-5109) @OneToOne - too many joins

by Marek Romanowski (JIRA)

@OneToOne - too many joins -------------------------- Key: HHH-5109 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5109 Project: Hibernate Core Issue Type: Bug Components: annotations, core Affects Versions: 3.5.0-Final Reporter: Marek Romanowski Attachments: hibernate-one-to-one.zip With classes like this: @Entity @Proxy(lazy=false) class Owner { @javax.persistence.Id @javax.persistence.Column(name = "ID", columnDefinition = "BIGINT") public java.lang.Long getId() { return this.id; } public void setId(java.lang.Long newValue) { this.id = newValue; } private java.lang.Long id; @javax.persistence.OneToOne(targetEntity = Owned.class) @org.hibernate.annotations.Cascade( { org.hibernate.annotations.CascadeType.ALL }) @javax.persistence.PrimaryKeyJoinColumn public Owned getOwned() { return this.owned; } public void setOwned(Owned owned) { this.owned = owned; if (owned != null) { owned.setOwner(this); } } private Owned owned; } @Entity @Proxy(lazy=false) class Owned { private java.lang.Long id; @javax.persistence.Id @javax.persistence.GeneratedValue(generator = "foreign") @org.hibernate.annotations.GenericGenerator( name = "foreign", strategy = "foreign", parameters = { @org.hibernate.annotations.Parameter(name = "property", value = "owner") }) @javax.persistence.Column(name = "ID", columnDefinition = "BIGINT") public java.lang.Long getId() { return this.id; } public void setId(java.lang.Long newValue) { this.id = newValue; } @javax.persistence.OneToOne(targetEntity = Owner.class, mappedBy = "owned") @javax.persistence.PrimaryKeyJoinColumn public Owner getOwner() { return this.owner; } public void setOwner(Owner owner) { this.owner = owner; } private Owner owner; } Idea is to have one to one relation between Owner and Owned mapped by "id" properties in both entities. So for each pair owner.id == owned.id. code: session.load(Owner.class, 1L) turns into SQL: select owner0_.ID as ID0_2_, owned1_.ID as ID1_0_, owner2_.ID as ID0_1_ from Owner owner0_ left outer join Owned owned1_ on owner0_.ID=owned1_.ID left outer join Owner owner2_ on owned1_.ID=owner2_.ID where owner0_.ID=? Isn't it wrong? @OneToOne annotation on getOwner() has mappedBy="owned" property, so I would expect this code to generate SQL with only one join (only "owner join owned"). If this is correct H3 behaviour in this case, then write what should I change in annotations to get described behaviour, please. I've attached maven project with one test encapsulating this issue. -- 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
11
0 / 0

[Hibernate-JIRA] Created: (HHH-4440) Support for column-level read/write fragments (Rob Hasselbaum)

by Steve Ebersole (JIRA)

Support for column-level read/write fragments (Rob Hasselbaum) -------------------------------------------------------------- Key: HHH-4440 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4440 Project: Hibernate Core Issue Type: Patch Components: core, metamodel Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.5 -- 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
11
0 / 0

[Hibernate-JIRA] Created: (HHH-3768) Modify the revision entity to include the end-revision number when available

by Adam Warski (JIRA)

Modify the revision entity to include the end-revision number when available ---------------------------------------------------------------------------- Key: HHH-3768 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3768 Project: Hibernate Core Issue Type: Sub-task Components: envers Reporter: Adam Warski Assignee: Adam Warski This includes adding a new annotation and modifying the default revision entity -- 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

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-4086) improving the performance of the object loading in hibernate

by shubha (JIRA)

improving the performance of the object loading in hibernate ------------------------------------------------------------ Key: HHH-4086 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4086 Project: Hibernate Core Issue Type: Task Components: query-hql Affects Versions: 3.2.3 Environment: hibernate 3.2.3 ga, oracle Reporter: shubha Priority: Critical _sessions = SessionFactoryUtil.getSessionFactory(); session = _sessions.openSession(); Query query = session.getNamedQuery(queryName); tx = session.beginTransaction(); results = query.list(); System.out.println(results.size()); tx.commit(); i am trying to get a collection of objects from query.list(). Even though the SQL generated from hibernate runs very fast in oracle, the O/R mapping in case of hibernate is taking lot of time. To fetch around 15 thousand records it takes 8 to 12 minutes. I am using left join fetch on the query -- 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-3909) Improve Performance of FieldInterceptionHandler (and thus of flushing)

by Ovidio Mallo (JIRA)

Improve Performance of FieldInterceptionHandler (and thus of flushing) ---------------------------------------------------------------------- Key: HHH-3909 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3909 Project: Hibernate Core Issue Type: Improvement Components: core Affects Versions: 3.3.1 Reporter: Ovidio Mallo Attachments: patch.txt In the FieldInterceptionHelper class, the method Class#getInterfaces() is used in conjunction with a subsequent loop over all interfaces of an entity class in order to check whether a bytecode instrumentation interface of CGlib or Javassist is found. This is done that way since CGlib and Javassist are both optional so they should only be accessed at runtime if available on the classpath. Attached you can find a simple patch which only once checks whether CGlib and/or Javassist is available and then uses the more performant "instanceof" operator in order to check whether an entity has an interceptor. The new code still guarantees that no CGlib or Javassist class is accessed if it is not on the classpath. The patch helps making the FieldInterceptionHelper methods more performant which can e.g. be noticed during a session flush, especially if bytecode instrumentation is used. In order to measure the performance impact of the patch I've written a simple program which does the following: 1. insert 100 thousand entities into a simple table with 6 numeric attributes 2. do an initial flush on the session in order to execute all the insert statements 3. loop 300 times and do a flush on the session (only a dirty check is performed, no database operation) I've time the flushes under point 3 above with and without bytecode instrumentation for the used entity. Here are the results: USING BYTECODE INSTRUMENTATION ============================= * SUN JVM 1.6.0_05: - without patch: 25734ms - with patch: 11015ms * IBM JVM 1.4.2: - without patch: 20672ms - with patch: 11140ms WITHOUT BYTECODE INSTRUMENTATION ================================ * SUN JVM 1.6.0_05: - without patch: 73328ms - with patch: 62015ms * IBM JVM 1.4.2: - without patch: 70344ms - with patch: 61125ms Using bytecode instrumentation, the performance improvement is about of a factor of 2-2.5. When not using bytecode instrumentation, the overall impact is of course less relevant since the rest of the work done during flush is more expensive anyway. In any case, IMHO the impact when using bytecode instrumentation is relevant. The patch is very simple and only touches the FieldInterceptionHelper class. -- 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
5
0 / 0

[Hibernate-JIRA] Created: (HHH-5185) Columns in Formulas not always rewritten, triggers ambiguous column SQL error

by Chris Wilson (JIRA)

Columns in Formulas not always rewritten, triggers ambiguous column SQL error ----------------------------------------------------------------------------- Key: HHH-5185 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5185 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.1 Environment: MySQL Server version: 5.0.51a-3ubuntu5.5 (Ubuntu) Hibernate version 3.5.1-Final Reporter: Chris Wilson Attachments: HibernateJoinFormulaAliasTest.java The attached test case joins an entity with two @Formulas twice. The first @Formula is the algebraic expression "(kittens * 4) + 3", the second is a SQL function "EXTRACT(MONTH FROM birthday)". kittens is rewritten but birthday is not. Because the table is joined twice, MySQL reports the error: {code} com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Column 'birthday' in field list is ambiguous {code} which shows up as: {code} org.hibernate.exception.ConstraintViolationException: could not load an entity: [org.aptivate.hibernate.test.HibernateJoinFormulaAliasTest$House#1] at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:96) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66) at org.hibernate.loader.Loader.loadEntity(Loader.java:1937) at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:86) at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:76) at org.hibernate.persister.entity.AbstractEntityPersister.load(AbstractEntityPersister.java:3270) at org.hibernate.event.def.DefaultLoadEventListener.loadFromDatasource(DefaultLoadEventListener.java:496) at org.hibernate.event.def.DefaultLoadEventListener.doLoad(DefaultLoadEventListener.java:477) at org.hibernate.event.def.DefaultLoadEventListener.load(DefaultLoadEventListener.java:227) at org.hibernate.event.def.DefaultLoadEventListener.lockAndLoad(DefaultLoadEventListener.java:403) at org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:155) at org.hibernate.impl.SessionImpl.fireLoad(SessionImpl.java:1080) at org.hibernate.impl.SessionImpl.get(SessionImpl.java:1065) at org.hibernate.impl.SessionImpl.get(SessionImpl.java:1056) at org.aptivate.hibernate.test.HibernateJoinFormulaAliasTest.testFailing(HibernateJoinFormulaAliasTest.java:97) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.aptivate.hibernate.test.base.HibernateTestBase.runTestMethod(HibernateTestBase.java:204) at org.aptivate.hibernate.test.base.HibernateTestBase.runTest(HibernateTestBase.java:117) at junit.framework.TestCase.runBare(TestCase.java:130) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:120) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Column 'birthday' in field list is ambiguous at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at com.mysql.jdbc.Util.handleNewInstance(Util.java:409) at com.mysql.jdbc.Util.getInstance(Util.java:384) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1041) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3562) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3494) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1960) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2114) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2696) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2105) at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:2264) at org.hibernate.jdbc.AbstractBatcher.getResultSet(AbstractBatcher.java:208) at org.hibernate.loader.Loader.getResultSet(Loader.java:1849) at org.hibernate.loader.Loader.doQuery(Loader.java:718) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:270) at org.hibernate.loader.Loader.loadEntity(Loader.java:1933) ... 31 more {code} The rewritten SQL is: {code} select hibernatej0_.id as id0_2_, cats1x1_.firstHome_id as firstHome4_0_4_, cats1x1_.id as id4_, cats1x1_.id as id1_0_, cats1x1_.birthday as birthday1_0_, cats1x1_.firstHome_id as firstHome4_1_0_, cats1x1_.kittens as kittens1_0_, cats1x1_.secondHome_id as secondHome5_1_0_, EXTRACT(MONTH FROM birthday) as formula0_0_, (cats1x1_.kittens * 4) + 3 as formula1_0_, cats2x2_.secondHome_id as secondHome5_0_5_, cats2x2_.id as id5_, cats2x2_.id as id1_1_, cats2x2_.birthday as birthday1_1_, cats2x2_.firstHome_id as firstHome4_1_1_, cats2x2_.kittens as kittens1_1_, cats2x2_.secondHome_id as secondHome5_1_1_, EXTRACT(MONTH FROM birthday) as formula0_1_, (cats2x2_.kittens * 4) + 3 as formula1_1_ from houses hibernatej0_ left outer join cats cats1x1_ on hibernatej0_.id=cats1x1_.firstHome_id left outer join cats cats2x2_ on hibernatej0_.id=cats2x2_.secondHome_id where hibernatej0_.id=? {code} There's no apparent workaround that lets us reference the same column in a formula in a table that's joined twice. -- 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
6
0 / 0

[Hibernate-JIRA] Created: (HHH-2339) merge instumented class fails

by Alexey Romanchuk (JIRA)

merge instumented class fails ----------------------------- Key: HHH-2339 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2339 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.1, 3.2.0.ga Environment: Hibernate 3.2.1 (tested with 3.2.0 too) Postgresql 8.1.4 Reporter: Alexey Romanchuk Priority: Blocker When we try to merge instrumented detached entity with lazy no-proxy many-to-one association we have org.hibernate.LazyInitializationException. It occurs because cascade try to process all associations in Cascade class, but object disconected from session and can not obtaion lazy property. If classes are not instrumented all works ok. Why merge action does not have overrided performOnLazyProperty mathod to prevent fetching lazy properties? Here it is small example that illustates problem. ===MAPPING=== <hibernate-mapping> <class name="Client" table="test_client"> <id name="id" column="id" type="long"> <generator class="sequence"> <param name="sequence">test_seq</param> </generator> </id> <property name="name" column="name"/> <many-to-one name="info" class="LoginInfo" lazy="no-proxy" column="info_id" cascade="merge,evict"/> </class> <class name="LoginInfo" table="test_login_info"> <id name="id" column="id" type="long"> <generator class="sequence"> <param name="sequence">test_seq</param> </generator> </id> <property name="login" column="login"/> <property name="pass" column="pass"/> </class> </hibernate-mapping> ===JAVA=== ===DOMAIN=== public class Client { private long id; private String name; private LoginInfo info; //getters and setters } public class LoginInfo { private long id; private String login; private String pass; //getters and setters } ===USAGE=== public class Main { public static void main( String[] args ) { Session s1 = sf.openSession(); s1.beginTransaction(); Client c = ( Client ) s1.get( Client.class, 2l ); s1.flush(); s1.getTransaction().commit(); s1.close(); Session s2 = sf.openSession(); s2.beginTransaction(); c = ( Client ) s2.merge( c ); s2.flush(); s2.getTransaction().commit(); s2.close(); } } ==STACKTRACE=== org.hibernate.LazyInitializationException: session is not connected at org.hibernate.intercept.AbstractFieldInterceptor.intercept(AbstractFieldInterceptor.java:67) at org.hibernate.intercept.cglib.FieldInterceptorImpl.readObject(FieldInterceptorImpl.java:75) at Client.$cglib_read_info(Client.java) at Client.getInfo(Client.java:12) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.hibernate.property.BasicPropertyAccessor$BasicGetter.get(BasicPropertyAccessor.java:145) at org.hibernate.tuple.entity.AbstractEntityTuplizer.getPropertyValue(AbstractEntityTuplizer.java:277) at org.hibernate.persister.entity.AbstractEntityPersister.getPropertyValue(AbstractEntityPersister.java:3529) at org.hibernate.engine.Cascade.cascade(Cascade.java:130) at org.hibernate.event.def.DefaultMergeEventListener.cascadeOnMerge(DefaultMergeEventListener.java:407) at org.hibernate.event.def.DefaultMergeEventListener.entityIsDetached(DefaultMergeEventListener.java:266) at org.hibernate.event.def.DefaultMergeEventListener.onMerge(DefaultMergeEventListener.java:120) at org.hibernate.event.def.DefaultMergeEventListener.onMerge(DefaultMergeEventListener.java:53) at org.hibernate.impl.SessionImpl.fireMerge(SessionImpl.java:677) at org.hibernate.impl.SessionImpl.merge(SessionImpl.java:661) at org.hibernate.impl.SessionImpl.merge(SessionImpl.java:665) at Main.main(Main.java:56) -- 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: (HHH-2388) Insert w/ identity column fails on Sybase but no exception occurs

by Tim Morrow (JIRA)

Insert w/ identity column fails on Sybase but no exception occurs ----------------------------------------------------------------- Key: HHH-2388 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2388 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.1 Environment: Hibernate 3.2.1.GA with annotations Sybase jConnect 6.05 JDBC driver Sybase ASE 15 database Reporter: Tim Morrow I have a scenario where storing a new entity fails (i.e. the row is not inserted) but Hibernate does not realize this. No exceptions are thrown. Later, this leads to AssertionFailures (if two such entities fail in the same session - they both have the same PK). The problem specifically occurs with a table that has a numeric column with precision (e.g. numeric(10,4)) and an identity column when using Sybase ASE. ========== To reproduce: 1. Use Sybase jConnect 6.05 JDBC driver with Sybase ASE 15 database. 2. Define an Entity with a long ID and BigDecimal numeric column. 3. Create a corresponding table with an identity column and numeric(10, 4) column. For example: hibernate.MyEntity.java: ----------------------------------------- package hibernate; import java.math.BigDecimal; import javax.persistence.Column; import javax.persistence.Entity; import javax.persistence.GeneratedValue; import javax.persistence.GenerationType; import javax.persistence.Id; import javax.persistence.Table; import org.hibernate.validator.NotNull; @Entity @Table(name = "z_tim_test") public class MyEntity { private BigDecimal cost; private long id; public MyEntity() {} @Column(columnDefinition = "numeric(10,4)") @NotNull public final BigDecimal getCost() { return cost; } @GeneratedValue(strategy = GenerationType.AUTO) @Id public final long getId() { return id; } public final void setCost(BigDecimal cost) { this.cost = cost; } public final void setId(long id) { this.id = id; } } Table: ----------------------------------------- CREATE TABLE z_tim_test ( id numeric(19) PRIMARY KEY not null, cost numeric(10,4) not null ); 4. Write some code that stores a new entity and tries to load it: MyEntity myEntity = new MyEntity(); myEntity.setCost(new BigDecimal("123.12345")); session.save(myEntity); session.flush(); session.clear(); List<MyEntity> results = session.createCriteria(MyEntity.class).list(); if (results.size() != 1) { throw new IllegalStateException("Expected 1 result"); } This test will throw the IllegalStateException because the row was not persisted and no errors occurred. Reason: * Sybase does not thrown any SQLException when you try and persist a numeric value whose scale exceeds that defined on the column. Instead, it returns an updateCount of zero and an identity column value of zero. * Hibernate does not check the updateCount after executing the statement when using an Identity column. The offending code is in: org.hibernate.id.IdentityGenerator$InsertSelectDelegate public Serializable executeAndExtract(PreparedStatement insert) throws SQLException { if ( !insert.execute() ) { while ( !insert.getMoreResults() && insert.getUpdateCount() != -1 ) { // do nothing until we hit the rsult set containing the generated id } } ResultSet rs = insert.getResultSet(); try { return IdentifierGeneratorFactory.getGeneratedIdentity( rs, persister.getIdentifierType() ); } finally { rs.close(); } } It ignores the updateCount. The net result is that the object is assigned a PK value of zero. Hibernate continues. My applicaiton is unaware that the row failed to insert. Solution: It would seem to me replacing the above code with: if (!insert.execute()) { if (insert.getUpdateCount() < 1) { throw new HibernateException("No update occurred"); } while (!insert.getMoreResults()) { // do nothing until we hit the rsult set containing the generated id } } Would take care of the problem? -- 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

8
19
0 / 0

[Hibernate-JIRA] Created: (HHH-5229) org.hibernate.test.hql.ScrollableCollectionFetchingTest.testScrollingJoinFetchesEmptyResultSet() fails on sybase

by Strong Liu (JIRA)

org.hibernate.test.hql.ScrollableCollectionFetchingTest.testScrollingJoinFetchesEmptyResultSet() fails on sybase ---------------------------------------------------------------------------------------------------------------- Key: HHH-5229 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5229 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.2, 3.5.1 Reporter: Strong Liu Assignee: Strong Liu Fix For: 3.5.x, 3.6 {quote} Result set is IDLE as you are not currently accessing a row. Description: The application has called one of the ResultSet.getXXX column-data retrieval methods, but there is no current row; the application has not called ResultSet.next(), or ResultSet.next() returned "false" to indicate that there is no data. Action: Check that rs.next() is set to "true" before calling rs.getXXX. {quote} org.hibernate.exception.GenericJDBCException: could not perform sequential read of results (forward) at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:126) at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:114) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66) at org.hibernate.loader.Loader.loadSequentialRowsForward(Loader.java:420) at org.hibernate.impl.FetchingScrollableResultsImpl.next(FetchingScrollableResultsImpl.java:83) at org.hibernate.test.hql.ScrollableCollectionFetchingTest.testScrollingJoinFetchesEmptyResultSet(ScrollableCollectionFetchingTest.java:67) Caused by: java.sql.SQLException: JZ0R1: Result set is IDLE as you are not currently accessing a row. at com.sybase.jdbc3.jdbc.ErrorMessage.raiseError(Unknown Source) at com.sybase.jdbc3.jdbc.SybResultSet.checkIfReadableRow(Unknown Source) at com.sybase.jdbc3.jdbc.SybResultSet.getColumn(Unknown Source) at com.sybase.jdbc3.jdbc.SybResultSet.getLong(Unknown Source) at com.sybase.jdbc3.jdbc.SybResultSet.getLong(Unknown Source) at org.hibernate.type.LongType.get(LongType.java:51) at org.hibernate.type.NullableType.nullSafeGet(NullableType.java:184) at org.hibernate.type.NullableType.nullSafeGet(NullableType.java:173) at org.hibernate.loader.Loader.getKeyFromResultSet(Loader.java:1120) at org.hibernate.loader.Loader.loadSequentialRowsForward(Loader.java:409) ... 31 more -- 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-3624) DialectFactory needs DB2/NT64 adding to the MAPPERS Map

by mike wray (JIRA)

DialectFactory needs DB2/NT64 adding to the MAPPERS Map ------------------------------------------------------- Key: HHH-3624 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3624 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.3.1 Reporter: mike wray Priority: Minor DialectFactory needs DB2/NT64 adding to the MAPPERS Map. ie MAPPERS.put( "DB2/NT64", new VersionInsensitiveMapper( "org.hibernate.dialect.DB2Dialect" ) ); -- 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

5
6
0 / 0

[Hibernate-JIRA] Created: (HBX-1119) Hibernate tools tasks(hbm2java) generates info logs as standard error logs (shows red in eclipse) instead of standard out

by vivek meghanathan (JIRA)

Hibernate tools tasks(hbm2java) generates info logs as standard error logs (shows red in eclipse) instead of standard out ------------------------------------------------------------------------------------------------------------------------- Key: HBX-1119 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1119 Project: Hibernate Tools Issue Type: Bug Components: hbm2java Affects Versions: 3.2.0.GA Environment: Hibernate 3.2.0 GA Reporter: vivek meghanathan Hibernate tools tasks(hbm2java) generates info logs as standard error logs (shows red in eclipse) instead of standard out. Please have a look. -- 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, 11 months

1
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3475) Support not-found="ignore" for <any> mappings

by Felix Gnass (JIRA)

Support not-found="ignore" for <any> mappings --------------------------------------------- Key: HHH-3475 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3475 Project: Hibernate Core Issue Type: Improvement Components: core Affects Versions: 3.3.0.SP1 Reporter: Felix Gnass Priority: Minor It would be useful if the <any> element would support the not-found="ignore|exception" setting. Due to the nature of any-mappings it's impossible to use on-delete cascades at the database layer, so it's very likely that ObjectNotFoundExceptions occur. Currently the only work-around to gracefully handle such situations seems to be the implementation of a custom EntityNotFoundDelegate that doesn't throw an exception. -- 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, 11 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-4474) NullPointerException in AuditEventListener#generateBidirectionalCollectionChangeWorkUnits onPostInsert...

by Daniel Bleisteiner (JIRA)

NullPointerException in AuditEventListener#generateBidirectionalCollectionChangeWorkUnits onPostInsert... --------------------------------------------------------------------------------------------------------- Key: HHH-4474 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4474 Project: Hibernate Core Issue Type: Bug Components: envers Environment: <version>1.2.0.GA-hibernate-3.3</version> Reporter: Daniel Bleisteiner Attachments: stacktrace.txt I get the exception attached as file after creating an entity. The mapping works on my development machine... a test server throws that exception. I've tried to search for eny differences in the tables but can't find any so far. The last time a similar error occured I was missing the versioned entry in the version table - these have been filled with the lowest revision available (the same way on my machine as on the test server). So I'm stuck... I have no access to the related source either... maybe this would help! -- 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, 11 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3992) SQLServer "contains" boolean predicate not handled in HQL

by Scott Van Wart (JIRA)

SQLServer "contains" boolean predicate not handled in HQL --------------------------------------------------------- Key: HHH-3992 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3992 Project: Hibernate Core Issue Type: Improvement Components: query-hql Affects Versions: 3.3.2, 3.3.1 Environment: Hibernate core 3.3.1, JDK 1.6, SQLServer 2003 Reporter: Scott Van Wart The following HQL: select pp from Product pp where CONTAINS( pp.keywords, :keywords ) Will throw this exception: org.hibernate.hql.ast.QuerySyntaxException: unexpected AST node: ( near line 1, column 33 [select pp from Product pp where CONTAINS( pp.keywords, :keywords )] at org.hibernate.hql.ast.QuerySyntaxException.convert(QuerySyntaxException.java:54) at org.hibernate.hql.ast.QuerySyntaxException.convert(QuerySyntaxException.java:47) at org.hibernate.hql.ast.ErrorCounter.throwQueryException(ErrorCounter.java:82) at org.hibernate.hql.ast.QueryTranslatorImpl.analyze(QueryTranslatorImpl.java:258) at org.hibernate.hql.ast.QueryTranslatorImpl.doCompile(QueryTranslatorImpl.java:183) at org.hibernate.hql.ast.QueryTranslatorImpl.compile(QueryTranslatorImpl.java:134) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:101) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:80) at org.hibernate.engine.query.QueryPlanCache.getHQLQueryPlan(QueryPlanCache.java:94) at org.hibernate.impl.AbstractSessionImpl.getHQLQueryPlan(AbstractSessionImpl.java:156) at org.hibernate.impl.AbstractSessionImpl.createQuery(AbstractSessionImpl.java:135) at org.hibernate.impl.SessionImpl.createQuery(SessionImpl.java:1650) I tried changing it to this: select pp from Product pp where CONTAINS( pp.keywords, :keywords ) = TRUE But then SQL Server doesn't like it (it produces SQL like "CONTAINS(pkgproduct0_.keywords, ?)=1": org.hibernate.exception.SQLGrammarException: could not execute query using scroll Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax near '='. -- 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, 11 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3002) database field name 'version' causes ClassCastException while building session factory

by Patrick Burke (JIRA)

database field name 'version' causes ClassCastException while building session factory -------------------------------------------------------------------------------------- Key: HHH-3002 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3002 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.5 Environment: Hibernate 3.2.5, Java 1.6.0_03, MySQL 5.0.41 Reporter: Patrick Burke Attachments: out.hib4 When a database table contains a field named 'version', like his one: DROP TABLE IF EXISTS `tester`.`software_package`; CREATE TABLE `tester`.`software_package` ( `software_id` int(11) NOT NULL auto_increment, `version` varchar(100) default NULL, `name` varchar(100) default NULL, `root_file_id` int(11) default NULL, PRIMARY KEY (`software_id`) ) ENGINE=InnoDB DEFAULT CHARSET=latin1; The following error is thrown: [java] Initial SessionFactory creation failed.java.lang.ClassCastException: org.hibernate.type.StringType cannot be cast to org.hibernate.type.VersionType [java] Exception in thread "main" java.lang.ExceptionInInitializerError [java] at util.HibernateUtil.<clinit>(Unknown Source) [java] at events.EventManager.listNodes(Unknown Source) [java] at events.EventManager.main(Unknown Source) [java] Caused by: java.lang.ClassCastException: org.hibernate.type.StringType cannot be cast to org.hibernate.type.VersionType [java] at org.hibernate.tuple.PropertyFactory.buildVersionProperty(PropertyFactory.java:84) [java] at org.hibernate.tuple.entity.EntityMetamodel.<init>(EntityMetamodel.java:168) [java] at org.hibernate.persister.entity.AbstractEntityPersister.<init>(AbstractEntityPersister.java:434) [java] at org.hibernate.persister.entity.SingleTableEntityPersister.<init>(SingleTableEntityPersister.java:109) [java] at org.hibernate.persister.PersisterFactory.createClassPersister(PersisterFactory.java:55) [java] at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:226) [java] at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1294) [java] ... 3 more -- 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, 11 months

6
7
0 / 0

[Hibernate-JIRA] Created: (HHH-4968) Cannot deactivate default BeanValidationListener independently of DDL constraints generation

by Vladimir Klyushnikov (JIRA)

Cannot deactivate default BeanValidationListener independently of DDL constraints generation -------------------------------------------------------------------------------------------- Key: HHH-4968 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4968 Project: Hibernate Core Issue Type: Bug Components: annotations Affects Versions: 3.5.0-CR-2 Environment: Hibernate 3.5.0-CR-2, Hibernate Validator 4.0.2.GA Reporter: Vladimir Klyushnikov Hi, I need to configure my custom BeanValidationListener instance through Spring, but I cannot deactivate default BeanValidationListener instance. It can be switched off only with DDL constraint generation. When I provide *DDL* value for *javax.persistence.validation.mode* it still activates default BeanValidationListener. When I provide *NONE* value it switches off both BeanValidationListener and DDL constraints. This is because of following code in *BeanValidationListener.java*: {code} public static void activateBeanValidation(EventListeners eventListeners, Properties properties) { ... if ( modes.contains( ValidationMode.NONE ) ) return; ... } {code} It should be changed to following: {code} if (!(modes.contains(ValidationMode.CALLBACK) || modes.contains( ValidationMode.AUTO))) return; {code} -- 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, 11 months

3
12
0 / 0

[Hibernate-JIRA] Created: (HHH-5195) FilterImpl.validate() throws NullPointerExeption at line 164

by Savochkin Alexander (JIRA)

FilterImpl.validate() throws NullPointerExeption at line 164 ------------------------------------------------------------ Key: HHH-5195 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5195 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.1 Environment: hibernate-distribution-3.5.1-Final-dist Reporter: Savochkin Alexander After deserialization NPE is thrown at this line FilterImpl {code} line:164 Iterator itr = definition.getParameterNames().iterator(); {code} the last lines from stack trace are: {code} java.lang.NullPointerException at org.hibernate.impl.FilterImpl.validate(FilterImpl.java:164) at org.hibernate.engine.LoadQueryInfluencers.getEnabledFilters(LoadQueryInfluencers.java:109) at org.hibernate.impl.SessionImpl.readObject(SessionImpl.java:2144) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:600) at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:986) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1865) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1769) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1345) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:364) {code} Looking at SessionImpl class we see: {code} line 2143: Iterator iter = loadQueryInfluencers.getEnabledFilters().values().iterator(); while ( iter.hasNext() ) { ( ( FilterImpl ) iter.next() ).afterDeserialize( factory ); } {code} LoadQueryInfluencers: {code} line:105 Iterator itr = enabledFilters.values().iterator(); while ( itr.hasNext() ) { final Filter filter = ( Filter ) itr.next(); filter.validate(); } {code} So, afterDeserialization() on enabled filters method is invoked AFTER getEnabledFilters() method is. It seems to be the reason why the private TRANSIENT field "definition" of every filter is null at the moment of filter validation! "definition" field is supposed to be initialized only after validate() is called. -- 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, 11 months

3
11
0 / 0

[Hibernate-JIRA] Created: (HHH-4036) EntityMetamodel entityNameByInheritenceClassNameMap field used inconsistently

by Jeremy Stone (JIRA)

EntityMetamodel entityNameByInheritenceClassNameMap field used inconsistently ----------------------------------------------------------------------------- Key: HHH-4036 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4036 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.2 Reporter: Jeremy Stone After upgrading (from 3.3.0.SP1) to 3.3.2.GA we have started getting the follow stack trace logged: org.hibernate.HibernateException: Unable to resolve entity name from Class [com.cyclone.netPrefect.admin.restriction.complex.TimeSpanRestrictionItemEntity] expected instance/subclass of [RestrictionItem] at org.hibernate.tuple.entity.PojoEntityTuplizer.determineConcreteSubclassEntityName(PojoEntityTuplizer.java:363) at org.hibernate.persister.entity.AbstractEntityPersister.getSubclassEntityPersister(AbstractEntityPersister.java:3643) at org.hibernate.impl.SessionImpl.getEntityPersister(SessionImpl.java:1375) at org.hibernate.engine.ForeignKeys.isTransient(ForeignKeys.java:203) at org.hibernate.event.def.AbstractSaveEventListener.getEntityState(AbstractSaveEventListener.java:535) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.performSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:103) ... etc, etc The com.cyclone.netPrefect.admin.restriction.complex.TimeSpanRestrictionItemEntity is mapped (with entity name TimeSpanRestrictionItem) as a joined subclass of the entity named RestrictionItem. I have had a look at the Hibernate source for 3.3.2.ga and it looks like problem is the way that the org.hibernate.tuple.entity.EntityMetamodel is using it entityNameByInheritenceClassNameMap field: * Puts to the map are based on PersistentClass.getMappedClass() as a key - a Class object * Gets from the map (in findEntityNameByEntityClass method) are using the class name Presumably (given the name of the map field) both put and get should be using the class name. -- 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, 11 months

10
20
0 / 0

[Hibernate-JIRA] Created: (HHH-5192) Can't use group_concat in mysql without creating a custom function

by Douglas Ferguson (JIRA)

Can't use group_concat in mysql without creating a custom function ------------------------------------------------------------------ Key: HHH-5192 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5192 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.5.1 Environment: Linux, Mysql Reporter: Douglas Ferguson After upgrading we starting getting the exception below and had to register a "custom" function.. Caused by: org.hibernate.HibernateException: Unable to locate mapping for function named [group_concat] at org.hibernate.criterion.AggregateProjection.getFunction(AggregateProjection.java:93) at org.hibernate.criterion.AggregateProjection.getFunction(AggregateProjection.java:85) at org.hibernate.criterion.AggregateProjection.getTypes(AggregateProjection.java:64) at org.hibernate.criterion.ProjectionList.getTypes(ProjectionList.java:61) at org.hibernate.loader.criteria.CriteriaQueryTranslator.getProjectedTypes(CriteriaQueryTranslator.java:362) at org.hibernate.loader.criteria.CriteriaJoinWalker.<init>(CriteriaJoinWalker.java:101) at org.hibernate.loader.criteria.CriteriaJoinWalker.<init>(CriteriaJoinWalker.java:83) at org.hibernate.loader.criteria.CriteriaLoader.<init>(CriteriaLoader.java:92) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1687) at org.hibernate.impl.CriteriaImpl.list(CriteriaImpl.java:347) -- 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, 11 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5273) RowCountProjection long to int cast exception

by Pamir Erdem (JIRA)

RowCountProjection long to int cast exception --------------------------------------------- Key: HHH-5273 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5273 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.5.2 Environment: hibernate-core 3.5.2 Reporter: Pamir Erdem After we upgraded our hibernate.jar from 3.3.2 to 3.5.2 the methods which executes rowcount functions have started to throw long to cast exception. >From the source code of hibernate, it is clear that for the features which will be implemented in 3.6 some implementations are changed. #http://opensource.atlassian.com/projects/hibernate/browse/HHH-5138 In 3.3.2 {code:title=RowCountProjection.java|borderStyle=solid} public Type[] getTypes(Criteria criteria, CriteriaQuery criteriaQuery) throws HibernateException { return new Type[] { Hibernate.INTEGER }; } {code} In 3.5.2 {code:title=RowCountProjection.java|borderStyle=solid} return new Type[] { getFunction( criteriaQuery ).getReturnType( null, criteriaQuery.getFactory() ) }; {code} But the definitions of the rowcount functions in both versions in same in Dialect.java {code} static { STANDARD_AGGREGATE_FUNCTIONS.put( "count", new StandardSQLFunction("count") { public Type getReturnType(Type columnType, Mapping mapping) { return Hibernate.LONG; } public String render(List args, SessionFactoryImplementor factory) { if ( args.size() > 1 ) { if ( "distinct".equalsIgnoreCase( args.get( 0 ).toString() ) ) { return renderCountDistinct( args ); } } return super.render( args, factory ); } {code} By this minor change in 3.5.2 all the project tests which executes count sql function are failing by throwing class cast exception -- 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, 11 months

4
4
0 / 0

[Hibernate-JIRA] Created: (HHH-5098) AssertionFailure thrown when collection contains a parameterized type

by Kahli Burke (JIRA)

AssertionFailure thrown when collection contains a parameterized type --------------------------------------------------------------------- Key: HHH-5098 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5098 Project: Hibernate Core Issue Type: Bug Components: entity-manager Affects Versions: 3.5.0-Final Reporter: Kahli Burke Attachments: patch.txt The following exception is thrown when an entity exists with a collection containing a parameterized type: ERROR [AssertionFailure] an assertion failure occured (this may indicate a bug in Hibernate): org.hibernate.annotations.common.AssertionFailure: Fail to process type argument in a generic declaration. Type: class sun.reflect.generics.reflectiveObjects.ParameterizedTypeImpl at org.hibernate.ejb.metamodel.AttributeFactory$PluralAttributeMetadataImpl.getClassFromGenericArgument(AttributeFactory.java:836) at org.hibernate.ejb.metamodel.AttributeFactory$PluralAttributeMetadataImpl.<init>(AttributeFactory.java:748) at org.hibernate.ejb.metamodel.AttributeFactory$PluralAttributeMetadataImpl.<init>(AttributeFactory.java:723) at org.hibernate.ejb.metamodel.AttributeFactory.determineAttributeMetadata(AttributeFactory.java:518) at org.hibernate.ejb.metamodel.AttributeFactory.buildAttribute(AttributeFactory.java:93) at org.hibernate.ejb.metamodel.MetadataContext.wrapUp(MetadataContext.java:183) at org.hibernate.ejb.metamodel.MetamodelImpl.buildMetamodel(MetamodelImpl.java:66) at org.hibernate.ejb.EntityManagerFactoryImpl.<init>(EntityManagerFactoryImpl.java:83) at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:883) at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:73) at org.jboss.jpa.builder.DefaultCEMFBuilder.build(DefaultCEMFBuilder.java:47) at org.jboss.jpa.deployment.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:316) For example if a field exists like: @OneToMany List<SomeEntity<SomeClass>> associatedList; I've attached a patch that includes a test case for the entity-manager project and a proposed fix. -- 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, 11 months

5
8
0 / 0

[Hibernate-JIRA] Created: (HHH-5252) AttributeFactory needs more info in AssertionFailure

by Travis Stevens (JIRA)

AttributeFactory needs more info in AssertionFailure ---------------------------------------------------- Key: HHH-5252 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5252 Project: Hibernate Core Issue Type: Improvement Components: entity-manager Affects Versions: 3.5.2, 3.5.0-Final Environment: Hibernate version: 3.5.0-Final Reporter: Travis Stevens Priority: Trivial Attachments: tstevens-em.patch An exception is thrown that doesn't provide information about what member hibernate is asserting for. Attached is a patch that will include the associated Member object to the exception in order to provide some context. -- 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, 11 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5062) In the Session.flush method has a lost of perfomance about 50% when flush a large amout of data

by Fabiano Cury (JIRA)

In the Session.flush method has a lost of perfomance about 50% when flush a large amout of data ----------------------------------------------------------------------------------------------- Key: HHH-5062 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5062 Project: Hibernate Core Issue Type: Improvement Components: core Affects Versions: 3.5.0-Final, 3.5.0-CR-2, 3.5.0-CR-1, 3.5.0-Beta-4, 3.5.0-Beta-3, 3.5.0-Beta-2, 3.5.0.Beta-1, 3.3.2, 3.3.1, 3.3.0.SP1, 3.3.0.GA, 3.3.0.CR2, 3.3.0.CR1, 3.2.7, 3.2.6 Environment: Linux / DB2 / version 3.2.6 and above Reporter: Fabiano Cury Attachments: issueHibernate.JPG When the flush method is called this method call the onFlush method of class DefaultFlushEventListener and then the method flushEverythingToExecutions(event). This method (flushEverythingToExecutions) call many times (loop) the method log.isDebugEnabled(). This cause a big overhead in this method. I suggest you to put an attribute in the method flushEverythingToExecutions(flushEverythingToExecutions(FlushEvent event, Boolean isDebugEnable) and verify this attribute before the loop for. Attached the print screen of profiling that help me to detect this issue. Tks. -- 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, 11 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3045) Duplicated column aliases in scalar query

by Anderson Souza (JIRA)

Duplicated column aliases in scalar query ----------------------------------------- Key: HHH-3045 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3045 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.5 Environment: Hibernate 3.2.4SP1, 3.2.5GA Oracle 10g Reporter: Anderson Souza Priority: Critical Attachments: ddl-tables.sql, dominio.zip The HQL bellow works fine, but when I add a call to a funcion in the select clause the SQL generated has duplicated aliases and it generate error on query execution, because the query is paginated. {code} select a from Area a inner join fetch a.horarioPadrao left outer join fetch a.horarioTemporario as hrtemp {code} The SQL generated for this query is: {code} select * from ( select area0_.cod_local as cod1_15_0_, horarioare1_.cod_area as cod1_6_1_, horarioare2_.cod_area as cod1_7_2_, area0_.des_local as des2_15_0_, area0_.sig_local as sig3_15_0_, area0_.flg_extinto as flg4_15_0_, horarioare1_.hr_hora_ini as hr2_6_1_, horarioare1_.hr_hora_fim as hr3_6_1_, horarioare1_.flg_fim_semana as flg4_6_1_, horarioare2_.hr_hora_ini as hr2_7_2_, horarioare2_.hr_hora_fim as hr3_7_2_, horarioare2_.flg_fim_semana as flg4_7_2_, horarioare2_.dat_ini_vigencia as dat5_7_2_, horarioare2_.dat_fim_vigencia as dat6_7_2_ from esq_fp.tb_local area0_ inner join tb_horario_local_padrao horarioare1_ on area0_.cod_local=horarioare1_.cod_area left outer join tb_horario_local_temporario horarioare2_ on area0_.cod_local=horarioare2_.cod_area where 1=1 order by area0_.sig_local ) where rownum <= ? {code} The scalar HQL query that generate duplicated column names is: {code} select a, count(*) from Area a inner join fetch a.horarioPadrao left outer join fetch a.horarioTemporario as hrtemp {code} The SQL generated is: {code} select * from ( select area0_.cod_local as col_0_0_, count(*) as col_1_0_, horarioare1_.cod_area as cod1_6_1_, horarioare2_.cod_area as cod1_7_2_, area0_.cod_local as cod1_15_0_, horarioare1_.cod_area as cod1_6_1_, horarioare2_.cod_area as cod1_7_2_, area0_.des_local as des2_15_0_, area0_.sig_local as sig3_15_0_, area0_.flg_extinto as flg4_15_0_, horarioare1_.hr_hora_ini as hr2_6_1_, horarioare1_.hr_hora_fim as hr3_6_1_, horarioare1_.flg_fim_semana as flg4_6_1_, horarioare2_.hr_hora_ini as hr2_7_2_, horarioare2_.hr_hora_fim as hr3_7_2_, horarioare2_.flg_fim_semana as flg4_7_2_, horarioare2_.dat_ini_vigencia as dat5_7_2_, horarioare2_.dat_fim_vigencia as dat6_7_2_ from esq_fp.tb_local area0_ inner join tb_horario_local_padrao horarioare1_ on area0_.cod_local=horarioare1_.cod_area left outer join tb_horario_local_temporario horarioare2_ on area0_.cod_local=horarioare2_.cod_area where 1=1 order by area0_.sig_local ) where rownum <= ? {code} As you can see the aliases cod1_6_1_ and cod1_7_2_ are repeated and this repetition breaks the paginated query, beacause the main query appears in the from clause. The HBM's and classes are attached. -- 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, 11 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-4053) Incorrect SQL with substring for Firebird

by yeti the foot (JIRA)

Incorrect SQL with substring for Firebird ----------------------------------------- Key: HHH-4053 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4053 Project: Hibernate Core Issue Type: Bug Components: query-sql Affects Versions: 3.3.1 Reporter: yeti the foot HQL query substring function generate incorrect SQL query for Firebird. In Firebird SQL query with substring has follow syntax: substring(str from 1 for 3). Generated ин Hibernate query looks like: substring(str, 1, 3). -- 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, 11 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2190) JDBCTransaction.isActive() should report false if jdbcContext.connection().isClosed()

by Jeffrey Bennett (JIRA)

JDBCTransaction.isActive() should report false if jdbcContext.connection().isClosed() ------------------------------------------------------------------------------------- Key: HHH-2190 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2190 Project: Hibernate3 Type: Bug Components: core Reporter: Jeffrey Bennett In error-handling routines, I use Transaction.isActive() to determine if it is 'safe' to perform Transaction.rollback(). If the Session has previously closed, Transaction.isActive() mis-reports that the transaction is still alive when it is not. I'll grant that the JavaDoc for isActive indicates it is the 'local transaction', not the underlying transaction, but since there is no way to delve into the underlying connection in the public API, that is really a cop-out. If you don't like the idea of modifying the behavior of isActive(), how about exposing a 'public Connection connection()' method that exposes the connection? -- 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, 11 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3058) When using native sql query and multiple selects with setMaxResults, Hibernate inserts the TOP statement in the first query

by Sean Blaes (JIRA)

When using native sql query and multiple selects with setMaxResults, Hibernate inserts the TOP statement in the first query --------------------------------------------------------------------------------------------------------------------------- Key: HHH-3058 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3058 Project: Hibernate3 Issue Type: Bug Components: query-sql Affects Versions: 3.2.4.sp1 Environment: Hibernate 3.2.4sp1, Microsoft SQL Server Reporter: Sean Blaes Priority: Minor When using a query similar to the following: DECLARE @SUB_TABLE TABLE( ID INT ) INSERT INTO @SUB_TABLE SELECT ID FROM FOO SELECT * FROM BAR INNER JOIN @SUB_TABLE ON ... Then if I call setMaxResults(100) on the query object. It inserts "TOP 100" in the first query, which isn't really what would be expected. Since the second SELECT actually consists of the data that will be returned, the TOP 100 statement should go there. I'd expect it's an easy fix. Just start your search for SELECT from the bottom rather than the top. However, I guess you have to make sure you're not hitting a subquery of a larger select either... I may try cooking up a patch this weekend for this if I can find the time, and I'll attach it to this issue if I do. -- 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, 11 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3405) Add support for Unicode aware MS SQL Server dialect

by Chris Larun (JIRA)

Add support for Unicode aware MS SQL Server dialect --------------------------------------------------- Key: HHH-3405 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3405 Project: Hibernate3 Issue Type: New Feature Components: core Affects Versions: 3.2.6 Reporter: Chris Larun Cf. http://jira.atlassian.com/browse/CONF-4786 for a description of the issue. http://forum.hibernate.org/viewtopic.php?t=941781&highlight=sqlserver+dia... for a possible solution. -- 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, 11 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3905) Improve FieldInterceptionHelper perfomance

by Sergey Vladimirov (JIRA)

Improve FieldInterceptionHelper perfomance ------------------------------------------ Key: HHH-3905 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3905 Project: Hibernate Core Issue Type: Improvement Components: core Affects Versions: 3.3.1 Reporter: Sergey Vladimirov Priority: Minor Attachments: patch.txt do not iterate over interfaces, use Class.isAssignableFrom -- 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, 11 months

2
6
0 / 0

[Hibernate-JIRA] Created: (HHH-5262) Allow UserType and CompositeUserType to be registered with BasicTypeRegistry

by Steve Ebersole (JIRA)

Allow UserType and CompositeUserType to be registered with BasicTypeRegistry ---------------------------------------------------------------------------- Key: HHH-5262 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5262 Project: Hibernate Core Issue Type: Improvement Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.6 The implication here is that CustomType and CompositeCustomType need to (1) derive from the BasicType interface and (2) allow the user to configure the registration keys. 2 options for registration keys: # new (optional) interface, RegisterableUserType # allow passing the keys during registration via Configuration -- 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, 11 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-5268) Support for java.util.UUID properties/generators

by Steve Ebersole (JIRA)

Support for java.util.UUID properties/generators ------------------------------------------------ Key: HHH-5268 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5268 Project: Hibernate Core Issue Type: Improvement Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.x See discussion on dev mailing list : http://lists.jboss.org/pipermail/hibernate-dev/2010-May/005209.html -- 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, 11 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-1989) Deleted object remains referenced in 2nd level cache collections

by Justin Haddad (JIRA)

Deleted object remains referenced in 2nd level cache collections ---------------------------------------------------------------- Key: HHH-1989 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1989 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.cr2 Environment: Spring 1.2.8, Hibernate 3.2, Postgres 8.0.3 Reporter: Justin Haddad This problem seems identical to issue NH-678. I have enabled caching for an one-to-many association. I use Ehcache. I have a test in which I load the parent object along with its collection. Both the parent and the collection wind up in the 2nd level cache. I then delete an object that is in the collection, not by removing it from the collection, but rather by doing a delete on the object itself. After deleting, I try to reload the parent and get the following exception (User#3102 is the deleted object): aused by: org.hibernate.ObjectNotFoundException: No row with the given identifier exists: [com.bluenotenetworks.common.management.sm.User#3102] at org.hibernate.impl.SessionFactoryImpl$1.handleEntityNotFound(SessionFactoryImpl.java:372) at org.hibernate.event.def.DefaultLoadEventListener.load(DefaultLoadEventListener.java:128) at org.hibernate.event.def.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:178) at org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:86) at org.hibernate.impl.SessionImpl.fireLoad(SessionImpl.java:871) at org.hibernate.impl.SessionImpl.internalLoad(SessionImpl.java:839) at org.hibernate.type.EntityType.resolveIdentifier(EntityType.java:266) at org.hibernate.type.ManyToOneType.assemble(ManyToOneType.java:177) at org.hibernate.collection.PersistentSet.initializeFromCache(PersistentSet.java:101) at org.hibernate.cache.entry.CollectionCacheEntry.assemble(CollectionCacheEntry.java:35) at org.hibernate.event.def.DefaultInitializeCollectionEventListener.initializeCollectionFromCache(DefaultInitializeCollectionEventListener.java:130) at org.hibernate.event.def.DefaultInitializeCollectionEventListener.onInitializeCollection(DefaultInitializeCollectionEventListener.java:48) at org.hibernate.impl.SessionImpl.initializeCollection(SessionImpl.java:1705) (continues on) I stepped through the code in the debugger and can see that the object's ID (3102 in this case) remains in the cached collection even after the deletion. -- 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, 11 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5228) In Envers, retrieve only the most recent revision for all entities of a particular type

by Edwin Tellman (JIRA)

In Envers, retrieve only the most recent revision for all entities of a particular type --------------------------------------------------------------------------------------- Key: HHH-5228 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5228 Project: Hibernate Core Issue Type: Improvement Components: envers Affects Versions: 3.3.2 Environment: any Reporter: Edwin Tellman Priority: Minor I would like to retrieve the most recent version of everything that has changed since a specified revision. This is useful for keeping one application synchronized with another. One system polls the other and the second system provides the current state of things that have changed recently. This query fetches everything that has changed since the specified revision: AuditQuery query = auditReader.createQuery() .forRevisionsOfEntity(entityClass, false, true) .add(AuditEntity.revisionNumber().gt(revision)) If I add a maximize restriction on the revision number, I get a single item which changed at the highest revision number, which isn't what I'm looking for. You could find the right data in SQL or HQL by grouping by ID and then selecting the maximum revision from each group. And, of course, I can use the above query and then filter out the older items from the result in Java, which is what I'm doing now. -- 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, 11 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3075) Should be possible to register UserTypes for known property types (classes) in configuration

by Martin Probst (JIRA)

Should be possible to register UserTypes for known property types (classes) in configuration -------------------------------------------------------------------------------------------- Key: HHH-3075 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3075 Project: Hibernate3 Issue Type: Improvement Components: core Environment: n/a Reporter: Martin Probst Priority: Minor Currently, when persisting primitive properties of a class that are not known to Hibernate, there are only cumbersome ways to tell Hibernate that a certain UserType should be used. Good example is Joda Time: <pre> @Entity class MyClass { org.joda.time.DateTime foo; } </pre> .. which will result in ugly binary fields in database. Next try: <pre> @Entity class MyClass { @Type(type = "org.joda.time.contrib.hibernate.PersistentDateTime") org.joda.time.DateTime foo; } </pre> That works, but now I have to specify that on all time fields of all classes. Plus it's different types for different classes, which makes it more messy. And it's simply a string in code, so it's fragile to refactoring, code move, etc. TypeDefs allow a shorter handle for certain types, but don't really address the refactoring issues. A better way might be to allow configurations to register UserTypes for known classes. E.g. have a configuration directive like this: <mappable-type class="org.joda.time.DateTime" usertype="org.joda.time.hibernate.DateTimeType"/> This would allow the classes to stay clean from type mappings and reduce coupling between domain objects and persistence mapping. This might be as easy as allowing the org.hibernate.type.TypeFactory map to be extended at configuration time. -- 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, 11 months

3
3
0 / 0

[Hibernate-JIRA] Commented: (HHH-13) Fetch groups

by Sebastien Tardif (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-13?page=com... ] Sebastien Tardif commented on HHH-13: ------------------------------------- GK said: the "fetch group" notion does not work with annotations You can see an annotation example here: http://openjpa.apache.org/builds/1.0.2/apache-openjpa-1.0.2/docs/manual/r... > Fetch groups > ------------ > > Key: HHH-13 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-13 > Project: Hibernate Core > Issue Type: Improvement > Components: core > Affects Versions: 3.1 rc3 > Reporter: Adrien > > I don't like JDO at all, but it may have a good feature : the fetch groups. Instead of saying in each request which relations (or property now) I want to be fetch, I could says which fetch groups I want to be loaded. I will be usefull for complex objects will lot of relationship. Each fetch group will represent a view to the object. > from Contract c > left join fetch c.customer > left join fetch c.items > left join fetch c.foo > ==> > from Contract c > left join fetch c.fetchGroup1 > with : > <many-to-one name="customer" fetch-group="fetchGroup1" /> > <set name="items" fetch-group="fetchGroup1, fetchGroup2" > > <many-to-one name="foo" fetch-group="fetchGroup1" /> > > Adrien -- 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, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5279) Performance: a lot of time is spent getting and setting the auto-commit flag. Suggest it be configurable

by Phillip Henry (JIRA)

Performance: a lot of time is spent getting and setting the auto-commit flag. Suggest it be configurable -------------------------------------------------------------------------------------------------------- Key: HHH-5279 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5279 Project: Hibernate Core Issue Type: Improvement Components: core Affects Versions: 3.5.2 Environment: Seen in Hibernate 3.2 but appears to still be in Trunk Reporter: Phillip Henry Priority: Minor In org.hibernate.transaction.JDBCTransaction, a call to getAutoCommit is made on the connection at the start of the transaction and if it returns true, a setAutoCommit(true) is made after Hibernate has finished. These calls may be network calls (they certainly are with Sybase JConnect 5.5 drivers. They may be with others as well) and they are done in the same thread as that executing my INSERT/UPDATE commands. This means that about 25% of the time spent making a simple Session.saveOrUpdate is spent on something that is not important to me (in my application, I am not sharing the connection pool with other services so I don't care about the auto-commit status of connections when they are in the pool). It would be nice if I could speed up my application a little by setting an optional flag that indicates to JDBCTransaction whether it should care or not about the state of the connection when it has finished with it. Or, to have this work done by another thread. See http://javaagile.blogspot.com/2010/05/hibernate-and-performance-tuning.html for YourKit profiles. -- 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, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5278) Wrong parsing of hql/ejbql query

by ron piterman (JIRA)

Wrong parsing of hql/ejbql query -------------------------------- Key: HHH-5278 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5278 Project: Hibernate Core Issue Type: Bug Components: query-hql Affects Versions: 3.3.2 Reporter: ron piterman Attachments: hibtest.tar.gz Hibernate parses following query, ignoring superfluous parentheses and rules after: FROM Parent AS p WHERE p.id = ? ) AND p.child is null Attached is a test which should not pass. -- 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, 11 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HV-326) Verify that for caching user objects during the validation process we use a IdentityHashMap or IdentityHashSet

by Emmanuel Bernard (JIRA)

Verify that for caching user objects during the validation process we use a IdentityHashMap or IdentityHashSet -------------------------------------------------------------------------------------------------------------- Key: HV-326 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-326 Project: Hibernate Validator Issue Type: Bug Components: engine Affects Versions: 4.0.1.GA Reporter: Emmanuel Bernard Assignee: Hardy Ferentschik Fix For: 4.1.0 -- 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, 11 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-5271) Support for Sybase IQ database in StandardDialectResolver

by Anton Nikitin (JIRA)

Support for Sybase IQ database in StandardDialectResolver --------------------------------------------------------- Key: HHH-5271 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5271 Project: Hibernate Core Issue Type: Improvement Components: core Affects Versions: 3.5.2 Reporter: Anton Nikitin Priority: Minor During our experiments we have found that StandardDialectResolver is not able to determine dialect for Sybase IQ 15.1 database. I recommend to include the check for getDatabaseProductName().startsWith("Sybase IQ") and return SybaseAnywhereDialect for it. -- 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, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5004) Specifying entity access type at class level and then redundantly again on id field or getId() causes EntityManagerFactory configuration failure

by Jesse Hutton (JIRA)

Specifying entity access type at class level and then redundantly again on id field or getId() causes EntityManagerFactory configuration failure ------------------------------------------------------------------------------------------------------------------------------------------------ Key: HHH-5004 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5004 Project: Hibernate Core Issue Type: Bug Components: annotations, entity-manager Affects Versions: 3.5.0-CR-2 Environment: I'm developing on Fedora 12 64bit version. java version: Java(TM) SE Runtime Environment (build 1.6.0_18-b07) Reporter: Jesse Hutton Priority: Minor Attachments: testHibernate.tar.gz If you annotation an entity class with @Access and either AccessType.FIELD or AccessType.PROPERTY and then repeat the same respective access annotation for identifier of the class, hibernate will not be able to find the identifier. An example stack trace is: javax.persistence.PersistenceException: [PersistenceUnit: testhibernate] Unable to configure EntityManagerFactory ... Caused by: org.hibernate.AnnotationException: No identifier specified for entity: com.mycompany.testhibernate.Foo ... To annotate a class as such is clearly redundant, but it doesn't seem like it should really cause this error. I happened to have discovered it while experimenting with different access type options in JPA 2 using EclipseLink, forgetting to remove an access type annotation to the getId() method of my entity, and then eventually switching JPA providers to Hibernate. Under EclipseLink, there was no problem with the redundant annotations. Attached is a sample test app illustrating the problem. It has access PROPERTY specified, but the error occurs with FIELD just the same. -- 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, 11 months

4
6
0 / 0

[Hibernate-JIRA] Created: (HHH-5270) Oracle Error ORA-01719 on @ManyToMany associations with @FilterJoinTable annotation

by Nico Mack (JIRA)

Oracle Error ORA-01719 on @ManyToMany associations with @FilterJoinTable annotation ----------------------------------------------------------------------------------- Key: HHH-5270 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5270 Project: Hibernate Core Issue Type: Bug Components: query-hql Environment: Hibernate 3.4.0GA (shipped with JBoss 5.1GA) Oracle 11R2 Standard Edition Reporter: Nico Mack I have an User EJB Bean who can be assigned via a relation table any number of roles. The following mapping in my User Bean @ManyToMany(fetch = FetchType.LAZY) @FilterJoinTable(name = "contextFilter", condition = "context_id = :contextId OR context_id IS NULL") @JoinTable(name = "rel_user_role", schema = "usermanagement", joinColumns = {@JoinColumn(name = "user_id")}, inverseJoinColumns = {@JoinColumn(name = "role_id")}) public Set <Role> getRoles() { return m_Roles; } results in the following query being generated: select roles0_.user_id as user4_1_, roles0_.role_id as role3_1_, role1_.id as id5_0_, role1_.created as created5_0_, role1_.creator as creator5_0_, role1_.modified as modified5_0_, role1_.modifier as modifier5_0_, role1_.description as descript4_5_0_, role1_.name as name5_0_ from usermanagement.rel_user_role roles0_, usermanagement.role role1_ where roles0_.role_id=role1_.id(+) and roles0_.context_id = ? OR roles0_.context_id IS NULL and roles0_.user_id=? which in turn causes the following oracle error: java.sql.SQLException: ORA-01719: outer join operator (+) not allowed in operand of OR or IN -- 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, 11 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HCANN-24) @PrimaryKeyJoinColumn and @ForeignKey(name = "FOREIGN_FOOBAR") don't work for InheritanceType.JOINED

by Marcin Cinik (JIRA)

@PrimaryKeyJoinColumn and @ForeignKey(name = "FOREIGN_FOOBAR") don't work for InheritanceType.JOINED ---------------------------------------------------------------------------------------------------- Key: HCANN-24 URL: http://opensource.atlassian.com/projects/hibernate/browse/HCANN-24 Project: Hibernate Commons Annotations Issue Type: Bug Affects Versions: 3.2.0 Environment: dialect: Oracle10g Reporter: Marcin Cinik Attachments: jpr.zip, schema2.ddl I've got an example where I have two classes: Customer, ValuedCustomer, where ValuedCustomer inherits from Customer. As InheritanceType.JOINED is used here, hibernate will generate a primary key in ValuedCustomer as well as all integrity constraints for that (I use Oracle10g dialect). I would like to give a name to that foreign key in ValuedCustomer (which is also a primary key there), but it's not possible. In ValuedCustomer I use @PrimaryKeyJoinColumn annotation and @org.hibernate.annotations.Table with foreignKey property set in it. I would like that hibernate hbm2ddl generate foreign key constraint name as indicated in @ForeignKey annotation but it doesn't. It generates random constraint name instead. I'm attaching example java project and generated schema file. -- 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, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5269) Schema specified in @Table annotation should be passed as a parameter to the SequenceGenerator generate method.

by Nico Mack (JIRA)

Schema specified in @Table annotation should be passed as a parameter to the SequenceGenerator generate method. --------------------------------------------------------------------------------------------------------------- Key: HHH-5269 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5269 Project: Hibernate Core Issue Type: Improvement Components: core Environment: Hibernate 3.4.0GA (bundled with JBoss5.1GA) Reporter: Nico Mack Priority: Minor In the scope of a recent project built on JBoss5.1GA and using Oracle as a database we came up with the following architecture. Since all our EJBs are going to need an Id, we put the ID property in a class, called CoreEntityBean with the @MappedSuperclass annotation. Here's what the getId method looks like: @Id @GeneratedValue(generator="my_gen") @GenericGenerator(name = "my_gen", strategy = "my_package.TableNameSequenceGenerator") @Column(name = "id") public Integer getId() { return this.Id; } All our actual EJBs inherit from this CoreEntityBean, and are mapped using @Table annotations to tables in different schemas: @Entity @Table(name = "info", schema = "core") public class CoreInfo extends CoreEntityBean { Our custom TableNameSequenceGenerator basically takes the name of the table and adds the suffix "_seq" to determine the name of the sequence for the corresponding table. All sequences have been created beforehand, in the same schema the corresponding table is located. Here's what the generate method of our TableNameSequenceGenerator looks like: @Override public void configure (Type p_Type, Properties p_Parameters, Dialect p_Dialect) throws MappingException { String l_TableName; String l_SequenceName; String l_SchemaName; l_SequenceName = p_Parameters.getProperty(SequenceGenerator.SEQUENCE); if ((l_SequenceName == null) || (l_SequenceName.length() == 0)) { l_TableName = p_Parameters.getProperty(PersistentIdentifierGenerator.TABLE); l_SchemaName = p_Parameters.getProperty(PersistentIdentifierGenerator.SCHEMA); if (l_TableName != null) { l_SequenceName = (l_SchemaName != null)?l_SchemaName + "." + l_TableName + "_seq":l_TableName + "_seq"; p_Parameters.setProperty(SequenceGenerator.SEQUENCE, l_SequenceName); m_Logger.log(Level.INFO, "Sequence Name = " + l_SequenceName); } } super.configure (p_Type,p_Parameters,p_Dialect); } When single-stepping through the generate method, we came to realize that the SCHEMA property was never set and as a consequence the db sequences are not found. I'm not sure whether this issue has already been fixed in a later version or not. If not, I thought it would be useful to add the schema to the properties passed to the SequenceGenerator. -- 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, 11 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HV-293) Annotation processor fails in Eclipse when evaluating custom constraints not defined in the current project

by Gunnar Morling (JIRA)

Annotation processor fails in Eclipse when evaluating custom constraints not defined in the current project ----------------------------------------------------------------------------------------------------------- Key: HV-293 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-293 Project: Hibernate Validator Issue Type: Bug Affects Versions: 4.1.0-Beta-1 Reporter: Gunnar Morling Assignee: Hardy Ferentschik In certain situations the AP fails when being integrated in Eclipse with the following exception: java.lang.AssertionError: Class org.hibernate.validator.constraints.impl.LengthValidator specified in @Constraint.validatedBy doesn't implement ConstraintValidator. at org.hibernate.validator.ap.util.ConstraintHelper.getConstraintValidatorSuperType(ConstraintHelper.java:497) at org.hibernate.validator.ap.util.ConstraintHelper.getSupportedType(ConstraintHelper.java:426) at org.hibernate.validator.ap.util.ConstraintHelper.getSupportedTypes(ConstraintHelper.java:402) at org.hibernate.validator.ap.util.ConstraintHelper.checkCustomConstraint(ConstraintHelper.java:356) at org.hibernate.validator.ap.util.ConstraintHelper.checkConstraint(ConstraintHelper.java:295) at org.hibernate.validator.ap.ConstraintAnnotationVisitor.checkConstraintAtField(ConstraintAnnotationVisitor.java:290) at org.hibernate.validator.ap.ConstraintAnnotationVisitor.visitVariableAsField(ConstraintAnnotationVisitor.java:174) at org.hibernate.validator.ap.ConstraintAnnotationVisitor.visitVariableAsField(ConstraintAnnotationVisitor.java:45) at javax.lang.model.util.ElementKindVisitor6.visitVariable(ElementKindVisitor6.java:199) at org.eclipse.jdt.internal.compiler.apt.model.VariableElementImpl.accept(VariableElementImpl.java:55) at org.hibernate.validator.ap.ConstraintValidationProcessor.process(ConstraintValidationProcessor.java:84) at org.eclipse.jdt.internal.compiler.apt.dispatch.RoundDispatcher.handleProcessor(RoundDispatcher.java:139) at org.eclipse.jdt.internal.compiler.apt.dispatch.RoundDispatcher.round(RoundDispatcher.java:121) at org.eclipse.jdt.internal.compiler.apt.dispatch.BaseAnnotationProcessorManager.processAnnotations(BaseAnnotationProcessorManager.java:159) at org.eclipse.jdt.internal.apt.pluggable.core.dispatch.IdeAnnotationProcessorManager.processAnnotations(IdeAnnotationProcessorManager.java:134) at org.eclipse.jdt.internal.compiler.Compiler.processAnnotations(Compiler.java:810) at org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:428) at org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.compile(AbstractImageBuilder.java:364) at org.eclipse.jdt.internal.core.builder.IncrementalImageBuilder.compile(IncrementalImageBuilder.java:321) at org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.compile(AbstractImageBuilder.java:301) at org.eclipse.jdt.internal.core.builder.IncrementalImageBuilder.build(IncrementalImageBuilder.java:134) at org.eclipse.jdt.internal.core.builder.JavaBuilder.buildDeltas(JavaBuilder.java:265) at org.eclipse.jdt.internal.core.builder.JavaBuilder.build(JavaBuilder.java:193) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:627) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:170) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:201) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:253) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:256) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:309) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:341) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:140) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:238) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) This happens, if the AP examines a constraint annotation, which is not defined in the currently built project itself, but is imported from some other JAR (e.g. @Length from HV): public class TestModel { @Length private String test; } The problem occurs, regardless whether the JAR containing the constraint is on the AP classpath or not. The AP works as expected when running on javac. -- 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, 11 months

2
7
0 / 0

[Hibernate-JIRA] Created: (HHH-4436) Stackoverflow exception if Composite id has many to one relationship and fetchMode = EAGER

by Kirill Trofimov (JIRA)

Stackoverflow exception if Composite id has many to one relationship and fetchMode = EAGER ------------------------------------------------------------------------------------------ Key: HHH-4436 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4436 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.0.SP1 Environment: hibernate-core: 3.3.0.SP1, hibernate-annotations: 3.4.0.GA Reporter: Kirill Trofimov Attachments: hibernatetest.zip Stackoverflow occurred if composite id has many to one relationshipt. See unit test in attached file. -- 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, 11 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-4868) Upgrade to Javassist 3.11.GA

by Julien Kronegg (JIRA)

Upgrade to Javassist 3.11.GA ---------------------------- Key: HHH-4868 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4868 Project: Hibernate Core Issue Type: Improvement Affects Versions: 3.5.0-Beta-4, 3.3.2, 3.3.1 Reporter: Julien Kronegg Priority: Minor Hibernate 3.3.1 uses Javassist 3.4.GA (3.5 years old) Hibernate 3.3.2 uses Javassist 3.9.GA (1.5 years old) Hibernate 3.5.0 uses Javassist 3.9.GA (1.5 years old) -- 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, 11 months

4
7
0 / 0

[Hibernate-JIRA] Created: (HHH-4738) getSingleResult returning SQLException in DerbyDialect

by Samuel Halliday (JIRA)

getSingleResult returning SQLException in DerbyDialect ------------------------------------------------------ Key: HHH-4738 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4738 Project: Hibernate Core Issue Type: Bug Components: query-hql Affects Versions: 3.5.0-Beta-2 Environment: hibernate 3.5.0-0.2, Glassfish v3, Derby Reporter: Samuel Halliday I am encountering problems when issuing getSingleResult queries using the Glassfish v3 "hibernate 3.5.0-0.2". These queries work fine if I use hibernate 3.3.1.GA, or a PostgreSQL backend/dialect. Something between 3.3.1 and 3.5 has therefore introduced this bug. The queries are along the lines of [code] Query q = em.createQuery("SELECT COUNT(s) FROM MyTable s"); Long result = (Long) q.getSingleResult(); [/code] and [code] Query query = em.createQuery("SELECT s FROM MyTable s ORDER BY s.id"); query.setFirstResult(id); query.setMaxResults(1); MyTable random = (MyTable) query.getSingleResult(); [/code] The exception I am seeing is below, when used with (at least) the Java Derby DB. The message is "The column position '1' is out of range. The number of columns for this ResultSet is '0'." [code] Caused by: java.sql.SQLException: The column position '1' is out of range. The number of columns for this ResultSet is '0'. at org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(Unknown Source) at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source) at org.apache.derby.client.am.ColumnMetaData.getColumnType(Unknown Source) at org.apache.derby.client.am.PreparedStatement.setInt(Unknown Source) at org.hibernate.loader.Loader.bindLimitParameters(Loader.java:1669) at org.hibernate.loader.Loader.prepareQueryStatement(Loader.java:1594) at org.hibernate.loader.Loader.doQuery(Loader.java:694) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:257) at org.hibernate.loader.Loader.doList(Loader.java:2232) ... 42 more Caused by: org.apache.derby.client.am.SqlException: The column position '1' is out of range. The number of columns for this ResultSet is '0'. at org.apache.derby.client.am.ColumnMetaData.checkForValidColumnIndex(Unknown Source) ... 49 more [/code] -- 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, 11 months

4
7
0 / 0

[Hibernate-JIRA] Created: (HCANN-21) EnumType speed up in initEnumValues()

by Ondrej Medek (JIRA)

EnumType speed up in initEnumValues() ------------------------------------- Key: HCANN-21 URL: http://opensource.atlassian.com/projects/hibernate/browse/HCANN-21 Project: Hibernate Commons Annotations Issue Type: Patch Affects Versions: 3.1.0.GA, 3.2.x Environment: Hibernate 3.5.1, Sun JDK 1.6.0_18 Reporter: Ondrej Medek Priority: Minor Attachments: EnumType.java.patch Hi, I have simplified and sped up the method EnumType.initEnumValues(). See the attached patch. Tested on Sun JDK 1.6.0_18 Note 1: I do not know, why the author (Emmanuel Bernard?) has used reflection. Maybe the method Class.getEnumConstants() in not implemented by other JREs (IBM, BEA) or he just didn't know this method.? Note: the method getEnumConstants() in SUN JRE does use the reflection to look for method "values()", too, but it's results are cached, so the second call to the getEnumConstants() is fast. And because the results are cached inside the Enum class itself, it does not cause any memory leaks like HHH-4317. -- 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, 11 months

3
4
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 May 2010