May 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-3160) Support one-to-many list associations with constraints on both (owner_id, position) and (child_id)

by Gail Badner (JIRA)

Support one-to-many list associations with constraints on both (owner_id, position) and (child_id) -------------------------------------------------------------------------------------------------- Key: HHH-3160 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3160 Project: Hibernate3 Issue Type: Sub-task Reporter: Gail Badner Assignee: Gail Badner The logic used for removing entities from one-to-many list associations can cause ConstraintViolationException will be thrown if there are constraints on both (owner_id, position) and (child_id) in the "collection table". If the association is on a join table, the "collection table" is the join table; otherwise, the "collection table" is the child entity table.. Currently, SchemaExport does not put a constraint on (owner_id, position) when exporting one-to-many list associations on a foreign key. SchemaExport should be updated to also export this constraint. See HHH-1268 for a description of how to reproduce this issue. For one-to-many list associations on a foreign key, the workaround is to either define the constraint on (owner_id, position) in the child entity table as deferred. If this is not on option for a particular Dialect, the constraint on (owner_id, position) will have to be excluded. For a one-to-many list association on a join table, the workaround is to either define the constraint on (child_id) in the join table as deferred. If this is not on option for a particular Dialect, the constraint on (child_id) will have to be excluded. -- 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

14 years, 8 months

4
6
0 / 0

[Hibernate-JIRA] Created: (HHH-5146) org.hibernate.util.IdentitySet.iterator() return Map.Entry instances instead of actual elements

by Nicklas Nordborg (JIRA)

org.hibernate.util.IdentitySet.iterator() return Map.Entry instances instead of actual elements ----------------------------------------------------------------------------------------------- Key: HHH-5146 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5146 Project: Hibernate Core Issue Type: Bug Components: core Reporter: Nicklas Nordborg Priority: Trivial Attachments: patch.txt By accident I used the IdentitySet implementation in my code and got ClassCastException:s when iterating over it. It turns out that the iterator() method returns Map.entrySet().iterator() instead of Map.keySet().iterator(). There is also a similar problem with the toArray() methods. I provide a patch. -- 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

14 years, 8 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3404) Regular expressions (regex) boolean operator in HQL's where clause: rlike in mysql, regexp_match in informix, ... (regression from hibernate2)

by Geoffrey De Smet (JIRA)

Regular expressions (regex) boolean operator in HQL's where clause: rlike in mysql, regexp_match in informix, ... (regression from hibernate2) ---------------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-3404 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3404 Project: Hibernate3 Issue Type: New Feature Components: query-hql Affects Versions: 3.2.6 Reporter: Geoffrey De Smet Hibernate 2 supported the rlike boolean operator (at least for mysql): HB-1034. Hibernate3 currently doesn't. It turns out that most mainstream databases support regular expression patterns (independently from normal like patterns). Mysql: rlike where a.serial rlike '\d*' Informix: regexp_match() where regexp_match(a.serial, '\d*') Oracle: REGEXP_LIKE where REGEXP_LIKE(a.serial, '\d*') There have been several forum posts asking about this feature for hibernate3 btw: http://forum.hibernate.org/viewtopic.php?p=2391395 http://forum.hibernate.org/viewtopic.php?p=2375634 etc -- 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

14 years, 8 months

6
6
0 / 0

[Hibernate-JIRA] Created: (HHH-3887) Envers hbm xml based configuration

by Helmut Pasch (JIRA)

Envers hbm xml based configuration ---------------------------------- Key: HHH-3887 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3887 Project: Hibernate Core Issue Type: Improvement Components: envers Affects Versions: 3.5 Environment: Hibernate: All Hibernate Versions including Envers as subproject Our Project: Hibernate 3.3.1, Spring 2.5.6, Spring DM 1.2.0, Swing, GWT, .... Reporter: Helmut Pasch Currently the tool library Envers can only be configured / mapped to java POJOs by annotations. We would appreciate if this mapping could be done by hbm xml files. Using this approach the POJO won't be bound to Envers annotations. They simply would be left as POJOs instead of transformed to JPA like Entity Beans. We use POJOs to directly serialize them to a client tier, e.g. a Swing or GWT client tier. If our POJOs have to rely on Envers annotations similar like JPA annotations we see only two options objects may leave the server tier. First by a copy to an annotation less value object, which is consuming performance and resources. Second by coping / using Envers / Hibernate libraries for reference purposes on the client tier. Both solutions are not very attractive compared to the very well working hbm xml approach Hibernate core ORM functionality provides us. It is our intention to reduce / eliminate in client server communication model transformations like coping objects or transforming them to other formats like XML, e.g. like web services does. The easiest way would be to just serialize the Java POJO objects. But never then less the client should only depend (logically) on the server API. It is not intended to rely on a specific server implementation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3410) @OneToMany forces unique key in @JoinTable when inverseJoinColumns = @JoinColumn(unique=false)

by Kamil Morong (JIRA)

@OneToMany forces unique key in @JoinTable when inverseJoinColumns = @JoinColumn(unique=false) ---------------------------------------------------------------------------------------------- Key: HHH-3410 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3410 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.6 Environment: MySQL 5.0.51b, Hibernate Core 3.2.6 GA, Hibernate Annotations 3.3.1 GA Reporter: Kamil Morong Hi, I need to have this class composition with one to many relation: @Entity @Table(name="USER") public class User implements java.io.Serializable { private Long id; private String username; private String password; private Set<Role> roles = new LinkedHashSet<Role>(); public User() { } @Id @GeneratedValue(strategy = GenerationType.AUTO) @Column(name = "USER_ID") public Long getId() { return id; } public void setId(Long id) { this.id = id; } @Column(name="USERNAME", nullable=false, unique=true) public String getUsername() { return username; } public void setUsername(String userName) { this.username = userName; } @Column(name="PASSWORD", nullable=false) public String getPassword() { return password; } public void setPassword(String password) { this.password = password; } @CollectionOfElements @OneToMany(cascade={CascadeType.PERSIST, CascadeType.MERGE}) @JoinTable(name = "USER_ROLE", joinColumns = @JoinColumn(name = "USER_ID", unique=false), inverseJoinColumns = @JoinColumn(name = "ROLE_ID", unique=false)) @Cascade(org.hibernate.annotations.CascadeType.SAVE_UPDATE) @LazyCollection(LazyCollectionOption.FALSE) public Set<Role> getRoles() { return roles; } public void setRoles(Set<Role> roles) { this.roles = roles; } } @Entity @Table(name="ROLE") public class Role implements java.io.Serializable { private Long id; private String name; public Role() { } @Id @GeneratedValue(strategy = GenerationType.AUTO) @Column(name = "ROLE_ID") public Long getId() { return id; } public void setId(Long id) { this.id = id; } @Column(name="NAME", nullable=false, unique=true) public String getName() { return name; } public void setName(String name) { this.name = name; } } This will create db tables like SQL script CREATE TABLE `user` ( `USER_ID` BIGINT(20) NOT NULL AUTO_INCREMENT, `PASSWORD` VARCHAR(255) NOT NULL DEFAULT '', `USERNAME` VARCHAR(255) NOT NULL DEFAULT '', PRIMARY KEY (`USER_ID`), UNIQUE KEY `USERNAME` (`USERNAME`) ); CREATE TABLE `role` ( `ROLE_ID` BIGINT(20) NOT NULL AUTO_INCREMENT, `NAME` VARCHAR(255) NOT NULL DEFAULT '', PRIMARY KEY (`ROLE_ID`), UNIQUE KEY `NAME` (`NAME`) ); CREATE TABLE `user_role` ( `USER_ID` BIGINT(20) NOT NULL, `ROLE_ID` BIGINT(20) NOT NULL, PRIMARY KEY (`USER_ID`, `ROLE_ID`), UNIQUE KEY `ROLE_ID` (`ROLE_ID`), KEY `FKBC16F46A1174FFAB` (`ROLE_ID`), KEY `FKBC16F46AB69FC38B` (`USER_ID`), CONSTRAINT `FKBC16F46AB69FC38B` FOREIGN KEY (`USER_ID`) REFERENCES `user` (`USER_ID`), CONSTRAINT `FKBC16F46A1174FFAB` FOREIGN KEY (`ROLE_ID`) REFERENCES `role` (`ROLE_ID`) ); Tables USER and ROLE are right, but the join table USER_ROLE still have defined UNIQUE KEY `ROLE_ID` (`ROLE_ID`). This causes there cannot be one user with many roles. There must be some bug while generating database scheme. I am not able to remove unique key. -- 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

14 years, 8 months

7
8
0 / 0

[Hibernate-JIRA] Created: (HHH-3716) Sybase - null values for columns mapped as "boolean" are persisted as 0 (zero) instead of NULL

by Gail Badner (JIRA)

Sybase - null values for columns mapped as "boolean" are persisted as 0 (zero) instead of NULL ---------------------------------------------------------------------------------------------- Key: HHH-3716 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3716 Project: Hibernate Core Issue Type: Bug Components: core Environment: Sybase Reporter: Gail Badner Assignee: Gail Badner Fix For: 3.2.x, 3.3.x, 3.4 Null values for columns mapped as "boolean" are persisted as 0 (zero) instead of NULL. This happens because Hibernate persists a null Boolean value by calling: PreparedStatement.setNull( index, java.sql.Types.BIT ) The SQL code, java.sql.Types.BIT, is used because the Hibernate BooleanType defines its code as java.sql.Type.BIT. Sybase JDBC converts the null to 0, apparently because Sybase does not allow nullable bit columns. This can be reproduced using an annotations unit test, Java5FeaturesTest.testAutoboxing().. Sybase maps bit columns to tinyint, so when the unit test is executed, the column in the underlying table is actually of type tinyint, not bit. Sybase allows nullable tinyint columns, so there should be no problem persisting a null value as null. I've verified that changing the call to: PreparedStatement.setNull( index, java.sql.Types.TINYINT ) persists the null value without being converted to 0. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
8
0 / 0

[Hibernate-JIRA] Created: (HHH-4452) Sybase ingroes the last byte when persis a byte [] with BinaryType and the last byte is 0

by strong liu (JIRA)

Sybase ingroes the last byte when persis a byte [] with BinaryType and the last byte is 0 ------------------------------------------------------------------------------------------ Key: HHH-4452 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4452 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0.Beta-1 Environment: hibernate-core trunk + sybase ase 15 Reporter: strong liu this issue can be repro with org.hibernate.test.annotations.LobTest.testBinary(). and that test will throw an ArrayIndexOutOfBoundsException. but if we change metadata[1] = (byte) 0; to metadata[1] = (byte) 2; (something else except 0), then the test will pass. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

