April 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-5042) TableGenerator does not increment hibernate_sequences.next_hi_value anymore after having exhausted the current lo-range

by Guenther Demetz (JIRA)

TableGenerator does not increment hibernate_sequences.next_hi_value anymore after having exhausted the current lo-range ----------------------------------------------------------------------------------------------------------------------- Key: HHH-5042 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5042 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 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 Environment: Hibernate: 3.5 , db: HSQLDB (not relevant) Reporter: Guenther Demetz Priority: Critical Attachments: TestTableGenerator.java This bug is new in 3.5 In version 3.5 class MultipleHiLoPerTableGenerator.java was modified introducing a new increment variable IntegralDataTypeHolder value; along with int lo; The problem in the new code is that only value get's incremented whilst variable lo is still used to check when a new hiVal must be obtained. if ( lo > maxLo ) { IntegralDataTypeHolder hiVal = (IntegralDataTypeHolder) doWorkInNewTransaction( session ); as lo is never incremented, MultipleHiLoPerTableGenerator continues to deliver numbers without ever update hibernate_sequences.next_hi_value on the database (only one unique update is propagates at the first insert) This lead to duplicate keys as soon another session from another sessionfactory tries to insert new objects on the concerning table. Please see attached testcase. IMPORTANT ADVICE TO RUN THE TESTCASE: as the testcase uses 2 sessionfactories hibernate.hbm2ddl.auto=create cannot be used!! Schema has to be exported separately and the testcase must run without hbm2ddl.auto property! Here the schema for HSQLDB: create table A (oid bigint not null, name varchar(255), version integer not null, primary key (oid), unique (name)) create table hibernate_sequences ( sequence_name varchar(255), sequence_next_hi_value integer ) -- 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

6
18
0 / 0

[Hibernate-JIRA] Created: (HHH-4991) ManyToMany table not joined due to max_join_depth parameter, results to SQL exceptions

by Sergii Novotarskyi (JIRA)

ManyToMany table not joined due to max_join_depth parameter, results to SQL exceptions -------------------------------------------------------------------------------------- Key: HHH-4991 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4991 Project: Hibernate Core Issue Type: Bug Components: query-criteria Affects Versions: 3.5.0-CR-2 Environment: Hibernate 3.5.0-CR-2, MacOS X, MySQL 5.1 Reporter: Sergii Novotarskyi Attachments: Example.zip *max_join_depth* parameter prevents Hibernate from joining one end of ManyToMany relationship when using Criteria API, if the relationship is "far" enough from the root entity. {quote} Criteria c = session.createCriteria(SubEntity.class) .createAlias("entity", "e") // ManyToOne, inner join .createAlias("e.entity", "ee") // ManyToOne, inner join .createAlias("ee.sides", "s") // ManyToMany, inner join + left outer join .setProjection(Projections.count("id")) .add(Restrictions.ne("s.data", "abc")); {quote} When *max_join_depth* is set to *2* (default) the above example generates following SQL query {quote} select count(this_.sub_id) as y0_ from SubEntity this_ inner join SubMainEntity e1_ on this_.submain_id=e1_.submain_id inner join MainEntity ee2_ on e1_.main_id=ee2_.main_id inner join MainSide sides7_ on ee2_.main_id=sides7_.main_id where s3_.data<>? {quote} The query, naturally, throws the "Unknown column 's3_.data' in 'where clause'" exception. Expected query would be {quote} select count(this_.sub_id) as y0_ from SubEntity this_ inner join SubMainEntity e1_ on this_.submain_id=e1_.submain_id inner join MainEntity ee2_ on e1_.main_id=ee2_.main_id inner join MainSide sides7_ on ee2_.main_id=sides7_.main_id left outer join SideEntity s3_ on sides7_.side_id=s3_.side_id where s3_.data<>? {quote} -- 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-4957) Criteria Projections.countDistinct() function broken

by Lin Lai Fu (JIRA)

Criteria Projections.countDistinct() function broken ---------------------------------------------------- Key: HHH-4957 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4957 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0-CR-2 Environment: Hibernate: 3.5.0-CR-2 OS: Windows XP (should be OS independent) IDE: Eclipse 3.5 Galileo Reporter: Lin Lai Fu Priority: Blocker The criteria countDistinct() does not generate the correct query: criteria.setProjection(Projections.countDistinct("id")); generates: select count(id) instead of: select count(distinct id) This used to work in version 3.3.2-GA with toSqlString(). This method is missing in 3.5.0 Working version in 3.3.2-GA: http://viewvc.jboss.org/cgi-bin/viewvc.cgi/hibernate/core/trunk/core/src/... Broken version in 3.5.0: http://viewvc.jboss.org/cgi-bin/viewvc.cgi/hibernate/core/trunk/core/src/... See also the forum thread: http://forum.hibernate.org/viewtopic.php?f=1&t=1002910 -- 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
8
0 / 0

[Hibernate-JIRA] Created: (HHH-5125) The annotations @Entity and @MappedSuperclass used in one class produce a nullpointerexception

by Simone Rodenbach (JIRA)

