August 2010 - hibernate-issues - Jboss List Archives

[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

12 years, 10 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

12 years, 10 months

3
8
0 / 0

[Hibernate-JIRA] Created: (HHH-5413) null values for columns mapped as "boolean" cause exception when saving entity with Sybase jdbc4

by Strong Liu (JIRA)

null values for columns mapped as "boolean" cause exception when saving entity with Sybase jdbc4 ------------------------------------------------------------------------------------------------ Key: HHH-5413 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5413 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.6.0.Beta1, 3.5.4, 3.5.3 Environment: Sybase jdbc4 Reporter: Strong Liu ASE doesn't allow 'null' value for 'BIT' datatype; While performing insert operation using jconn3.jar it permit you to have 'null' value, this 'null' value is converted into bit 0 by jconn3 & hence ASE doesn't throw any exception; But incase of jconn4.jar 'null' value is not converted into bit 0, hence jconn4 directly reports an exception for 'null' value(which is the expected correct behavior) 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. 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

12 years, 10 months

2
2
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

12 years, 11 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

12 years, 11 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

12 years, 11 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

12 years, 11 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

12 years, 11 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

12 years, 11 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

12 years, 11 months

6
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues August 2010