4
5
0 / 0

[Hibernate-JIRA] Created: (ANN-692) StringClobType doesn't work with Sybase ASA

by Paul Middelkoop (JIRA)

StringClobType doesn't work with Sybase ASA ------------------------------------------- Key: ANN-692 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-692 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.0.ga Environment: Database: Adaptive Server Anywhere, version: 9.0.1.1753 JDBC: jConnect (TM) for JDBC(TM)/6.05(Build 26023) Reporter: Paul Middelkoop Sybase ASA doesn't support the CLOB datatype. However StringClobType works fine except when inserting a null value in the PreparedStatement. I fixed this by changing st.setNull(index, Types.CLOB) to st.setString(index, null). Maybe this can be added to the next release? -- 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

14 years, 8 months

5
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3843) @Audited and @ManyToMany relation problem - after modyfing an Entity: org.hibernate.NonUniqueObjectException with message: "a different object with the same identifier value was already associated with the session ...

by Michał Maryniak (JIRA)

@Audited and @ManyToMany relation problem - after modyfing an Entity: org.hibernate.NonUniqueObjectException with message: "a different object with the same identifier value was already associated with the session ... ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-3843 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3843 Project: Hibernate Core Issue Type: Bug Components: envers Affects Versions: 3.3.1 Environment: envers.jar 1.2.0, Hibernate 3.3.1, postgresql-8.3, jboss-4.2.3 Reporter: Michał Maryniak Attachments: enverse.7z There is a problem with unidirectional @ManyToMany relation. This case is different than the one with inheritance: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3830. The example is trival and code is as simple as it can be. A single Person can have many roles, and one Role can by assigned to many Person entities. @Entity @Audited public class Person implements Serializable { (...) @ManyToMany public List<Role> getRoles() { return roles; } (...) } and @Entity @Audited public class Role implements Serializable { (...) } And here comes a use case: 1) I create role 'admin' 2) I create role 'user' 3) I create person 'john' and add him a role 'admin' 4) I edit 'john' and add him second role 'user' and I got an exception: org.hibernate.NonUniqueObjectException with message: "a different object with the same identifier value was already associated with the session: [Person_Role_AUD#{roles_id=1, Person_id=5, REV=DefaultRevisionEntity(id = 7, revisionDate = 2009-04-01 10:46:32)}]" If I add one role and remove the second one, or if I only remove a role - an Exception does not occur. I attached a zip file with this simple SEAM project generated by seam-gen 2.1.1 GA. I haven't included jar files, but project requires jar's "generated" with seam-gen (2.1.1) and following jar's have been replaced with new ones: 2008-06-13 13:09 313˙898 dom4j.jar 1.6.1 2009-03-23 13:01 285˙158 envers.jar 1.2.0-hibernate-3.3 2008-08-20 11:27 279˙714 hibernate-annotations.jar 3.4.0.GA 2008-08-20 11:31 66˙993 hibernate-commons-annotations.jar 3.1.0.GA 2008-08-20 12:19 119˙292 hibernate-entitymanager.jar 3.4.0.GA 2008-12-04 14:39 304˙236 hibernate-search.jar 3.1.0.GA 2008-09-10 14:01 62˙574 hibernate-validator.jar 3.1.0.GA 2008-09-10 13:27 2˙766˙130 hibernate.jar from hibernate-distribution-3.3.1.GA-dist 2008-06-13 13:09 13˙236 jta.jar 1.1 (from hibernate-distribution-3.3.1.GA-dist) 2008-12-04 14:41 818˙961 lucene-core.jar 2.4.0 701827 - 2008-10-05 16:44:37 2008-08-19 20:40 17˙384 slf4j-api.jar 1.5.2 If you wish - I can attach a file with my oryginal jar - but it would be a realy big file ;-) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

5
12
0 / 0

[Hibernate-JIRA] Created: (BVAL-24) What should be done when multiple META-INF/validation.xml are found?

by Emmanuel Bernard (JIRA)

What should be done when multiple META-INF/validation.xml are found? -------------------------------------------------------------------- Key: BVAL-24 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-24 Project: Bean Validation Issue Type: Task Components: spec-general Reporter: Emmanuel Bernard -- 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

14 years, 8 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3434) hql insert doesn't work when inserting into a table with composite-id

by Ning Zhang (JIRA)

hql insert doesn't work when inserting into a table with composite-id ---------------------------------------------------------------------- Key: HHH-3434 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3434 Project: Hibernate3 Issue Type: Bug Components: query-hql Affects Versions: 3.2.6 Environment: 3.2.6GA, any database Reporter: Ning Zhang I have a table serving as an association table, so the Id of the table is just the ids from the linked tables. The mapping file looks like: <class name="UserPt" table="user_pt" > <composite-id> <key-property name="userId" type="java.lang.Long" column="user_id"/> <key-property name="ptId" type="java.lang.Long" column="pt_id"/> </composite-id> </class> And I need to run some HQL to insert the association into the table like: INSERT INTO UserPt(userId, ptId) SELECT user.id, pt.id FROM........... When I run this HQL, it gives an error saying: "can only generate ids as part of bulk insert with either sequence or post-insert style generators". I logged the bug in http://opensource.atlassian.com/projects/hibernate/browse/HHH-3400, but it is closed because I asked for a workaround. So this time I am not asking for anthing, just report the bug. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

5
8
0 / 0

[Hibernate-JIRA] Created: (HHH-4596) Bulk insertion with assigned identifiers

by Zoran Regvart (JIRA)

Bulk insertion with assigned identifiers ---------------------------------------- Key: HHH-4596 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4596 Project: Hibernate Core Issue Type: Patch Components: core Affects Versions: 3.5.0-Beta-2 Environment: latest hibernate, but tracing this since batch processing inception Reporter: Zoran Regvart Attachments: assigned-bulk-insert.patch supportsIdGenWithBulkInsertion method of HqlSqlWalker explicitly checks if the id generator is either SequenceGenerator or PostInsertIdentifierGenerator, I think this could be extended to include Assigned id generator, attached is the patch for that -- 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

14 years, 8 months

5
18
0 / 0

[Hibernate-JIRA] Created: (HHH-3440) 3.3.0 GA with MySQL 5.0 throws table validation exception

by Carlo Luib-Finetti (JIRA)

3.3.0 GA with MySQL 5.0 throws table validation exception --------------------------------------------------------- Key: HHH-3440 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3440 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.3.0.GA Environment: Hibernate 3.3.0 GA MySQL 5.0 JBoss 4.2.2 Reporter: Carlo Luib-Finetti Hibernate immediately throws an exception at application startup, when it does the schema validation. org.hibernate.HibernateException: Wrong column type in dpjw.assessment for column NOTES. Found: text, expected: longtext Comparing the sources of 3.2.0 with 3.3.0 I can see that someone set two java statements into comment. The 3.2 version of MySQLDialect.java looks like this: protected void registerVarcharTypes() { registerColumnType( Types.VARCHAR, "longtext" ); registerColumnType( Types.VARCHAR, 16777215, "mediumtext" ); registerColumnType( Types.VARCHAR, 65535, "text" ); registerColumnType( Types.VARCHAR, 255, "varchar($l)" ); } while the new 3.3.0 version is this: protected void registerVarcharTypes() { registerColumnType( Types.VARCHAR, "longtext" ); // registerColumnType( Types.VARCHAR, 16777215, "mediumtext" ); // registerColumnType( Types.VARCHAR, 65535, "text" ); registerColumnType( Types.VARCHAR, 255, "varchar($l)" ); } If I uncomment these (and others in the same Java file!), the validation process is ok. Is there any reason why these statements (and others!) were commented out??? -- 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

14 years, 8 months

6
7
0 / 0

[Hibernate-JIRA] Created: (HHH-3530) The code in the 3.3.1.GA subversion tag is not the code that's been released on the maven repository.jboss.org as 3.3.1.GA

by Geoffrey De Smet (JIRA)

The code in the 3.3.1.GA subversion tag is not the code that's been released on the maven repository.jboss.org as 3.3.1.GA -------------------------------------------------------------------------------------------------------------------------- Key: HHH-3530 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3530 Project: Hibernate Core Issue Type: Bug Components: build Affects Versions: 3.3.1 Reporter: Geoffrey De Smet Here's the proof: http://fisheye.jboss.org/browse/Hibernate/core/tags/hibernate-3.3.1.GA/co... contains the lines (44-45): registerColumnType( Types.CLOB, "longtext" ); registerColumnType( Types.CLOB, 16777215, "mediumtext" ); registerColumnType( Types.CLOB, 65535, "text" ); But the sources jar downloaded from http://repository.jboss.org/maven2/org/hibernate/hibernate-core/3.3.1.GA/... file org\hibernate\dialect\MySQLDialect.java so on my pc C:\Documents and Settings\gds\.m2\repository\org\hibernate\hibernate-core\3.3.1.GA\hibernate-core-3.3.1.GA-sources.jar!\org\hibernate\dialect\MySQLDialect.java has these lines (66-68) instead: registerColumnType( Types.CLOB, "longtext" ); // registerColumnType( Types.CLOB, 16777215, "mediumtext" ); // registerColumnType( Types.CLOB, 65535, "text" ); It's not just some copyright stuff that been added (giving it different line numbers), some lines are clearly commented out. Maybe untagged changes happened in other files too? -- 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

14 years, 8 months

4
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3930) one-to-one causes redundant select query

by Martijn Dashorst (JIRA)