The annotations @Entity and @MappedSuperclass used in one class produce a nullpointerexception ---------------------------------------------------------------------------------------------- Key: HHH-5125 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5125 Project: Hibernate Core Issue Type: Bug Components: annotations Affects Versions: 3.5.1 Environment: MS SQL Server Reporter: Simone Rodenbach Priority: Critical Caused by: java.lang.NullPointerException at org.hibernate.cfg.ClassPropertyHolder.addPropertyToMappedSuperclass(ClassPropertyHolder.java:133) at org.hibernate.cfg.ClassPropertyHolder.addPropertyToPersistentClass(ClassPropertyHolder.java:118) at org.hibernate.cfg.ClassPropertyHolder.addProperty(ClassPropertyHolder.java:98) at org.hibernate.cfg.ClassPropertyHolder.addProperty(ClassPropertyHolder.java:81) at org.hibernate.cfg.annotations.PropertyBinder.bind(PropertyBinder.java:246) at org.hibernate.cfg.annotations.PropertyBinder.makePropertyValueAndBind(PropertyBinder.java:200) at org.hibernate.cfg.AnnotationBinder.processElementAnnotations(AnnotationBinder.java:1979) at org.hibernate.cfg.AnnotationBinder.processIdPropertiesIfNotAlready(AnnotationBinder.java:762) at org.hibernate.cfg.AnnotationBinder.bindClass(AnnotationBinder.java:726) at org.hibernate.cfg.AnnotationConfiguration.processArtifactsOfType(AnnotationConfiguration.java:636) at org.hibernate.cfg.AnnotationConfiguration.secondPassCompile(AnnotationConfiguration.java:359) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1377) at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:954) -- 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
3
0 / 0

[Hibernate-JIRA] Created: (ANN-756) @Column annotation ignored when placed on entity's @Id property

by sagi mann (JIRA)

@Column annotation ignored when placed on entity's @Id property --------------------------------------------------------------- Key: ANN-756 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-756 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.1.GA Environment: hib core 3.2.6, my sql 5 Reporter: sagi mann Hibernate docs specify that when using a compound key class, a Hibernate optional feature is to place @Column annotations within the key class. The observed behavior is that Hibernate ignores @Column if placed ANYWHERE ELSE, for example, on the entity's ID properties. In other words, the standard JPA way of annotating ID fields is not working under Hibernate, and the "optional" feature is mandatory. Example how to reproduce (see comments inside the code regarding the inconsistency above). Accessors were omitted for clarity: // the identity class @Entity public class SecurityIdentity implements Serializable { public SecurityIdentity() {} @Id @Column(name="IDENTITY_ID") @GeneratedValue public Long getId() ... @Column(name="IDENTITY_NAME") public String getName() ... @Override public boolean equals(Object o) ... @Override public int hashCode() ... } // the domain class @Entity public class SecurityDomain implements Serializable { public SecurityDomain() {} @Id @Column(name="DOMAIN_ID") @GeneratedValue public Long getId() ... @Column(name="DOMAIN_NAME") public String getName() ... @Override public boolean equals(Object o) ... @Override public int hashCode() ... } // the domain-identity mapping class @Entity @IdClass(pu1.DomainIdentityPK.class) public class DomainIdentity implements Serializable { public DomainIdentity() {} @Id public Long getDomainId() ... @Id public String getUserAlias() ... @ManyToOne @JoinColumn(name="IDENTITY_ID") public SecurityIdentity getSecurityIdentity() ... @ManyToOne @JoinColumn(name="DOMAIN_ID", insertable=false, updatable=false) public SecurityDomain getSecurityDomain() { return securityDomain; } public void setSecurityDomain(SecurityDomain securityDomain) { this.securityDomain = securityDomain; this.domainId = (securityDomain != null ? securityDomain.getId() : null); } private SecurityDomain securityDomain; } // the map key class public class DomainIdentityPK implements Serializable { public DomainIdentityPK() { } /********* @Column inconsistency - cannot be placed inside the entity - only inside the PK class *******/ @Column(name="DOMAIN_ID") public Long getDomainId() ... [b]@Column(name="ALIAS")[/b] public String getUserAlias() ... public boolean equals(Object o) ... public int hashCode() ... } -- 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-2608) allow delete-orphan cascade style in one-to-one mapping

by Joe Kelly (JIRA)

allow delete-orphan cascade style in one-to-one mapping ------------------------------------------------------- Key: HHH-2608 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2608 Project: Hibernate3 Issue Type: New Feature Components: core Affects Versions: 3.2.4 Environment: 3.2.4, DB2 v8 Reporter: Joe Kelly Please allow the cascade-style "delete-orphan" for one-to-one relationships. When I try to use that cascade style, I get the exception "org.hibernate.MappingException: single-valued associations do not support orphan delete". I realize that the reference manual says "Note that single valued associations (many-to-one and one-to-one associations) do not support orphan delete." But why? I can think of many cases where you WOULD want parent-child semantics in a one-to-one relationship. For example, I have encountered some legacy databases where an entity has all of its fields stored in one table EXCEPT for an optional large field (e.g. a blob field) that is stored in another table, presumably for some performance or storage optimization reason. In this case the two tables are joined with a one-to-one relationship, using a shared primary key. Here are some hypothetical tables, classes and mappings that illustrate this example: company ( company_id (PK) name ) company_extra ( company_extra_id (PK), (FK referencing company.company_id) some_extra_info ) class Company { int companyId; String name; CompanyExtra companyExtra; } class CompanyExtra { int companyExtraId; String someExtraInfo; Company company; } <class name="Company" table="company"> <id name="companyId" column="company_id"> <generator class="sequence"> <param name="sequence">COMPANY_SEQ</param> </generator> </id> <property name="name" column="name" /> <one-to-one name="companyExtra" class="CompanyExtra" cascade="all, delete-orphan" /> </class> <class name="CompanyExtra" table="company_extra"> <id name="companyExtraId" column="company_extra_id" unsaved-value="null"> <generator class="foreign"> <param name="property">company</param> </generator> </id> <property name="someExtraInfo" column="some_extra_info" /> <one-to-one name="company" class="Company" constrained="true" /> </class> For the purposes of this example, CompanyExtra is a child of Company and belongs to one and only one instance of Company. It cannot be shared between Company instances and it cannot be an orphan (i.e. it cannot exist without a parent Company). Also, CompanyExtra is optional so you can have a Company without any associated CompanyExtra during Company's lifecycle. To me, it seems natural and logical that if you set Company.companyExtra to null, and save Company, Hibernate should automatically delete the associated record in the company_extra table if the delete-orphan cascade style is configured (which, of course, it not currently allowed). This is what I want to do when editing an existing Company instance: aCompany = session.load(...); aCompany.setCompanyExtra(null); aCompany.setName("some new name"); session.save(aCompany); // automatically deletes company_extra record For now, I think the workaround is to explicitly delete the CompanyExtra instance in Java code but that just doesn't seem natural to me and it isn't transparent. I do NOT want to do this: aCompany = session.load(...); companyExtra = aCompany.getCompanyExtra(); // ***extra, unnatural method call aCompany.setCompanyExtra(null); aCompany.setName("some new name"); session.save(aCompany); session.delete(companyExtra); // ***another extra, unnatural method call -- 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