one-to-one causes redundant select query ---------------------------------------- Key: HHH-3930 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3930 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1 Reporter: Martijn Dashorst @Entity public class Address { @Id @GeneratedValue(strategy = GenerationType.AUTO) private Long id; @OneToOne(mappedBy = "address") private Customer customer; } @Entity public class Customer { @Id @GeneratedValue(strategy = GenerationType.AUTO) private Long id; @OneToOne(fetch = FetchType.EAGER, cascade = CascadeType.ALL) private Address address = new Address(); public Long getId() { return id; } public Address getAddress() { return address; } } This mapping causes 2 instead of the expected 1 query to retrieve a Customer and its Address from the db: select * from Customer customer0_ left outer join Address address1_ on customer0_.address_id=address1_.id where customer0_.id=? select * from Customer customer0_ left outer join Address address1_ on customer0_.address_id=address1_.id where customer0_.address_id=? Changing the mapping to a LAZY fetch type: @OneToOne(fetch = FetchType.LAZY, cascade = CascadeType.ALL) private Address address = new Address(); Causes 3 select queries instead of the expected 2 queries to retrieve a Customer (and its Address) from the db: select * from Customer customer0_ where customer0_.id=? select * from Address address0_ left outer join Customer customer1_ on address0_.id=customer1_.address_id where address0_.id=? select * from Customer customer0_ where customer0_.address_id=? The third select is superfluous because the relationship is already completely known: you already have the customer, so why not just set it on the address entity? Making the address field in Customer a @ManyToOne doesn't make a difference. Making the customer field in Address a @OneToMany does remove the extra select, but forces our model to change the relationship from Customer to List<Customer> where we *know* there'll be only 1 element. Apparently Hibernate can figure out the reverse relationship with a @ManyToOne - @OneToMany without the need for additional queries, can't this be extended to @OneToOne bidirectional relationships as well? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

4
3
0 / 0

[Hibernate-JIRA] Created: (HHH-4881) restrict polymorphic query results

by Domenico Loiacono (JIRA)

restrict polymorphic query results ---------------------------------- Key: HHH-4881 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4881 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0-Beta-4 Environment: Hibernate 3.5.0-Beta-4, MySQL 5.1 Glassfish v3 Reporter: Domenico Loiacono I'm using JPA 2.0, Hibernate 3.5.0-Beta4, MySQL 5.1 on Glassfish v3. I want to limit the polymorphic query results using JPA 2.0 syntax (TYPE) : SELECT e FROM Employee e WHERE TYPE(e) IN (FullTime, Executive) but it seems that Hibernate 3.5.0-Beta4 doesn't support this syntax because in the generated sql query the 'type' keyword remains unmapped and MySQL throws an Exception: Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '(type(employee0_.id) in (5))' at line 1 So I tried with Criteria API: CriteriaBuilder criteriaBuilder = em.getCriteriaBuilder(); CriteriaQuery<Employee> criteria = criteriaBuilder.createQuery(Employee.class); Root<Employee> employee= criteria.from(Employee.class); criteria.where(employee.type().in(FullTime.class,Executive.class)); But I received an Exception: Caused by: java.lang.IllegalArgumentException: Unexpected call on EntityTypeExpression#render at org.hibernate.ejb.criteria.expression.PathTypeExpression.render(PathTypeExpression.java:48) at org.hibernate.ejb.criteria.predicate.InPredicate.render(InPredicate.java:164) at org.hibernate.ejb.criteria.QueryStructure.render(QueryStructure.java:258) at org.hibernate.ejb.criteria.CriteriaQueryImpl.render(CriteriaQueryImpl.java:340) at org.hibernate.ejb.criteria.CriteriaQueryCompiler.compile(CriteriaQueryCompiler.java:150) at org.hibernate.ejb.AbstractEntityManagerImpl.createQuery(AbstractEntityManagerImpl.java:416) at com.sun.enterprise.container.common.impl.EntityManagerWrapper.createQuery(EntityManagerWrapper.java:489) So I opened the PathTypeExpression class and in the render method I saw : public String render(CriteriaQueryCompiler.RenderingContext renderingContext) { // todo : is it valid for this to get rendered into the query itself? throw new IllegalArgumentException( "Unexpected call on EntityTypeExpression#render" ); } Then I switched to use Hibernate custom query syntax (class) : SELECT e FROM Employee e WHERE (e.class) IN (FullTime, Executive) Ok this works fine. But when I add a join with another entity (Department) that has the same TABLE_PER_CLASS inheritance strategy of entity Employee, I have a new problem: SELECT e FROM Employee e JOIN e.departments d WHERE d.code = 'D1' and (e.class) IN (FullTime, Executive) GRAVE: Column 'clazz_' in where clause is ambiguous Caused by: javax.persistence.PersistenceException: org.hibernate.exception.ConstraintViolationException: could not execute 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

14 years, 9 months

6
8
0 / 0

[Hibernate-JIRA] Created: (HHH-3133) ParameterParser incorrectly identifies positional paramters as output parameters

by Michael Cervantes (JIRA)

ParameterParser incorrectly identifies positional paramters as output parameters -------------------------------------------------------------------------------- Key: HHH-3133 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3133 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.5 Reporter: Michael Cervantes Any HQL that references a property with the text "call" in it will throw off the parser. For instance: <i>FROM Cdr WHERE account.id = ? AND callStart >= ? AND callStart < ?</i> kept giving me ordinal parameter errors because "callStart" tricks the parser into thinking there's an output parameter. -- 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

14 years, 9 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2866) The order of parameters is not maintained between HQL and SQL, but the parameters are inserted into the PreparedStatement in their HQL order.

by Benjamin Keil (JIRA)

The order of parameters is not maintained between HQL and SQL, but the parameters are inserted into the PreparedStatement in their HQL order. --------------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-2866 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2866 Project: Hibernate3 Issue Type: Bug Components: query-hql Affects Versions: 3.2.5 Environment: Hibernate 3.2.5.ga; both with MySQLInnoDB and H2 dialects; both with annotations and hand written mapping files Reporter: Benjamin Keil Attachments: ReorderedParameters.java, ReorderedParameters.zip The HQL query from Assoc a where a.type.oid = ? and a.constituents[?].oid = ? gets translated into select reorderedp0_.oid as oid1_, reorderedp0_.type_oid as type2_1_ from Assoc reorderedp0_, Assoc_Topic constituen1_, Topic reorderedp2_ where reorderedp0_.oid=constituen1_.Assoc_oid and constituen1_.topic_index = ? and constituen1_.constituents_oid=reorderedp2_.oid and reorderedp0_.type_oid=? and reorderedp2_.oid=? Where clearly the first and second parameters (the index and the type) have been permuted. The relevant thread in the User forum is : http://forum.hibernate.org/viewtopic.php?t=979832 Attached are a java source file that demonstrates the error, and a zipped maven2 project that supplies the Hibernate, Hibernate-Annotation, H2, and Log4J dependencies. -- 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

14 years, 9 months

4
4
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-46) Race condition in manual index update

by Christian Bauer (JIRA)