17
20
0 / 0

[Hibernate-JIRA] Created: (ANN-573) Many-to-many with Attributes (Attribute-class with two @ManyToOne mappings as @Id) not possible

by Christian Köberl (JIRA)

Many-to-many with Attributes (Attribute-class with two @ManyToOne mappings as @Id) not possible ----------------------------------------------------------------------------------------------- Key: ANN-573 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-573 Project: Hibernate Annotations Type: Bug Components: binder Versions: 3.2.1 Environment: Hibernate+Annotations 3.2.1-ga, HSQLDB 1.8.0.7 Reporter: Christian Köberl Attachments: manytomanybug.zip Im trying to map the following relation: Order 1-n OrderLine m-1 Product where the OrderLine contains an amount of the ordered product. The problem seems to be multiple @Id in combination with @ManyToOne: @Entity @Table(name = "order_line") // @IdClass(OrderLinePK.class) public class OrderLine implements Serializable { @Id @ManyToOne(targetEntity = Order.class) @JoinColumn(name = "order_id", nullable = false) private Order order; @Id @ManyToOne(targetEntity = Product.class) @JoinColumn(name = "product_id", nullable = false) ... } Hibernate maps the OrderLine class in the following way: DEBUG SchemaUpdate:149 - create table order_line (product varbinary(255) not null, order varbinary(255) not null, amount integer, primary key (order)) (maybe this relates to http://opensource.atlassian.com/projects/hibernate/browse/ANN-435) When I add an IdClass to the OrderLine, I get the following exception: Initial SessionFactory creation failed.org.hibernate.AnnotationException: mappedBy reference an unknown target entity property: model.OrderLine.order in model.Order.lineItems The example is attached as a runnable Maven2-Project, just run mvn test. The test dao.OrderDaoAnnotationTest fails. In the project I also tried to map the same classes with hbm-Files and this works (dao.OrderDaoHbmTest). -- 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
7
0 / 0

[Hibernate-JIRA] Created: (HHH-4744) Incorrect audit entity for TABLE_PER_CLASS with abstract classes (results in query error)

by Volker Schmidt (JIRA)

Incorrect audit entity for TABLE_PER_CLASS with abstract classes (results in query error) ----------------------------------------------------------------------------------------- Key: HHH-4744 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4744 Project: Hibernate Core Issue Type: Bug Components: envers Affects Versions: 3.5.0-Beta-2, 3.2.0.ga Reporter: Volker Schmidt Attachments: envers-1.2.2.ga-hibernate-3.3.patch, trunk.patch The configuration code of Envers does not check the abstract flag of a PersistentClass. Thus the created audit entity is not declared as being abstract. Abstract entities do not have concrete tables. Without declaring the audit entity of a super class as being abstract, queries include a table (that does not exist) for the abstract super class. I have added a patch for the trunk and for Envers 1.2.2. -- 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
2
0 / 0

[Hibernate-JIRA] Created: (HHH-4078) EntityMetamodel#entityNameByInheritenceClassNameMap mapping from class or class names?

by Tsering Shrestha (JIRA)

EntityMetamodel#entityNameByInheritenceClassNameMap mapping from class or class names? -------------------------------------------------------------------------------------- Key: HHH-4078 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4078 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.5 Reporter: Tsering Shrestha In the constructor of EntityMetaModel (http://anonsvn.jboss.org/repos/hibernate/core/trunk/core/src/main/java/or... revision 15258) Line 314: if ( persistentClass.hasPojoRepresentation() ) { entityNameByInheritenceClassNameMap.put( persistentClass.getMappedClass(), persistentClass.getEntityName() ); However at Line 578: public String findEntityNameByEntityClass(Class inheritenceClass) { return ( String ) entityNameByInheritenceClassNameMap.get( inheritenceClass.getName() ); } Why are we using java.lang.Class as the keys when we put new entries to the map but try to read with java.lang.String keys? -- 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
5
0 / 0

[Hibernate-JIRA] Created: (HHH-4438) It is impossible to override RelationTargetAuditMode using AuditOverride

by Eugene Goroschenya (JIRA)

It is impossible to override RelationTargetAuditMode using AuditOverride ------------------------------------------------------------------------ Key: HHH-4438 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4438 Project: Hibernate Core Issue Type: Bug Components: envers Affects Versions: 3.5.0.Beta-1, 3.3.2, 3.3.x, 3.5 Reporter: Eugene Goroschenya The implementation of HHH-4010 provides great feature: support auditing of entity having reference (many-to-one relation) to not audited entity But it is still impossible to use it with @Embedded to override RelationTargetAuditMode for some reference(s) in @Embeddable 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
3
0 / 0

[Hibernate-JIRA] Created: (HHH-4626) OneToMany cascadeType.ALL change collection and merge - does not remove entities

by Dave (JIRA)