Race condition in manual index update ------------------------------------- Key: HSEARCH-46 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-46 Project: Hibernate Search Issue Type: Bug Components: engine Reporter: Christian Bauer log.info("rebuilding Lucene index"); Class[] entityTypes = { Document.class, File.class, Comment.class, Faq.class}; EntityManager em = (EntityManager) Component.getInstance("entityManager"); FullTextSession ftSession = org.hibernate.search.Search.createFullTextSession( (Session) em.getDelegate() ); for (Class entityType : entityTypes) { for (Object o : ((Session) em.getDelegate()).createCriteria(entityType).list()) { ftSession.index(o); } } 08:23:39,419 INFO [WikiInit] rebuilding Lucene index 08:23:39,532 DEBUG [ManagedPersistenceContext] created seam managed persistence context from EntityManagerFactory 08:23:39,553 INFO [STDOUT] Hibernate: /* criteria query */ select this_.NODE_ID as NODE2_1_1_, this_.AREA_NR as AREA3_1_1_, this_.CREATED_BY_USER_ID as CREATED17_1_1_, this_.CREATED_ON as CREATED4_1_1_, this_.LAST_MODIFIED_BY_USER_ID as LAST18_1_1_, this_.LAST_MODIFIED_ON as LAST5_1_1_, this_.MENU_ITEM as MENU6_1_1_, this_.NAME as NAME1_1_, this_.PARENT_NODE_ID as PARENT20_1_1_, this_.READ_ACCESS_LEVEL as READ8_1_1_, this_.NODE_REVISION as NODE9_1_1_, this_.OBJ_VERSION as OBJ10_1_1_, this_.WIKINAME as WIKINAME1_1_, this_.WRITE_ACCESS_LEVEL as WRITE12_1_1_, this_.ENABLE_COMMENT_FORM as ENABLE14_1_1_, this_.ENABLE_COMMENTS as ENABLE15_1_1_, this_.NAME_AS_TITLE as NAME16_1_1_, node2_.NODE_ID as NODE2_1_0_, node2_.AREA_NR as AREA3_1_0_, node2_.CREATED_BY_USER_ID as CREATED17_1_0_, node2_.CREATED_ON as CREATED4_1_0_, node2_.LAST_MODIFIED_BY_USER_ID as LAST18_1_0_, node2_.LAST_MODIFIED_ON as LAST5_1_0_, node2_.MENU_ITEM as MENU6_1_0_, node2_.NAME as NAME1_0_, node2_.PARENT_NODE_ID as PARENT20_1_0_, node2_.READ_ACCESS_LEVEL as READ8_1_0_, node2_.NODE_REVISION as NODE9_1_0_, node2_.OBJ_VERSION as OBJ10_1_0_, node2_.WIKINAME as WIKINAME1_0_, node2_.WRITE_ACCESS_LEVEL as WRITE12_1_0_, node2_.DEFAULT_DOCUMENT_ID as DEFAULT19_1_0_, node2_.ENABLE_COMMENT_FORM as ENABLE14_1_0_, node2_.ENABLE_COMMENTS as ENABLE15_1_0_, node2_.NAME_AS_TITLE as NAME16_1_0_, node2_1_.CONTENT_TYPE as CONTENT1_2_0_, node2_1_.FILENAME as FILENAME2_0_, node2_1_.FILESIZE as FILESIZE2_0_, node2_1_.IMAGE_SIZE_X as IMAGE5_2_0_, node2_1_.IMAGE_SIZE_Y as IMAGE6_2_0_, node2_1_.IMAGE_THUMBNAIL as IMAGE7_2_0_, node2_.NODE_TYPE as NODE1_1_0_ from NODE this_ left outer join NODE node2_ on this_.PARENT_NODE_ID=node2_.NODE_ID left outer join NODE_FILE node2_1_ on node2_.NODE_ID=node2_1_.FILE_ID where this_.NODE_TYPE='DOCUMENT' 08:23:39,587 INFO [STDOUT] Hibernate: /* load org.jboss.seam.wiki.core.model.Node */ select node0_.NODE_ID as NODE2_1_1_, node0_.AREA_NR as AREA3_1_1_, node0_.CREATED_BY_USER_ID as CREATED17_1_1_, node0_.CREATED_ON as CREATED4_1_1_, node0_.LAST_MODIFIED_BY_USER_ID as LAST18_1_1_, node0_.LAST_MODIFIED_ON as LAST5_1_1_, node0_.MENU_ITEM as MENU6_1_1_, node0_.NAME as NAME1_1_, node0_.PARENT_NODE_ID as PARENT20_1_1_, node0_.READ_ACCESS_LEVEL as READ8_1_1_, node0_.NODE_REVISION as NODE9_1_1_, node0_.OBJ_VERSION as OBJ10_1_1_, node0_.WIKINAME as WIKINAME1_1_, node0_.WRITE_ACCESS_LEVEL as WRITE12_1_1_, node0_.DEFAULT_DOCUMENT_ID as DEFAULT19_1_1_, node0_.ENABLE_COMMENT_FORM as ENABLE14_1_1_, node0_.ENABLE_COMMENTS as ENABLE15_1_1_, node0_.NAME_AS_TITLE as NAME16_1_1_, node0_1_.CONTENT_TYPE as CONTENT1_2_1_, node0_1_.FILENAME as FILENAME2_1_, node0_1_.FILESIZE as FILESIZE2_1_, node0_1_.IMAGE_SIZE_X as IMAGE5_2_1_, node0_1_.IMAGE_SIZE_Y as IMAGE6_2_1_, node0_1_.IMAGE_THUMBNAIL as IMAGE7_2_1_, node0_.NODE_TYPE as NODE1_1_1_, node1_.NODE_ID as NODE2_1_0_, node1_.AREA_NR as AREA3_1_0_, node1_.CREATED_BY_USER_ID as CREATED17_1_0_, node1_.CREATED_ON as CREATED4_1_0_, node1_.LAST_MODIFIED_BY_USER_ID as LAST18_1_0_, node1_.LAST_MODIFIED_ON as LAST5_1_0_, node1_.MENU_ITEM as MENU6_1_0_, node1_.NAME as NAME1_0_, node1_.PARENT_NODE_ID as PARENT20_1_0_, node1_.READ_ACCESS_LEVEL as READ8_1_0_, node1_.NODE_REVISION as NODE9_1_0_, node1_.OBJ_VERSION as OBJ10_1_0_, node1_.WIKINAME as WIKINAME1_0_, node1_.WRITE_ACCESS_LEVEL as WRITE12_1_0_, node1_.DEFAULT_DOCUMENT_ID as DEFAULT19_1_0_, node1_.ENABLE_COMMENT_FORM as ENABLE14_1_0_, node1_.ENABLE_COMMENTS as ENABLE15_1_0_, node1_.NAME_AS_TITLE as NAME16_1_0_, node1_1_.CONTENT_TYPE as CONTENT1_2_0_, node1_1_.FILENAME as FILENAME2_0_, node1_1_.FILESIZE as FILESIZE2_0_, node1_1_.IMAGE_SIZE_X as IMAGE5_2_0_, node1_1_.IMAGE_SIZE_Y as IMAGE6_2_0_, node1_1_.IMAGE_THUMBNAIL as IMAGE7_2_0_, node1_.NODE_TYPE as NODE1_1_0_ from NODE node0_ left outer join NODE_FILE node0_1_ on node0_.NODE_ID=node0_1_.FILE_ID left outer join NODE node1_ on node0_.PARENT_NODE_ID=node1_.NODE_ID left outer join NODE_FILE node1_1_ on node1_.NODE_ID=node1_1_.FILE_ID where node0_.NODE_ID=? 08:23:39,654 INFO [STDOUT] Hibernate: /* criteria query */ select this_.COMMENT_ID as COMMENT1_4_0_, this_.CREATED_ON as CREATED2_4_0_, this_.DOCUMENT_ID as DOCUMENT9_4_0_, this_.FROM_USER_EMAIL as FROM3_4_0_, this_.FROM_USER_HOMEPAGE as FROM4_4_0_, this_.FROM_USER_NAME as FROM5_4_0_, this_.SUBJECT as SUBJECT4_0_, this_.COMMENT_TEXT as COMMENT7_4_0_, this_.OBJ_VERSION as OBJ8_4_0_ from COMMENTS this_ 08:23:39,662 INFO [STDOUT] Hibernate: /* criteria query */ select this_.FAQ_ID as FAQ1_7_0_, this_.ANSWER as ANSWER7_0_, this_.CREATED_ON as CREATED3_7_0_, this_.QUESTION as QUESTION7_0_, this_.RATING as RATING7_0_, this_.OBJ_VERSION as OBJ6_7_0_ from FAQ this_ 08:23:39,665 DEBUG [Work] committing transaction 08:23:39,807 ERROR [AssertionFailure] an assertion failure occured (this may indicate a bug in Hibernate) org.hibernate.annotations.common.AssertionFailure: Tries to read for update a index while a writer is accessedclass org.jboss.seam.wiki.core.model.Document at org.hibernate.search.backend.Workspace.getIndexReader(Workspace.java:54) at org.hibernate.search.backend.impl.lucene.LuceneWorker.remove(LuceneWorker.java:81) at org.hibernate.search.backend.impl.lucene.LuceneWorker.performWork(LuceneWorker.java:69) at org.hibernate.search.backend.impl.lucene.LuceneWorker.performWork(LuceneWorker.java:40) at org.hibernate.search.backend.impl.lucene.LuceneBackendQueueProcessor.run(LuceneBackendQueueProcessor.java:36) at org.hibernate.search.backend.impl.BatchedQueueingProcessor.performWork(BatchedQueueingProcessor.java:116) at org.hibernate.search.backend.impl.PostTransactionWorkQueueSynchronization.afterCompletion(PostTransactionWorkQueueSynchronization.java:49) at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.afterCompletion(SynchronizationImple.java:136) at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.afterCompletion(TwoPhaseCoordinator.java:342) at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:95) at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:177) -- 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

14 years, 9 months

4
4
0 / 0

[Hibernate-JIRA] Created: (HHH-4723) Column in SQL query is returned as java.lang.Character

by Nick de Graeve (JIRA)

Column in SQL query is returned as java.lang.Character ------------------------------------------------------ Key: HHH-4723 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4723 Project: Hibernate Core Issue Type: Bug Components: query-sql Affects Versions: 3.3.1 Reporter: Nick de Graeve When I run this code sample: {{List data = session.createSQLQuery("select e.country_iso_code from agent.tbd3_Entry e where e.country_iso_code = 'BE'").list();}} {{Object row = data.get(0);}} {{System.out.print(row + ": " + row.getClass());}} I get this result: {{B: class java.lang.Character}} I expect to get a {{java.lang.String}} containing "BE", not just the 1st Character. The column country_is_code of table tbd3_entry is defined in Oracle as {{COUNTRY_ISO_CODE CHAR(2 BYTE)}} When I add a scalar with correct type I do get what I need: {{List data = session.createSQLQuery("select e.country_iso_code countryIsoCode from agent.tbd3_Entry e where e.country_iso_code = 'BE'").addScalar("countryIsoCode", Hibernate.STRING).list();}} {{Object row = data.get(0);}} {{System.out.print(row + ": " + row.getClass());}} results in {{BE: class java.lang.String}} -- 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

14 years, 9 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3313) Criteria + Property Projection + LockMode causes a NPE

by Christian Nelson (JIRA)

Criteria + Property Projection + LockMode causes a NPE ------------------------------------------------------ Key: HHH-3313 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3313 Project: Hibernate3 Issue Type: Bug Components: query-criteria Affects Versions: 3.2.6 Environment: Hibernate 3.2.6.ga, PostgreSQL 8.1 Reporter: Christian Nelson Attachments: hibernate-criteria-projection-lockmode-project.zip In converting a working HQL query to the Criteria API, we stumbled upon what looks very much like a bug. When combining a criteria with a projection and setting the lockmode (to read or upgrade), hibernate throws a NPE down in CriteriaLoader.applyLocks(). Here's a simplified snippet of the criteria that results in the exception: Criteria criteria = session.createCriteria(Article.class).add(Restrictions.ilike("title", "%frozen%")); criteria.createCriteria("moderation", "m").add(Restrictions.eq("approved", true)); criteria.setProjection(Projections.property("moderation")); criteria.setLockMode("m", LockMode.UPGRADE); assertions(criteria.list()); [The test case includes other attempts at building a similar criteria using different approaches.] And here's the stack trace: java.lang.NullPointerException at org.hibernate.loader.criteria.CriteriaLoader.applyLocks(CriteriaLoader.java:131) at org.hibernate.loader.Loader.preprocessSQL(Loader.java:201) at org.hibernate.loader.Loader.prepareQueryStatement(Loader.java:1538) at org.hibernate.loader.Loader.doQuery(Loader.java:673) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:236) at org.hibernate.loader.Loader.doList(Loader.java:2213) at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2104) at org.hibernate.loader.Loader.list(Loader.java:2099) at org.hibernate.loader.criteria.CriteriaLoader.list(CriteriaLoader.java:94) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1569) at org.hibernate.impl.CriteriaImpl.list(CriteriaImpl.java:283) There's already some talk on the web about this problem: * http://forum.hibernate.org/viewtopic.php?t=955525 * http://saloon.javaranch.com/cgi-bin/ubb/ultimatebb.cgi?ubb=get_topic&f=78... I've created a simplified test case which includes the HQL version of the query (works), the Criteria version without lockmode (works), and then 3 failing tests illustrating the problem. The attached zip contains the test case and supporting files. The source code for the test case is also available via anonymous svn access (http://svn.carbonfive.com/public/christian/hibernate-criteria-projection-...). The test will run out of the box using maven against an h2database in-memory database with no setup. This combination of features doesn't seem that obscure so I'd expect it to work, or at the very least, report that it is not supported in a more graceful manner. -- 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

14 years, 9 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2304) Wrong type detection for sql type char(x) columns

by Markus Heiden (JIRA)

Wrong type detection for sql type char(x) columns ------------------------------------------------- Key: HHH-2304 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2304 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.ga Environment: Hibernate 3.2.0, Oracle 9.2, Oracle JDBC driver 10.2 Reporter: Markus Heiden Attachments: hibernate.zip When executing a sql query which returns columns of sql type char(x), a java.lang.Character is returned. This leads to returning just the first character of the value. In my eyes a String should be returned when the char(x) type has a width > 1. I wasn't able to determine whether this is a jdbc driver issue or a hibernate issue. When using sql type char(x) for columns of entities no such problems occur. Test case is 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