OneToMany cascadeType.ALL change collection and merge - does not remove entities --------------------------------------------------------------------------------- Key: HHH-4626 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4626 Project: Hibernate Core Issue Type: Bug Components: entity-manager Affects Versions: 3.3.1 Environment: JBoss 5.1.0.GA, FC 10, Java 1.6 Reporter: Dave public Class Foo { @OneToMany(fetch=FetchType.LAZY, cascade={CascadeType.ALL}, mappedBy="foo") public List<Bar> getBars() { return bars; } } // aFoo is persited Foo aFoo = ... aFoo.getBars().remove(0); // remove the first aFoo.getBars().add(aBar); // add new one em.merge(aFoo); For cascade={CascadeType.ALL}, it works for creating/deleting aFoo. For merge, the new aBar is created, but the bar that was removed from collection are not deleted from persistence. -- 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
6
0 / 0

[Hibernate-JIRA] Created: (HHH-3940) Remove hasSelfReferentialForeignKeyBug (returning true) override from MySQL dialects

by Steve Ebersole (JIRA)

Remove hasSelfReferentialForeignKeyBug (returning true) override from MySQL dialects ------------------------------------------------------------------------------------ Key: HHH-3940 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3940 Project: Hibernate Core Issue Type: Task Components: core Affects Versions: 3.3.1, 3.2.7 Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.2.x, 3.3.x, 3.5 Previous versions of MySQL had a nasty bug when using self-referential foreign keys with the innodb storage engine. This Dialect#hasSelfReferentialForeignKeyBug was originally added to account for that. Testing against the lastest (5.1) MySQL versions shows this to no longer be present. -- 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-3995) Cleanup test data

by Steve Ebersole (JIRA)

Cleanup test data ----------------- Key: HHH-3995 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3995 Project: Hibernate Core Issue Type: Task Components: testsuite Reporter: Steve Ebersole Assignee: Steve Ebersole Priority: Minor Fix For: 3.2.x, 3.3.x, 3.5 Lots of tests are leaving test data hanging around. That works on a particular assumption wrt the execution order of tests or that only a single test method exists. That cuases problems later in many cases. All tests should clean up the test data they create. Currently on trunk I see 246 tests leaving data around. The sys prop hibernate.test.validateDataCleanup can be used to check for this; set it to true. -- 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-2439) delay IDENTITY insertions in the case of FlushMode.MANUAL/NEVER

by Steve Ebersole (JIRA)

delay IDENTITY insertions in the case of FlushMode.MANUAL/NEVER --------------------------------------------------------------- Key: HHH-2439 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2439 Project: Hibernate3 Type: Improvement Components: core Reporter: Steve Ebersole Assigned to: Steve Ebersole Fix For: 3.2.3 Much like we do now in 3.2 for out of transaction operations, we should delay performing insertions for post-insert generators with FlushMode.isManualFlushMode -- 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
20
0 / 0

[Hibernate-JIRA] Created: (HHH-4706) Leverage new o.h.dialect.function.TrimFunctionTemplate and o.h.dialect.function.AnsiTrimFunction classes

by Steve Ebersole (JIRA)

Leverage new o.h.dialect.function.TrimFunctionTemplate and o.h.dialect.function.AnsiTrimFunction classes -------------------------------------------------------------------------------------------------------- Key: HHH-4706 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4706 Project: Hibernate Core Issue Type: Improvement Components: core, query-hql Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.5 o.h.dialect.function.TrimFunctionTemplate defines basic support for understanding which trim options were specified. o.h.dialect.function.AnsiTrimFunction defines rendering of a trim function using the ANSI SQL defined syntax. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-3946) Test FooBarTest isn't opening transactions and contains an invalid assertion

by Juraci Paixao Krohling (JIRA)

Test FooBarTest isn't opening transactions and contains an invalid assertion ---------------------------------------------------------------------------- Key: HHH-3946 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3946 Project: Hibernate Core Issue Type: Bug Components: testsuite Reporter: Juraci Paixao Krohling Assignee: Juraci Paixao Krohling Fix For: 3.5 Attachments: FooBarTest.java.diff Test FooBarTest have three tests failing: - testDisconnect - testOrderBy - testVeto All of them are issuing commit to transactions which were not started, causing "Transaction not successfully started" error. Also, the test testOrderBy contains an invalid assertion. The code reads: assertEquals( "'b' isn't second element", "b", ( (One) results.get(2) ).getValue() ); But as the method "get" is 0-indexed, the parameter should be 1, instead of 2. The attached patch fixes those issues. -- 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
8
0 / 0

[Hibernate-JIRA] Created: (HHH-4035) skip org.hibernate.action.BulkOperationCleanupAction on INSERT HQL queries

by Steve Ebersole (JIRA)

skip org.hibernate.action.BulkOperationCleanupAction on INSERT HQL queries -------------------------------------------------------------------------- Key: HHH-4035 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4035 Project: Hibernate Core Issue Type: Improvement Components: caching (L2) Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.3.x, 3.5 For INSERT queries it is really not needed to cleanup caches as we'd have no invalid entity/collection data to cleanup (we'd still nee to invalidate the appropriate update-timestamps regions) as a result of 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
6
0 / 0

[Hibernate-JIRA] Created: (HHH-4885) Use "test" durability mode for derby database in testssuites

by Steve Ebersole (JIRA)

Use "test" durability mode for derby database in testssuites ------------------------------------------------------------ Key: HHH-4885 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4885 Project: Hibernate Core Issue Type: Improvement Components: testsuite Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.5.0-Next Very similar to Oracle's NOLOG option. {quote} While performance is improved, note that under these conditions, a commit no longer guarantees that the transaction's modification will survive a system crash or JVM termination, the database may not recover successfully upon restart, a near-full disk at runtime may cause unexpected errors, and the database may be in an inconsistent state. {quote} http://publib.boulder.ibm.com/infocenter/cscv/v10r1/index.jsp?topic=/com.... -- 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-5052) EventListenerConfigurator uses Ejb3Configuration but could use AnnotationConfiguration instead

by Alexandre Walter Pretyman (JIRA)