14 years, 9 months

8
13
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-395) Master/Slave configuration as outlined in Hibernate Search in Action does not work when shared location is on NFS

by Sam Doyle (JIRA)

Master/Slave configuration as outlined in Hibernate Search in Action does not work when shared location is on NFS ----------------------------------------------------------------------------------------------------------------- Key: HSEARCH-395 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-395 Project: Hibernate Search Issue Type: Bug Components: directory provider Affects Versions: 3.1.1.GA Reporter: Sam Doyle Priority: Critical https://forum.hibernate.org/viewtopic.php?f=9&t=998613&p=2416681#p2416681 There are many .nfs files being generated in slave locations and appear to be still held open by some part of the application since they fail to be cleaned up. 2009-08-21 10:51:08,696 ERROR [org.hibernate.search.util.FileHelper] Could not delete /location/to/slave/index/2/.nfs000000000085a3ce000016 7e -- 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

14 years, 9 months

4
8
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-159) Sort + Pagination returns wrong results.

by Jason Eacott (JIRA)

Sort + Pagination returns wrong results. ---------------------------------------- Key: HSEARCH-159 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-159 Project: Hibernate Search Issue Type: Bug Affects Versions: 3.0.1.GA Environment: hib 3.2.5ga Reporter: Jason Eacott Perhaps I am doing something wrong? Using the code below if I call getSearchResults("test",0,10); //returns incorrect data I get a different item at the head of the list than if I call getSearchResults("test",0,100);// (this one has correct data, total results for this search is 196 in my ndx & db) if I dont try to paginate the results then the sort items are in order and are correct. and if I paginate with just 1 result getSearchResults("test",0,1); and change the sort order I get the same result for each attempt: ie: Sort datesort=new Sort( new SortField( "date_time", SortField.STRING, true ) ); and Sort datesort=new Sort( new SortField( "date_time", SortField.STRING, false ) ); return the same entry - which is NOT the correct result either. This behavious seems to indicate that the data is being sorted after the limit is set and whats worse, if there are 50,000,000 results, even though I only want 10 and hibernate has already correctly hydrated those 10 (albeit the wrong 10) hibernatesearch then loops over all 50,000,000 hits and creates a new (empty) hibernate proxy object for each & discard all but 10! ... @Field(name="date_time", index=Index.UN_TOKENIZED, store=Store.NO) @DateBridge(resolution=Resolution.MINUTE) private Date publishDate; ... public List getSearchResults(Query query,int firstResult,int maxResults) { List result=null; Session sess=null; Transaction tx = null; try { sess=getSessionFactory().openSession(); FullTextSession fullTextSession = Search.createFullTextSession(sess); tx = fullTextSession.beginTransaction(); tx.begin(); org.hibernate.search.FullTextQuery hibQuery= fullTextSession.createFullTextQuery( query, FeedItem.class ); Sort datesort=new Sort( new SortField( "date_time", SortField.STRING, true ) ); hibQuery.setSort(datesort); Criteria dbCr=fullTextSession.createCriteria(FeedItem.class); hibQuery.setCriteriaQuery(dbCr); dbCr.setFirstResult(firstResult); dbCr.setMaxResults(maxResults); } long resultSize=hibQuery.getResultSize(); if (resultSize>0){ result = hibQuery.list() } tx.commit(); } finally { releaseSession(sess); tx=null; } log.debug("<getSearchResults"); return result; } -- 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

14 years, 9 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3429) SQLQuery, advice user to always use addScalar if CHAR column are involved.

by Anthony Patricio (JIRA)

SQLQuery, advice user to always use addScalar if CHAR column are involved. -------------------------------------------------------------------------- Key: HHH-3429 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3429 Project: Hibernate3 Issue Type: Improvement Components: documentation Reporter: Anthony Patricio Priority: Minor see HHH-2220 If CHAR(2+) is involved in a SQLQuery and if addScalar isn't used, then the returned value is truncated which is very bad. There is no easy fix for this so a little advice in the documentation would be helpful. -- 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

14 years, 9 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2220) session.createSQLQuery(sql) translates database type CHAR(n) to Java type char instead of String

by Regis Pires Magalhaes (JIRA)

session.createSQLQuery(sql) translates database type CHAR(n) to Java type char instead of String ------------------------------------------------------------------------------------------------ Key: HHH-2220 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2220 Project: Hibernate3 Type: Bug Components: query-sql Versions: 3.2.0.ga Reporter: Regis Pires Magalhaes createSQLQuery() method translates database type CHAR(n) to Java type char instead of String when using setResultTransformer(Criteria.ALIAS_TO_ENTITY_MAP). That happens when I do not use addScalar(). And that is the only problem that I have found when not filling return types in advance. A workaround I have made is to concatenate the projected field with an empty string (''). See example below: ... query.setResultTransformer(Criteria.ALIAS_TO_ENTITY_MAP); String sqlQuery = "select s.name state from state s where s.name='PI' "; query = session.createSQLQuery(sqlQuery); ... result: [{STATE=P}] name field is CHAR(2) in database definition (PostgreSQL, HSQLDB and Oracle were tested). Note that it works when I concatenate the field used in projection with an empty string: ... String sqlQuery = "select s.name || '' state from state s where s.name='PI' "; ... result: [{STATE=PI}] -- 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

14 years, 9 months

8
7
0 / 0

[Hibernate-JIRA] Created: (HHH-2429) SQL Character Types Incorrectly mapped to Java objects

by Tyler Van Gorder (JIRA)

SQL Character Types Incorrectly mapped to Java objects ------------------------------------------------------ Key: HHH-2429 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2429 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.1 Environment: Hibernate 3.2.1, Oracle10g Reporter: Tyler Van Gorder We have a work flow that allows the user to enter an arbitrary SQL statement to be executed by our application. We pass those queries through session.createSQLQuery(). We ran into a problem with String literals, which are reported by Oracle (ResultSetMetaData) to be CHAR. Reading the JDBC API, CHAR is a fixed length string. Hibernate is incorrectly mapping this to a Character field. We ended up overriding the Oracle dialect with our own as follows: In our constructor, for a dialect that extends Oracle9iDialect: super() registerColumnType(Types.CHAR, "char($l)" ); registerHibernateType( Types.CHAR, Hibernate.STRING.getName() ); The HibernateType is the crucial one and we are overriding the behavior in the base "Dialect" class, so this appears that it would be a problem for all database variants that don't explicitly change this. 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

14 years, 9 months

4
3
0 / 0

[Hibernate-JIRA] Created: (HCANN-10) JPA OneToOne(optional=true) not supported, supported alternative NotFound() is hibernate-proprietary!

by Bruno Melloni (JIRA)

JPA OneToOne(optional=true) not supported, supported alternative NotFound() is hibernate-proprietary! ----------------------------------------------------------------------------------------------------- Key: HCANN-10 URL: http://opensource.atlassian.com/projects/hibernate/browse/HCANN-10 Project: Hibernate Commons Annotations Issue Type: Bug Environment: Hibernate 3.3.1, annotations 3.4.0, MsSQL DB. Reporter: Bruno Melloni Rejected issue ANN-725 covers this partially. I might have misunderstood, but it seems the reason for rejecting is that @NotFound provides the same capability. All information I could find for JPA and other ORM tools indicates that this capability is supplied by @OneToOne(optional=true). Hibernate seems to be the lone ORM tool that requires the use of a proprietary annotation: @NotFound. @NotFound works, but the problem is that it makes the application no longer be pure-JPA. Not supporting pure-JPA outer joins would seem to be a major bug. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

6
16
0 / 0

[Hibernate-JIRA] Created: (HHH-4854) Make constraint violation name extraction language neutral

by Jonas Olsson (JIRA)

Make constraint violation name extraction language neutral ---------------------------------------------------------- Key: HHH-4854 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4854 Project: Hibernate Core Issue Type: Improvement Components: core Affects Versions: 3.2.6 Environment: Oracle 8 or later Reporter: Jonas Olsson The ViolatedConstraintNameExtracter of Oracle8iDialect uses the following pattern for extracting the contraint violated: return extractUsingTemplate( "constraint (", ") violated", sqle.getMessage() ); and is highly error message language dependent. Changing to: return extractUsingTemplate( "(", ")", sqle.getMessage() ); would eliminate this while still getting the constraint 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

14 years, 9 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HHH-3239) MarkerObject should be serializable when using with swf

by Goran Blankendal (JIRA)

MarkerObject should be serializable when using with swf ------------------------------------------------------- Key: HHH-3239 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3239 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.6 Environment: Hibernate 3.2.6 and Spring Webflow 2.0 Reporter: Goran Blankendal You get a java.io.NotSerializableException: org.hibernate.util.MarkerObject when using hibernate in a persistence context in SWF 2 See http://forum.springframework.org/showthread.php?t=51738 and http://forum.hibernate.org/viewtopic.php?t=985226 The MarkerObject should be serializable. -- 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

14 years, 9 months

4
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2774) Call ResultTransformer.transformList() even if the list argument is an empty list

by Christian Bauer (JIRA)

Call ResultTransformer.transformList() even if the list argument is an empty list --------------------------------------------------------------------------------- Key: HHH-2774 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2774 Project: Hibernate3 Issue Type: Improvement Components: core Reporter: Christian Bauer Priority: Trivial I have a case where a ResultTransformer is doing all the work in transformTuple() and always returns null from that method. The transformed target state is held internally in the ResultTransformer instance (I basically turn many tuples into one). Now I can't get this state out of the ResultTransformer because transformList() is not called after transformTuple(). It would be better if transformList() is called even if the list of tuples returned by transformTuple() is empty. -- 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

14 years, 9 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-4838) 2L-Querycache ImmutableNaturalKeyLookup not properly recognized as hasImmutableNaturalId() is called on wrong EntityMetamodel

by Guenther Demetz (JIRA)