EventListenerConfigurator uses Ejb3Configuration but could use AnnotationConfiguration instead ---------------------------------------------------------------------------------------------- Key: HHH-5052 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5052 Project: Hibernate Core Issue Type: Improvement Components: annotations, entity-manager Affects Versions: 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: Tested with Hibernate 3.2.6ga, Annotations 3.2.1ga, EntityManager 3.3.2ga but seems to affect the code in the trunk. Reporter: Alexandre Walter Pretyman Priority: Trivial The class EventListenerConfigurator uses Ejb3Configuration on it's constructor, but it could use AnnotationConfiguration directly, as the methods called on the Ejb3Configuration instance by the EventListenerConfigurator, are actually delegations to the AnnotationConfiguration . -- 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
9
0 / 0

[Hibernate-JIRA] Created: (HHH-2309) fetch only the lazy property needed

by German de la Cruz (JIRA)

fetch only the lazy property needed ------------------------------------ Key: HHH-2309 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2309 Project: Hibernate3 Type: New Feature Components: core Versions: 3.2.1 Reporter: German de la Cruz The method AbstractEntityPersister.initializeLazyProperty(..) load all lazy properties when it's called. It would be great if could only load the requested property. I think the only change we need is in AbstractEntityPersister.initializeLazyPropertiesFromDatastore(...) and AbstractEntityPersister.initializeLazyPropertiesFromCache(...). We must change them in a way that only the referenced property is loaded. After that, we must change AbstractFieldInterceptor.intercept(..) to update in a better way the unitializedFields collection (I mean, removing the actual property only instead of null it). Besides. Why in line 777 to 780 a query is executed? I think it isn't necessary. Thanks. -- 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
12
0 / 0

[Hibernate-JIRA] Created: (HHH-5123) Brazilian translations

by Steve Ebersole (JIRA)

Brazilian translations ---------------------- Key: HHH-5123 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5123 Project: Hibernate Core Issue Type: Patch Components: core, documentation Affects Versions: 3.5.0-Final Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.5.x Grouping of a series of patches for the Brazilian doc translations -- 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
6
0 / 0

[Hibernate-JIRA] Created: (HHH-4903) Ambiguous column in field list

by Luis Eduardo Villares Matta (JIRA)

Ambiguous column in field list ------------------------------ Key: HHH-4903 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4903 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0-Beta-4 Environment: O.S.: Linux 2.6.28-18-generic #59-Ubuntu SMP Thu Jan 28 01:40:19 UTC 2010 x86_64 GNU/Linux Java.: Java HotSpot(TM) 64-Bit Server VM (build 14.2-b01, mixed mode) Web server: jetty-hightide-7.0.1.v20091125 DB Server: mysql Ver 14.14 Distrib 5.1.31, for debian-linux-gnu (x86_64) using EditLine wrapper Reporter: Luis Eduardo Villares Matta Priority: Blocker When executing entityManager.find(ClassName.class, pk) caught the exception below. Entities involved in the query below do not have any inheritance relationship (just composition), but they all contain a field named "private" (column name "_private") Hibernate: select libraryite0_.id as id2_2_, libraryite0_.active as active2_2_, libraryite0_.createdDate as createdD3_2_2_, libraryite0_.deleted as deleted2_2_, libraryite0_.updatedDate as updatedD5_2_2_, libraryite0_.defaultLocale as defaultL6_2_2_, libraryite0_.name as name2_2_, libraryite0_.parentId as parentId2_2_, _private as column8_2_2_, libraryite0_.typeId as typeId2_2_, libraryite1_.id as id2_0_, libraryite1_.active as active2_0_, libraryite1_.createdDate as createdD3_2_0_, libraryite1_.deleted as deleted2_0_, libraryite1_.updatedDate as updatedD5_2_0_, libraryite1_.defaultLocale as defaultL6_2_0_, libraryite1_.name as name2_0_, libraryite1_.parentId as parentId2_0_, _private as column8_2_0_, libraryite1_.typeId as typeId2_0_, libraryite2_.id as id5_1_, libraryite2_.active as active5_1_, libraryite2_.createdDate as createdD3_5_1_, libraryite2_.deleted as deleted5_1_, libraryite2_.updatedDate as updatedD5_5_1_, libraryite2_.folderish_ as folderish6_5_1_, libraryite2_.libraryId as libraryId5_1_, libraryite2_.name as name5_1_, libraryite2_.xsd_ as xsd8_5_1_, libraryite2_.xpaths_ as xpaths9_5_1_ from TKBMLibraryItem libraryite0_ left outer join TKBMLibraryItem libraryite1_ on libraryite0_.parentId=libraryite1_.id left outer join TKBMLibraryItemType libraryite2_ on libraryite1_.typeId=libraryite2_.id where libraryite0_.id=? 174363 [qtp1469937134-21] WARN org.hibernate.util.JDBCExceptionReporter - SQL Error: 1052, SQLState: 23000 174363 [qtp1469937134-21] ERROR org.hibernate.util.JDBCExceptionReporter - Column '_private' in field list is ambiguous 174363 [qtp1469937134-21] INFO org.hibernate.event.def.DefaultLoadEventListener - Error performing load command org.hibernate.exception.ConstraintViolationException: could not load an entity: [com.totvs.kbm.model.LibraryItemModel#10128] at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:95) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66) at org.hibernate.loader.Loader.loadEntity(Loader.java:1916) at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:71) at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:65) at org.hibernate.persister.entity.AbstractEntityPersister.load(AbstractEntityPersister.java:3212) at org.hibernate.event.def.DefaultLoadEventListener.loadFromDatasource(DefaultLoadEventListener.java:437) at org.hibernate.event.def.DefaultLoadEventListener.doLoad(DefaultLoadEventListener.java:418) at org.hibernate.event.def.DefaultLoadEventListener.load(DefaultLoadEventListener.java:165) at org.hibernate.event.def.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:223) at org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:126) at org.hibernate.impl.SessionImpl.fireLoad(SessionImpl.java:1080) at org.hibernate.impl.SessionImpl.get(SessionImpl.java:997) at org.hibernate.impl.SessionImpl.get(SessionImpl.java:990) at org.hibernate.ejb.AbstractEntityManagerImpl.find(AbstractEntityManagerImpl.java:538) at org.hibernate.ejb.AbstractEntityManagerImpl.find(AbstractEntityManagerImpl.java:513) at com.totvs.kbm.service.KnowledgeService.getLibraryItem(KnowledgeService.java:476) at org.apache.jsp.html.kbm.rootitemsnavigation_jsp._jspService(org.apache.jsp.html.kbm.rootitemsnavigation_jsp:179) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:109) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:389) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:486) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:380) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:530) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1216) at com.totvs.kbm.core.web.RequestPipeline.doFilter(RequestPipeline.java:132) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1187) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:425) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:119) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:457) at org.eclipse.jetty.server.session.SessionHandler.handle(SessionHandler.java:182) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:933) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:362) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:867) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117) at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:245) at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:126) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:113) at org.eclipse.jetty.server.Server.handle(Server.java:334) at org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:559) at org.eclipse.jetty.server.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:992) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:541) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:203) at org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:406) at org.eclipse.jetty.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:462) at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:436) at java.lang.Thread.run(Thread.java:619) Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Column '_private' 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:406) at com.mysql.jdbc.Util.getInstance(Util.java:381) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1015) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:956) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3558) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3490) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1959) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2109) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2648) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2077) at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:2228) at org.hibernate.jdbc.AbstractBatcher.getResultSet(AbstractBatcher.java:208) at org.hibernate.loader.Loader.getResultSet(Loader.java:1827) at org.hibernate.loader.Loader.doQuery(Loader.java:714) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:271) at org.hibernate.loader.Loader.loadEntity(Loader.java:1902) ... 45 more 2010-02-10 14:48:50.375:WARN::/html/kbm/rootitemsnavigation.jsp javax.persistence.PersistenceException: org.hibernate.exception.ConstraintViolationException: could not load an entity: [com.totvs.kbm.model.LibraryItemModel#10128] at org.hibernate.ejb.AbstractEntityManagerImpl.convert(AbstractEntityManagerImpl.java:1197) at org.hibernate.ejb.AbstractEntityManagerImpl.find(AbstractEntityManagerImpl.java:558) at org.hibernate.ejb.AbstractEntityManagerImpl.find(AbstractEntityManagerImpl.java:513) at com.totvs.kbm.service.KnowledgeService.getLibraryItem(KnowledgeService.java:476) at org.apache.jsp.html.kbm.rootitemsnavigation_jsp._jspService(org.apache.jsp.html.kbm.rootitemsnavigation_jsp:179) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:109) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:389) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:486) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:380) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:530) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1216) at com.totvs.kbm.core.web.RequestPipeline.doFilter(RequestPipeline.java:132) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1187) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:425) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:119) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:457) at org.eclipse.jetty.server.session.SessionHandler.handle(SessionHandler.java:182) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:933) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:362) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:867) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117) at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:245) at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:126) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:113) at org.eclipse.jetty.server.Server.handle(Server.java:334) at org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:559) at org.eclipse.jetty.server.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:992) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:541) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:203) at org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:406) at org.eclipse.jetty.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:462) at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:436) at java.lang.Thread.run(Thread.java:619) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-4624) QueryImpl.list() closes connection