2L-Querycache ImmutableNaturalKeyLookup not properly recognized as hasImmutableNaturalId() is called on wrong EntityMetamodel ----------------------------------------------------------------------------------------------------------------------------- Key: HHH-4838 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4838 Project: Hibernate Core Issue Type: Bug Components: caching (L2) Affects Versions: 3.5.0-Beta-3 Environment: 3.5.0-Beta3, HSQLDB, EHCache as 2L cache implementation Reporter: Guenther Demetz Attachments: TestImmutableNaturalId.jar If a entityclass with immutable naturalId has non-lazy properties (for instance a OneToOne association), then more entityPersisters are involved in the query as it becomes a join-query eager loading the associated entity. The method Loader#getResultFromQueryCache presumes that the first entityPersister in the array is the main entity class. boolean isImmutableNaturalKeyLookup = queryParameters.isNaturalKeyLookup() && getEntityPersisters()[0].getEntityMetamodel().hasImmutableNaturalId(); Debugging attached testcase you can see indeed that getEntityPersisters()[0] returns SingleTableEntityPersister(hello.D) which is the persister of the associated entity, not the main one! Consequently the query is not considered as isImmutableNaturalKeyLookup, despite fullfilling all conditions. Here my output (with enabled p6spy): 11:53:15,651 INFO Version:37 - Hibernate Annotations 3.5.0.Beta1 11:53:15,690 INFO Environment:563 - Hibernate 3.5.0-Beta-3 11:53:15,694 INFO Environment:596 - hibernate.properties not found 11:53:15,700 INFO Environment:774 - Bytecode provider name : javassist 11:53:15,706 INFO Environment:655 - using JDK 1.4 java.sql.Timestamp handling 11:53:15,863 INFO Version:38 - Hibernate EntityManager 3.5.0.Beta1 11:53:16,356 INFO AnnotationBinder:446 - Binding entity from annotated class: hello.A 11:53:16,424 INFO EntityBinder:471 - Bind entity hello.A on table A 11:53:16,526 INFO AnnotationBinder:446 - Binding entity from annotated class: hello.D 11:53:16,527 INFO EntityBinder:471 - Bind entity hello.D on table D 11:53:16,686 WARN Ejb3Configuration:943 - hibernate.connection.autocommit = false break the EJB3 specification 11:53:16,702 INFO HibernateSearchEventListenerRegister:75 - Unable to find org.hibernate.search.event.FullTextIndexEventListener on the classpath. Hibernate Search is not enabled. 11:53:16,718 INFO DriverManagerConnectionProvider:64 - Using Hibernate built-in connection pool (not for production use!) 11:53:16,719 INFO DriverManagerConnectionProvider:65 - Hibernate connection pool size: 20 11:53:16,720 INFO DriverManagerConnectionProvider:68 - autocommit mode: false 11:53:16,921 INFO DriverManagerConnectionProvider:103 - using driver: com.p6spy.engine.spy.P6SpyDriver at URL: jdbc:hsqldb:hsql://localhost 11:53:16,922 INFO DriverManagerConnectionProvider:109 - connection properties: {user=sa, password=****, autocommit=false, release_mode=after_transaction} 11:53:17,002 INFO SettingsFactory:117 - RDBMS: HSQL Database Engine, version: 1.8.0 11:53:17,004 INFO SettingsFactory:118 - JDBC driver: HSQL Database Engine Driver, version: 1.8.0 11:53:17,068 INFO Dialect:223 - Using dialect: org.hibernate.dialect.HSQLDialect 11:53:17,082 INFO JdbcSupportLoader:79 - Disabling contextual LOB creation as JDBC driver reported JDBC version [3] less than 4 11:53:17,085 INFO TransactionFactoryFactory:62 - Transaction strategy: org.hibernate.transaction.JDBCTransactionFactory 11:53:17,089 INFO TransactionManagerLookupFactory:80 - No TransactionManagerLookup configured (in JTA environment, use of read-write or transactional second-level cache is not recommended) 11:53:17,090 INFO SettingsFactory:169 - Automatic flush during beforeCompletion(): disabled 11:53:17,091 INFO SettingsFactory:173 - Automatic session close at end of transaction: disabled 11:53:17,097 INFO SettingsFactory:188 - Scrollable result sets: enabled 11:53:17,098 INFO SettingsFactory:196 - JDBC3 getGeneratedKeys(): disabled 11:53:17,099 INFO SettingsFactory:204 - Connection release mode: after_transaction 11:53:17,101 INFO SettingsFactory:231 - Default batch fetch size: 1 11:53:17,103 INFO SettingsFactory:235 - Generate SQL with comments: disabled 11:53:17,104 INFO SettingsFactory:239 - Order SQL updates by primary key: disabled 11:53:17,105 INFO SettingsFactory:243 - Order SQL inserts for batching: disabled 11:53:17,107 INFO SettingsFactory:410 - Query translator: org.hibernate.hql.ast.ASTQueryTranslatorFactory 11:53:17,114 INFO SettingsFactory:251 - Query language substitutions: {} 11:53:17,115 INFO SettingsFactory:256 - JPA-QL strict compliance: enabled 11:53:17,121 INFO SettingsFactory:261 - Second-level cache: enabled 11:53:17,130 INFO SettingsFactory:265 - Query cache: enabled 11:53:17,143 INFO SettingsFactory:395 - Cache region factory : org.hibernate.cache.impl.bridge.RegionFactoryCacheProviderBridge 11:53:17,144 INFO RegionFactoryCacheProviderBridge:61 - Cache provider: net.sf.ehcache.hibernate.SingletonEhCacheProvider 11:53:17,150 INFO SettingsFactory:275 - Optimize cache for minimal puts: disabled 11:53:17,151 INFO SettingsFactory:284 - Structured second-level cache entries: disabled 11:53:17,151 INFO SettingsFactory:374 - Query cache factory: org.hibernate.cache.StandardQueryCacheFactory 11:53:17,165 INFO SettingsFactory:313 - Statistics: disabled 11:53:17,166 INFO SettingsFactory:317 - Deleted entity synthetic identifier rollback: disabled 11:53:17,166 INFO SettingsFactory:332 - Default entity-mode: pojo 11:53:17,167 INFO SettingsFactory:336 - Named query checking : enabled 11:53:17,167 INFO SettingsFactory:340 - Check Nullability in Core (should be disabled when Bean Validation is on): disabled 11:53:17,240 INFO SessionFactoryImpl:197 - building session factory 11:53:17,260 WARN ConfigurationFactory:131 - No configuration found. Configuring ehcache from ehcache-failsafe.xml found in the classpath: jar:file:/home/pb00067/Desktop/ehcache-1.7.1/lib/ehcache-core-1.7.1.jar!/ehcache-failsafe.xml 11:53:17,361 WARN SingletonEhCacheProvider:92 - Could not find a specific ehcache configuration for cache named [hello.A]; using defaults. 11:53:17,566 WARN SingletonEhCacheProvider:92 - Could not find a specific ehcache configuration for cache named [hello.D]; using defaults. 11:53:17,661 INFO SchemaExport:226 - Running hbm2ddl schema export 11:53:17,663 INFO SchemaExport:251 - exporting generated schema to database p6spy - 1264416797664|0|0|commit|| p6spy - 1264416797670|1|0|statement alter table A drop constraint FK41F7BDC12E p6spy - 1264416797672|0|0|statement drop table A if exists p6spy - 1264416797673|0|0|statement drop table D if exists p6spy - 1264416797674|1|0|statement drop table hibernate_sequences if exists p6spy - 1264416797675|1|0|statement create table A (oid bigint not null, name varchar(255), version integer not null, assSingleD_oid bigint, primary key (oid), unique (name)) p6spy - 1264416797676|0|0|statement create table D (oid bigint not null, version integer not null, primary key (oid)) p6spy - 1264416797678|1|0|statement alter table A add constraint FK41F7BDC12E foreign key (assSingleD_oid) references D p6spy - 1264416797679|1|0|statement create table hibernate_sequences ( sequence_name varchar(255), sequence_next_hi_value integer ) 11:53:17,679 INFO SchemaExport:268 - schema export complete 11:53:17,684 INFO UpdateTimestampsCache:57 - starting update timestamps cache at region: org.hibernate.cache.UpdateTimestampsCache 11:53:17,686 WARN SingletonEhCacheProvider:92 - Could not find a specific ehcache configuration for cache named [org.hibernate.cache.UpdateTimestampsCache]; using defaults. 11:53:17,689 INFO StandardQueryCache:75 - starting query cache at region: org.hibernate.cache.StandardQueryCache 11:53:17,690 WARN SingletonEhCacheProvider:92 - Could not find a specific ehcache configuration for cache named [org.hibernate.cache.StandardQueryCache]; using defaults. 11:53:17,841 DEBUG ConnectionManager:444 - opening JDBC connection p6spy - 1264416797874|6|1|statement select sequence_next_hi_value from hibernate_sequences where sequence_name = 'A' p6spy - 1264416797876|0|1|statement insert into hibernate_sequences (sequence_name, sequence_next_hi_value) values ('A', 0) p6spy - 1264416797878|0|1|statement update hibernate_sequences set sequence_next_hi_value = 1 where sequence_next_hi_value = 0 and sequence_name = 'A' p6spy - 1264416797879|0|1|commit|| p6spy - 1264416797915|0|0|statement insert into A (assSingleD_oid, name, version, oid) values ('', 'name1', 0, 1) 11:53:17,919 DEBUG UpdateTimestampsCache:66 - Pre-invalidating space [A] p6spy - 1264416797931|0|0|commit|| 11:53:17,934 DEBUG UpdateTimestampsCache:81 - Invalidating space [A], timestamp: 5179051204337665 11:53:17,974 DEBUG StandardQueryCache:127 - checking cached query results in region: org.hibernate.cache.StandardQueryCache 11:53:17,975 DEBUG StandardQueryCache:132 - query results were not found in cache p6spy - 1264416797978|0|0|statement select this_.oid as oid0_1_, this_.assSingleD_oid as assSingleD4_0_1_, this_.name as name0_1_, this_.version as version0_1_, d2_.oid as oid1_0_, d2_.version as version1_0_ from A this_ left outer join D d2_ on this_.assSingleD_oid=d2_.oid where ( this_.name='name1' ) p6spy - 1264416797981|-1||resultset|oid=1, oid=null 11:53:17,985 DEBUG StandardQueryCache:94 - caching query results in region: org.hibernate.cache.StandardQueryCache; timestamp=5179051204546560 11:53:17,992 DEBUG StandardQueryCache:127 - checking cached query results in region: org.hibernate.cache.StandardQueryCache 11:53:17,993 DEBUG StandardQueryCache:185 - Checking query spaces for up-to-dateness: [A] 11:53:17,994 DEBUG UpdateTimestampsCache:102 - [A] last update timestamp: 5179051204337665, result set timestamp: 5179051204546560 11:53:17,994 DEBUG StandardQueryCache:142 - returning cached query results 11:53:17,997 INFO SessionFactoryImpl:908 - closing -- 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