by Dieter Freismuth (JIRA)

QueryImpl.list() closes connection ---------------------------------- Key: HHH-4624 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4624 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.2 Environment: linux, postgres 8.3 (same on oracle 11g, mssql 2005 and mysql) Reporter: Dieter Freismuth Priority: Critical if an outer query.iterate() calls within an iteration step a query.list() the connection is closed and the next outer iteration step causes: org.hibernate.exception.JDBCConnectionException: could not get next iterator result at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:97) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:52) at org.hibernate.impl.IteratorImpl.next(IteratorImpl.java:156) the exception is only thrown if there is no transaction! (works fine if done within an transaction) call hierarchy: QueryImpl.list() -> SessionImpl.list(String query, QueryParameters queryParameters) -> afterOperation(success); // within finally block -> JDBCContext.afterNontransactionalQuery( success ) -> ConnectionManager.afterTransaction() -> ConnectionManager.aggressiveRelease() // within if ( isAfterTransactionRelease() ) { -> ConnectionManager.closeConnection() -- 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
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3077) Move references to LRUMap and ReferenceMap

by Stephen Kestle (JIRA)

Move references to LRUMap and ReferenceMap ------------------------------------------ Key: HHH-3077 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3077 Project: Hibernate3 Issue Type: Sub-task Reporter: Stephen Kestle -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

2
3
0 / 0

[Hibernate-JIRA] Erstellt: (HHH-2224) executeUpdate causes coarse cache invalidation

by Stefan Fleiter (JIRA)

executeUpdate causes coarse cache invalidation ---------------------------------------------- Key: HHH-2224 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2224 Project: Hibernate3 Type: Improvement Versions: 3.2.0.ga Environment: Hibernate 3.2.0.ga, Oracle 9.2 Reporter: Stefan Fleiter Attachments: bulk_testcase.zip I am developing an application and want to mix bulk-updates with normal hibernate operations. The bulk updates work fine, but invalidate the whole region and I've found no possibility to prevent this. There would be 3 options to improve: - Invalidate only the modified objects if the ids where given as Query-parameters. - Let me deactivate the invalidation so I can invalidate the affected objects myself. - Transform the DML to a select to gather the objects to invalidate before executing the DML The reference documentation does not mention caching at all: http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#batch-direct The best documentation I've found is: http://blog.hibernate.org/cgi-bin/blosxom.cgi/2005/07/19#dml-basic Maybe this could be added to the reference documentation... I already posted this at the forum http://forum.hibernate.org/viewtopic.php?t=966775 but did not get a single answer. I've attached a testcase for this. -- 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

10
19
0 / 0

[Hibernate-JIRA] Created: (HHH-4832) Secondary tables do not work in JOINED or TABLE_PER_CLASS inheritance strategies

by Simon Godden (JIRA)

Secondary tables do not work in JOINED or TABLE_PER_CLASS inheritance strategies -------------------------------------------------------------------------------- Key: HHH-4832 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4832 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.2 Environment: Hibernate 3.3.2, Postgres 8.4.2 Reporter: Simon Godden Attachments: hibernatetest2.tgz I have a class hierarchy as follows: {noformat} Abstract RootClass (Mapped Superclass) | \ / Abstract IntermediateClass (Entity) | | \ / \ / LeafClass (Entity) LeafClass2 (Entity) {noformat} The following table shows which attributes are on each class: ||Class||Attribute||Table|| |RootClass|field1|rootclass| |IntermediateClass|field2|intermediateclass| |LeafClass|field3|leafclass| |LeafClass|field4|leafclass2| |AnotherLeafClass|field5|anotherleafclass| |AnotherLeafClass|field6|anotherleafclass2| Using {{InheritanceType.SINGLE_TABLE}}, it works. Using {{InheritanceType.JOINED}} or {{InheritanceType.TABLE_PER_CLASS}} at the {{IntermediateClass}} level causes different errors: Using {{InheritanceType.JOINED}} causes an incorrect insert statement which thinks that {{field4}} is on table {{leafclass}} rather than {{leafclass2}}: {noformat} Hibernate: insert into LeafClass (field1, field2, field3, field4, id) values (?, ?, ?, ?, ?) Exception in thread "main" [22/01/10 03:17:53:053 GMT] WARN util.JDBCExceptionReporter: SQL Error: 0, SQLState: null [22/01/10 03:17:53:053 GMT] ERROR util.JDBCExceptionReporter: Batch entry 0 insert into LeafClass (field1, field2, field3, field4, id) values (foo1, foo2, foo3, foo4, 1) was aborted. Call getNextException to see the cause. [22/01/10 03:17:53:053 GMT] WARN util.JDBCExceptionReporter: SQL Error: 0, SQLState: 42703 [22/01/10 03:17:53:053 GMT] ERROR util.JDBCExceptionReporter: ERROR: column "field4" of relation "leafclass" does not exist {noformat} Using {{InheritanceType.TABLE_PER_CLASS}} causes the following error as the session factory is built: {noformat} [22/01/10 03:06:05:005 GMT] INFO cfg.SettingsFactory: Echoing all SQL to stdout [22/01/10 03:06:05:005 GMT] INFO cfg.SettingsFactory: Statistics: disabled [22/01/10 03:06:05:005 GMT] INFO cfg.SettingsFactory: Deleted entity synthetic identifier rollback: disabled [22/01/10 03:06:05:005 GMT] INFO cfg.SettingsFactory: Default entity-mode: pojo [22/01/10 03:06:05:005 GMT] INFO cfg.SettingsFactory: Named query checking : enabled [22/01/10 03:06:05:005 GMT] INFO impl.SessionFactoryImpl: building session factory [22/01/10 03:06:06:006 GMT] ERROR hibernate.AssertionFailure: an assertion failure occured (this may indicate a bug in Hibernate, but is more likely due to unsafe use of the session) org.hibernate.AssertionFailure: Table leafclass2 not found at org.hibernate.persister.entity.JoinedSubclassEntityPersister.getTableId(JoinedSubclassEntityPersister.java:480) at org.hibernate.persister.entity.JoinedSubclassEntityPersister.<init>(JoinedSubclassEntityPersister.java:259) at org.hibernate.persister.PersisterFactory.createClassPersister(PersisterFactory.java:87) at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:267) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1341) at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:867) at tests.inheritdomain.SessionManager.initialiseSessionFactory(SessionManager.java:23) at tests.inheritdomain.SessionManager.openSession(SessionManager.java:14) at tests.inheritdomain.TestSecondaryTablesInInheritance.test(TestSecondaryTablesInInheritance.java:20) at tests.inheritdomain.TestSecondaryTablesInInheritance.main(TestSecondaryTablesInInheritance.java:44){noformat} A minimal test case is attached as an maven and eclipse project. mvn test will show the error. I have not created a test case for each inheritance type - you will have to change it in the intermediate domain class to see the other error. -- 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-2470) Use of session.createSQLQuery causes memory leak

by Bjørn Bjerkeli (JIRA)