14 years, 9 months

6
29
0 / 0

[Hibernate-JIRA] Created: (EJB-276) Support for CLOB not working for DB2 when table per concrete class is being used

by breako (JIRA)

Support for CLOB not working for DB2 when table per concrete class is being used -------------------------------------------------------------------------------- Key: EJB-276 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-276 Project: Hibernate Entity Manager Type: Bug Versions: 3.2.1 Reporter: breako Hi, This came up in the forums: http://forum.hibernate.org/viewtopic.php?p=2344008#2344008 Sample code: Two Pojos @Entity public class Person { private int i; @Identity public int getI() { return i; } public void setI(int i){ this.i = i; } } @Entity public class Employee extends Person{ @Basic(fetch=FetchType.LAZY) @Lob public String getClobAttr() { return clobAttr; } public void setClobAttr(String clobAttr) { this.clobAttr = clobAttr; } } Simple test: public static void main (String args[]) { Query queryImpl = em.createQuery(" from Person"); List list = queryImpl.getResultList(); } This will generate SQL select person0_.clobAttr as clobAttr1 from (select nullif(0,0) as clobAttr from TPerson union all select clobAttr from TEmployee) person0_ which chucks the exception: DB2 SQL error: SQLCODE: -415, SQLSTATE: 42825, SQLERRMC: null I think the SQL hibernate should generate should be: select person0_.clobAttr as clobAttr1 from (select cast(null as CLOB) as clobAttr from TPerson union all select clobAttr from TEmployee) person0_ -- 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

14 years, 9 months

5
4
0 / 0

[Hibernate-JIRA] Created: (BVAL-193) Publish javax.validation:validation-api to Maven central

by Pete Muir (JIRA)

Publish javax.validation:validation-api to Maven central -------------------------------------------------------- Key: BVAL-193 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-193 Project: Bean Validation Issue Type: Task Reporter: Pete Muir -- 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

14 years, 9 months

2
2
0 / 0

[Hibernate-JIRA] Created: (BVAL-200) Validator cannot find validation.xml unless is placed in /WEB-INF/classes/META-INF

by Cris Webber (JIRA)

Validator cannot find validation.xml unless is placed in /WEB-INF/classes/META-INF ---------------------------------------------------------------------------------- Key: BVAL-200 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-200 Project: Bean Validation Issue Type: Bug Components: ri-general - obsolete go to HValidator Environment: Java SE 1.5.0_10; Hibernate Validator 4.0.2.GA. Reporter: Cris Webber Priority: Minor Hibernate Validator requires that the validation.xml file is placed in the META-INF directory in order to load it. In the case of having a WAR file, placing the validation.xml file in /META-INF (at the same level as the WEB-INF directory) does not work, as Hibernate Validator cannot find the file there. Placing the file in /WEB-INF/classes/META-INF worked fine. I believe this is just a workaround and Hibernate Validator should be able to find validation.xml in /META-INF. -- 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

14 years, 9 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3248) org.hibernate.cache.EhCache.toMap() throws NullPointerException

by Kenny MacLeod (JIRA)

org.hibernate.cache.EhCache.toMap() throws NullPointerException --------------------------------------------------------------- Key: HHH-3248 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3248 Project: Hibernate3 Issue Type: Bug Components: caching (L2) Affects Versions: 3.2.6 Reporter: Kenny MacLeod The toMap() method of org.hibernate.cache.EhCache is not null-safe. The expression cache.get( key ).getObjectValue() Will throw a NPE, since get(key) may return a null in cases where the key exists in the cache, but the value does not, e.g. if it has expired. This should either check for the null, or the list of keys should be obtained using getKeysWithExpiredCheck(), rather than just getKeys(). -- 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

14 years, 9 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3747) Memory leak in EnumType class.

by Paweł Kępka (JIRA)

Memory leak in EnumType class. ------------------------------ Key: HHH-3747 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3747 Project: Hibernate Core Issue Type: Bug Components: core, metamodel Reporter: Paweł Kępka Priority: Critical Holding enum values in static enumValues map in EnumType class causes memory leaks on application server where hibernate is loaded by application server's common classloader (like for default configuration of JBoss4). SoftReference or SessionFactory based caching should be used instead. -- 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

14 years, 9 months

6
19
0 / 0

[Hibernate-JIRA] Created: (HHH-3836) composite-element with null columns in map is ignored

by Benoit Goudreault-Emond (JIRA)

composite-element with null columns in map is ignored ----------------------------------------------------- Key: HHH-3836 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3836 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.0.SP1 Environment: 3.3.0 SP1, noticed with Oracle and H2 but probably happens with all databases Reporter: Benoit Goudreault-Emond Attachments: patate.zip When a composite element with all properties set to NULL is inserted in a map of the said composite element, the data gets inserted to the database but is never retreived when reloading the entity. For instance, with an entity @Entity public class TestEntity { @Id private int id; @CollectionOfElements private Map<String, AccessPeriod> roleAccesses = new HashMap<String, AccessPeriod>(); // boilerplate getters/setters/etc omitted } And AccessPeriod being @Embeddable public class AccessPeriod { public Date startDate; public Date endDate; } If you insert in the map an AccessPeriod with both startDate and endDate set to null and persist the TestEntity, an entry is inserted in the auxiliary table, but when getting the TestEntity back, the map is empty. You get the same problem with a mapping file. This used to work in Hibernate 2.1--I found this out while porting some code to 3.3. See the attached example. You'll need to include Hibernate and h2 (com.h2database:h2 1.0.20061217) on your classpath to run it with the given jdbc.properties, but feel free to change it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

5
6
0 / 0

[Hibernate-JIRA] Created: (HCANN-18) Make sure that the build enforces JDK 5 compilation just like Core does today

by Emmanuel Bernard (JIRA)

Make sure that the build enforces JDK 5 compilation just like Core does today ----------------------------------------------------------------------------- Key: HCANN-18 URL: http://opensource.atlassian.com/projects/hibernate/browse/HCANN-18 Project: Hibernate Commons Annotations Issue Type: Task Affects Versions: 3.2.0 Reporter: Emmanuel Bernard Assignee: Hardy Ferentschik -- 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

14 years, 10 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3318) Allow omitting varchar limit by default in PostgreSQL

by Luke Maurer (JIRA)

Allow omitting varchar limit by default in PostgreSQL ----------------------------------------------------- Key: HHH-3318 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3318 Project: Hibernate3 Issue Type: New Feature Components: core Environment: Hibernate 3.2.6, PostgreSQL 8.3.1 Reporter: Luke Maurer Priority: Minor Essentially, what I'd like is for a String without a given maximum length be mapped as a varchar or text rather than a varchar(255) as is now the case. The maximum doesn't do anything to improve performance or storage efficiency in PostgreSQL, so varchar(255) merely imposes an arbitrary constraint. It would be more idiomatic to use varchar where no limit is given, leaving varchar(n) for cases where the length is limited as a business rule rather than an implementation detail. (Naturally, one can always use @Lob where it's actually *important* that the column be a varchar or text. So this is definitely minor.) -- 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

14 years, 10 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3244) Implement support NVARCHAR type

by Sergey Derugo (JIRA)

Implement support NVARCHAR type -------------------------------- Key: HHH-3244 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3244 Project: Hibernate3 Issue Type: New Feature Components: core Environment: al Reporter: Sergey Derugo JDBC 4.0 allows supports NVARCHAR type, but Hibernate doesn't handle it. Please implement support for NVarchar -- 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

14 years, 10 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-2955) Unnecessary version updates in two cases.

by Sławomir Wojtasiak (JIRA)

Unnecessary version updates in two cases. ----------------------------------------- Key: HHH-2955 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2955 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.5 Environment: JDK 5.0 Reporter: Sławomir Wojtasiak Attachments: HibernateTest.zip I found two situations where hibernate generates unnecessary version updates. Let's illustrate it with a simple example: Session session = SessionFactory.getSession(); Transaction transaction = session.getTransaction(); transaction.begin(); Article a = new Article(); a.setName( "atricle" ); ********************************************* *** Quantity is the owner of the relation *** ********************************************* Quantity q = new Quantity(); q.setName( "quantity" ); q.setArticle( a ); a.getQuantities().add( q ); session.persist( a ); session.flush(); ***** Hibernate generates following SQLs ***** Hibernate: select nextval ('hibernate_sequence') Hibernate: select nextval ('hibernate_sequence') Hibernate: insert into Article (name, version, id) values (?, ?, ?) Hibernate: insert into Quantity (article_id, name, version, id) values (?, ?, ?, ?) ********************************************** a.getQuantities().clear(); session.flush(); *** Hibernate generates following SQLs *** Hibernate: update Article set name=?, version=? where id=? and version=? This update of version field is performed because collection of quantities is marked as dirty, but Article entity is not relation owner so nothing change in database after this clear. Should it works like this? It looks like a bug because database remain unchanged so version changing is unnecessary in my opinion. ****************************************** session.clear(); **** SECOND PROBLEM *** Now I generate true copy of persisted objects. Notice that I use HashSet instead of PersistSet which was set during persist operation. This operation is similar to merging objects prepared by SOAP, during communication with remote client for example. *********************** Article a1 = new Article(); a1.setId( a.getId() ); a1.setName( a.getName() ); a1.setVersion( a.getVersion() ); Quantity q1 = new Quantity(); q1.setArticle( a1 ); q1.setName( q.getName() ); q1.setVersion( q.getVersion() ); q1.setId( q.getId() ); a1.getQuantities().add( q1 ); a1 = (Article)session.merge( a1 ); session.flush(); ***** This operation generates following SQLs ***** Hibernate: select article0_.id as id0_1_, article0_.name as name0_1_, article0_.version as version0_1_, quantities1_.article_id as article4_3_, quantities1_.id as id3_, quantities1_.id as id1_0_, quantities1_.article_id as article4_1_0_, quantities1_.name as name1_0_, quantities1_.version as version1_0_ from Article article0_ left outer join Quantity quantities1_ on article0_.id=quantities1_.article_id where article0_.id=? Hibernate: update Article set name=?, version=? where id=? and version=? It looks like problem is located in replaceElements() method of CollectgionType class (or somewhere near it). Maybe I'm wrong but this collection was checked for changes during merge operation (See this select above.) so why it remains dirty if it contains the same data as database?. I checked this issue on other JPA implementations (OpenJPA for example) and version is not incremented after similar merge operation. ***************************************************** transaction.rollback(); -- 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