Use of session.createSQLQuery causes memory leak ------------------------------------------------- Key: HHH-2470 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2470 Project: Hibernate3 Type: Bug Components: query-sql Versions: 3.1.3 Environment: Win XP, Oracle 10g, Java 1.4.2 Reporter: Bjørn Bjerkeli Attachments: TestCase.zip NativeSQLQuerySpecification fails to properly implement equals and hashcode caused by lacking implementation of hashCode and equals in all SQLQueryReturn implementations and SQLQueryScalarReturn which are members of NativeSQLQuerySpecification. I can see that NativeSQLQuerySpecification has been changed in 3.2, but the problem is still there. NativeSQLQuerySpecification instances are used as keys for retrieving and caching NativeSQLQueryPlan instances. This causes the caching-mechanism to be pretty useless when Queries created by session.createSQLQuery because new entries will be added all the time in the QueryPlanCache and the SoftLimitMRUCache member. So far so good, the more serious problem that is caused by this is stems from the implementation of SoftLimitMRUCache which again uses LRUMap in commons-collection. The put - method of the cache is not treadsafe, and that causes the following fragment in LRUMap to allow the map to grow beyond its maximumSize. That is bacause the containsKey method will return an incorrect result when concurrently updating the map. public Object put( Object key, Object value ) { int mapSize = size(); Object retval = null; if ( mapSize >= maximumSize ) { // don't retire LRU if you are just // updating an existing key if (!containsKey(key)) { // lets retire the least recently used item in the cache removeLRU(); } } retval = super.put(key,value); return retval; } I have included a test-case that demonstrates: 1) Wrong implementation of equals and hashCode in NativeSQLQuerySpecification 2) Concurrent use of LRUMap causes the map to grow beyound it's max limit 3) Concurrent execution of session.createSQLQuery causes memory leak due to 1) and 2) I would be more than happy to contribute to get this fixed. Just let me know. -- 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

14
23
0 / 0

[Hibernate-JIRA] Created: (HHH-3221) Cascading performance problems when session contains many entities

by Yves Galante (JIRA)

Cascading performance problems when session contains many entities ------------------------------------------------------------------ Key: HHH-3221 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3221 Project: Hibernate3 Issue Type: Improvement Components: core Affects Versions: 3.3.0.CR1, 3.2.6, 3.2.5 Reporter: Yves Galante Attachments: patchCascading.patch, SaveTest.zip When session contains many entities, performence of cascading become very slow. For each collection element the whole persistence context is searched (by StatefulPersistenceContext#getIndexInOwner() and StatefulPersistenceContext#getOwnerId) and its even searched twice when the collection is an indexed collection. This patch optimize cascading operation by caching relation parent-child on a map. eventSource.getPersistenceContext().addChildParent(child, parent); action.cascade(eventSource, child, entityName, anything, isCascadeDeleteEnabled); eventSource.getPersistenceContext().removeChildParent(child); The test case save and flush 10 * 551 objects. Before patch save object with cascading is more slow when session size grows. After patch time of save stay same at each loop. Output of the test case before the patch : Save took 449 ms Save took 669 ms Save took 1042 ms Save took 1464 ms Save took 2481 ms Save took 2741 ms Save took 3807 ms Save took 4344 ms Save took 4975 ms Save took 5251 ms Total took 30906 ms Output after the patch Save took 445 ms Save took 144 ms Save took 164 ms Save took 108 ms Save took 93 ms Save took 93 ms Save took 93 ms Save took 94 ms Save took 91 ms Save took 89 ms Total took 4905 ms -- 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
10
0 / 0

[Hibernate-JIRA] Created: (ANN-793) @ManyToOne - @OneToMany doesn't work with @Inheritance(strategy= InheritanceType.JOINED)

by Tomaz Cerar (JIRA)

@ManyToOne - @OneToMany doesn't work with @Inheritance(strategy= InheritanceType.JOINED) ---------------------------------------------------------------------------------------- Key: ANN-793 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-793 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.4.0.GA Environment: Hibernate Core 3.3.1.GA Hibernate Annotations 3.4.0 GA Hibernate EntityManager 3.4.0 GA Jboss 4.3 EAP, DB2 9.5 Reporter: Tomaz Cerar I am trying to create bidirectional association between two entities in which one can be Inherited and it fails with table not found: 11:37:39,229 ERROR [AssertionFailure] [] an assertion failure occured (this may indicate a bug in Hibernate, but is more likely due to unsafe use of the session) org.hibernate.AssertionFailure: Table CRM.CRM_AKTIVNOST_DOGODKI not found at org.hibernate.persister.entity.JoinedSubclassEntityPersister.getTableId(JoinedSubclassEntityPersister.java:480) at org.hibernate.persister.entity.JoinedSubclassEntityPersister.<init>(JoinedSubclassEntityPersister.java:259) at org.hibernate.persister.PersisterFactory.createClassPersister(PersisterFactory.java:87) at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:261) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1327) at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:867) at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:669) at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:132) at org.jboss.ejb3.entity.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:246) The code looks like this: @Entity @Table(name = "CRM_AKTIVNOST") public class Aktivnost implements Serializable { private List<Dogodek> dogodki; .... .... @OneToMany(fetch = FetchType.LAZY, cascade = CascadeType.ALL,mappedBy = "aktivnost") public List<Dogodek> getDogodki() { return dogodki; } public void setDogodki(List<Dogodek> dogodki) { this.dogodki = dogodki; } ... ... } @Entity @Table(name = "CRM_DOGODEK") @Inheritance(strategy= InheritanceType.JOINED) public class Dogodek implements Serializable { ... ... private Aktivnost aktivnost; .... .... @ManyToOne(fetch = FetchType.LAZY, cascade = CascadeType.ALL) @JoinTable(name = "CRM_AKTIVNOST_DOGODKI", joinColumns = {@JoinColumn(name = "DOGODEK_ID")}, inverseJoinColumns = {@JoinColumn(name = "AKTIVNOST_ID")}) public Aktivnost getAktivnost() { return aktivnost; } public void setAktivnost(Aktivnost aktivnost) { this.aktivnost = aktivnost; } ... } -- 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

9
12
0 / 0

[Hibernate-JIRA] Created: (HHH-4716) NotAuditedException using the entity name concept of hibernate.

by Subhan (JIRA)

NotAuditedException using the entity name concept of hibernate. ---------------------------------------------------------------- Key: HHH-4716 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4716 Project: Hibernate Core Issue Type: Bug Components: envers Affects Versions: 3.5.0-Beta-2 Environment: hibernate-envers-3.5.0-Beta-2 and hibernate-core-3.3.2.GA DB : Oracle XE Reporter: Subhan Priority: Blocker Attachments: SimpleHibernateEnversExample.rar I'm trying to use the entity name concept of hibernate, it saves/updates/deletes the data and audit data properly. When trying to read the audited information its getting NotAuditedException error. For reading the audited information , it would be great to have the support of entity name concepts as hibernate. Sample project is added as attachment.(Which is having sample test case). -- 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-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-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-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-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-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-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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues April 2010