14 years, 10 months

3
2
0 / 0

[Hibernate-JIRA] Created: (EJB-318) PostUpdate callback not called after update on a collection / association (@OneToMany for example)

by Aghnar von Salza (JIRA)

PostUpdate callback not called after update on a collection / association (@OneToMany for example) -------------------------------------------------------------------------------------------------- Key: EJB-318 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-318 Project: Hibernate Entity Manager Issue Type: Bug Components: EntityManager Environment: Hibernate core3.2.5, entityManager 3.3.1, annotation 3.3.0, oracle 9i Reporter: Aghnar von Salza Environment is Weblogic 10 (J2EE 5), with Hibernate used as JPA provider There is no PostUpdate callback on an entity when one of its collections of other Entities (for example annoted with @OneToMany) is updated (i mean when one entity element is added or removed). JPA specification says that a postUpate must be called after the update of at least one data of an entity. I think we have to consider that a collection of other entities can be considered as data. -- 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

14 years, 10 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3051) NPE while query.list on a Native SQL, using L2 cache

by Amit Kapoor (JIRA)

NPE while query.list on a Native SQL, using L2 cache ---------------------------------------------------- Key: HHH-3051 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3051 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.5 Environment: Hibernate 3.2.5ga Database Oracle 9i Jdk - 1.4.2_13 EHCache 1.2.3 / OsCache 2.1 both Reporter: Amit Kapoor I get an NPE when i try to execute a native query. Below is the excerpt of the code that throws NPE: String sqlQuery = "select emp_id, emp_first_name from employee_mt"; SQLQuery query = session.createSQLQuery(sqlQuery); query.setCacheable(true).setCacheRegion("TEST_REGION"); query.addScalar("emp_id"); query.addScalar("emp_first_name"); List list = query.list(); query.list() throws the following NPE: java.lang.NullPointerException at org.hibernate.type.TypeFactory.disassemble(TypeFactory.java:451) at org.hibernate.cache.StandardQueryCache.put(StandardQueryCache.java:83) at org.hibernate.loader.Loader.putResultInQueryCache(Loader.java:2194) at org.hibernate.loader.Loader.listUsingQueryCache(Loader.java:2138) at org.hibernate.loader.Loader.list(Loader.java:2096) at org.hibernate.loader.custom.CustomLoader.list(CustomLoader.java:289) at org.hibernate.impl.SessionImpl.listCustomQuery(SessionImpl.java:1695) at org.hibernate.impl.AbstractSessionImpl.list(AbstractSessionImpl.java:142) at org.hibernate.impl.SQLQueryImpl.list(SQLQueryImpl.java:152) at poc.hibernate.caching.QueryCaching.fireNativeSql(QueryCaching.java:112) at poc.hibernate.caching.QueryCaching.fireQuery(QueryCaching.java:38) at poc.hibernate.caching.QueryCaching.main(QueryCaching.java:27) I tried tracing through the Hibernate code code and saw that the types[] in the at the time of execution of types[i].disassemble( row[i], session, owner ) (TypeFactory.disassemble()) was holding both the types as null. However before reaching that piece of code CustomLoader.autoDiscoverTypes(resultset) had already resolved the resultTypes to appropriate values. Hope this helps. -- 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

14 years, 10 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HCANN-20) Update pom to use the new distributationManagement information

by Hardy Ferentschik (JIRA)

Update pom to use the new distributationManagement information -------------------------------------------------------------- Key: HCANN-20 URL: http://opensource.atlassian.com/projects/hibernate/browse/HCANN-20 Project: Hibernate Commons Annotations Issue Type: Task Affects Versions: 3.2.0 Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 3.2.x http://community.jboss.org/wiki/MavenGettingStarted-Developers -- 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

14 years, 10 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-4580) Possible Sybase bug causes AssertionFailure in QueryByExampleTest

by Strong Liu (JIRA)

Possible Sybase bug causes AssertionFailure in QueryByExampleTest ----------------------------------------------------------------- Key: HHH-4580 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4580 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0-Beta-2, 3.5.0.Beta-1, 3.3.2, 3.2.4.sp1 Environment: sybase 15 Reporter: Strong Liu Test QueryByExampleTest.testJunctionNotExpressionQBE fails due to a possible bug in Sybase 15. The same test passes for Sybase 12.5. The test expects two records as a result for a query, but it gets 3. After some debugging with the query that Hibernate generated, I end up with these two simpler ones: select id from Componentizable where not (name like ? and subName1 like ?) select id from Componentizable where not (name like 'hibernate' and subName1 like 'ope%') The first one returns three records, while the second returns two. The interesting part is that if I replace the first parameter in the first query by a hardcoded value ("hibernate"), it still returns 3 records. That means that the problem is probably with the binding of JDBC parameters containing a wildcard % . -- 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

14 years, 10 months

2
5
0 / 0

[Hibernate-JIRA] Created: (ANN-814) OneToOne Unidirectional Support

by Rachit (JIRA)

OneToOne Unidirectional Support ------------------------------- Key: ANN-814 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-814 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.4.0.GA Environment: Oracle 10g, Java 1.5 Reporter: Rachit Priority: Blocker I tried hard for unidirectional OneToOne mapping as below: @Entity @Table(name = "PARTY") public class Party{ private Person person; private String key; @OneToOne(fetch = FetchType.EAGER, cascade = CascadeType.ALL,) @PrimaryKeyJoinColumn(name = "PARTY_ID", referencedColumnName = "PERSON_PARTY_ID") public Person getPerson() { return person; } public void setPerson(Person person) { this.person = person; } @Id @GeneratedValue(generator = "system-uuid") @GenericGenerator(name = "system-uuid", strategy = "uuid") @Column(name = "PARTY_ID", nullable = false) public String getKey() { return key; } private void setKey(String key) { this.key = key; } } and it is one-to-one mapped to Person as: @Entity(name = "Person") @Table(name = "PERSON") public class Person { private String key; @Id @Column(name = "PERSON_PARTY_ID") public String getKey() { return key; } public void setKey(String key) { this.key = key; } } Now in Person, I deliberately dont have sysUUID as generated as then it generates a unique value for person and the association gets lost. With this mapping hibernate throws the following exception : Caused by: org.hibernate.id.IdentifierGenerationException: ids for this class must be manually assigned before calling save(): Person. I read and saw constrained="true" being used in mapping files, which I couldnt use as there is no attribute like it in OneToOne annotation. Please help me out on 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

14 years, 10 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-4727) Add option to specify foreign key name on table with shared primary key used in one-to-one relationship

by Pavla Nováková (JIRA)

Add option to specify foreign key name on table with shared primary key used in one-to-one relationship --------------------------------------------------------------------------------------------------------- Key: HHH-4727 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4727 Project: Hibernate Core Issue Type: Improvement Components: core Affects Versions: 3.3.2 Reporter: Pavla Nováková There is currently no way to specify (user friendly) foreign key name on table with shared primary key used in One-to-One mapping. The most intuitive way would be to accept @ForeignKey on property level (see the comment in the code below) or on entity level (similar way to usage in joined inheritance) or last option may be add parameter in foreign generator. {code} @Entity public class ExampleEntity implements Serializable { @Id @GenericGenerator(name = "foreign-generator", strategy = "foreign", parameters=@Parameter(name="property", value="parentExampleEntity")) @GeneratedValue(generator = "foreign-generator") private Long id; ... @PrimaryKeyJoinColumn @OneToOne(fetch=FetchType.LAZY, optional=false) @org.hibernate.annotations.ForeignKey(name="parent_entity_fk") // this is currently ignored private ParentExampleEntity parentExampleEntity; ... } {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

14 years, 10 months

2
1
0 / 0

[Hibernate-JIRA] Created: (ANN-667) Foreign key name on @OneToOne

by Immo Heikkinen (JIRA)

Foreign key name on @OneToOne ----------------------------- Key: ANN-667 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-667 Project: Hibernate Annotations Issue Type: Bug Components: binder Affects Versions: 3.3.0.ga Environment: Hibernate Core 3.2.5.GA , Hibernate Annotations 3.3.0.GA, Sybase ASE 15 Reporter: Immo Heikkinen Priority: Minor Attachments: Child.java, Parent.java Foreign key constraint name cannot be changed using @org.hibernate.annotations.ForeignKey on a @OneToOne with foreign key. It doesn't matter which class is annotated with @ForeignKey. Please find the test case as an attachment. Original thread on the user forum: http://forum.hibernate.org/viewtopic.php?p=2367400 -- 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

14 years, 10 months

4
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2225) NPE when eager fetching joined component with native SQL query

by Christian Bauer (JIRA)

NPE when eager fetching joined component with native SQL query -------------------------------------------------------------- Key: HHH-2225 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2225 Project: Hibernate3 Type: Bug Components: query-sql Versions: 3.2.0.ga Reporter: Christian Bauer Priority: Minor Item -> many-to-one -> User -> joined component -> billingAddress This: result = session.createSQLQuery("select {i.*}, {u.*}, {ba.*} from ITEM i" + " join USERS u on i.SELLER_ID = u.USER_ID" + " left join BILLING_ADDRESS ba on u.USER_ID = ba.USER_ID" + " where u.USERNAME = :uname") .addEntity("i", Item.class) .addJoin("u", "i.seller") .addJoin("ba", "u.billingAddress") fails with: java.lang.NullPointerException at org.hibernate.loader.DefaultEntityAliases.<init>(DefaultEntityAliases.java:37) at org.hibernate.loader.custom.sql.SQLQueryReturnProcessor.generateCustomReturns(SQLQueryReturnProcessor.java:283) at org.hibernate.loader.custom.sql.SQLCustomQuery.<init>(SQLCustomQuery.java:129) at org.hibernate.engine.query.NativeSQLQueryPlan.<init>(NativeSQLQueryPlan.java:43) at org.hibernate.engine.query.QueryPlanCache.getNativeSQLQueryPlan(QueryPlanCache.java:114) at org.hibernate.impl.AbstractSessionImpl.getNativeSQLQueryPlan(AbstractSessionImpl.java:137) at org.hibernate.impl.AbstractSessionImpl.list(AbstractSessionImpl.java:142) at org.hibernate.impl.SQLQueryImpl.list(SQLQueryImpl.java:150) -- 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

14 years, 11 months

15
24
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues May 2010