July 2009 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-2603) Deprecate the Session.connection() method

by Steve Ebersole (JIRA)

Deprecate the Session.connection() method ----------------------------------------- Key: HHH-2603 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2603 Project: Hibernate3 Issue Type: Deprecation Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.2.4 Deprecate the Session.connection() method, in favor of a "JDBC work" API. Schedule for removal in 4.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

16 years, 1 month

14
26
0 / 0

[Hibernate-JIRA] Created: (HHH-3957) Audited Null Embeddable objects not returned as null

by Aslak Knutsen (JIRA)

Audited Null Embeddable objects not returned as null ---------------------------------------------------- Key: HHH-3957 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3957 Project: Hibernate Core Issue Type: Bug Components: envers Environment: 3.5.0-SNAPSHOT, Oracle, HSQL Reporter: Aslak Knutsen HIbernate Core and Hibernate Envers have different behaviour when it comes to handling null embeddable objects. Hibernate Core will return the Embeddable object as null when all of its properties are, Hibernate Envers will return the Embeddable object with all null properties. Description, TestCase: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=156716 -- 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

16 years, 1 month

3
3
0 / 0

[Hibernate-JIRA] Created: (HBX-1120) Incorrect ManyToMany Generation

by Henry Chan (JIRA)

Incorrect ManyToMany Generation ------------------------------- Key: HBX-1120 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1120 Project: Hibernate Tools Issue Type: Bug Environment: MySQL v5.1 Hibernate Tools 3.2.4 Reporter: Henry Chan When I run the reverse Engineering Tool to generate my classes, one of these classes does not have the correct manytomany annotation defined correctly: In the example below, the I have User, User_Role and Role The User classgets generated correctly: User.java ... @ManyToMany(fetch = FetchType.LAZY) @JoinTable(name = "user_role", catalog = "exms", joinColumns = { @JoinColumn(name = "userID", nullable = false, updatable = false) }, inverseJoinColumns = { @JoinColumn(name = "roleID", nullable = false, updatable = false) }) public Set<Role> getRoles() { return this.roles; } but Role.java class isn't correct: @ManyToMany(fetch = FetchType.LAZY, mappedBy = "roles") public Set<User> getUsers() { return this.users; } Where is the @JoinTable in Role.java? DROP TABLE IF EXISTS `exms`.`Role` ; CREATE TABLE IF NOT EXISTS `exms`.`Role` ( `roleID` INT NOT NULL AUTO_INCREMENT , `roleName` VARCHAR(45) NOT NULL , PRIMARY KEY (`roleID`) ) ENGINE = InnoDB; -- ----------------------------------------------------- -- Table `exms`.`Login` -- ----------------------------------------------------- DROP TABLE IF EXISTS `exms`.`Login` ; CREATE TABLE IF NOT EXISTS `exms`.`Login` ( `loginID` INT NOT NULL AUTO_INCREMENT , `userID` INT NULL , `timeStamp` DATETIME NULL , `failedLogins` INT NULL , PRIMARY KEY (`loginID`) , INDEX `fk_Login_User` (`userID` ASC) , CONSTRAINT `fk_Login_User` FOREIGN KEY (`userID` ) REFERENCES `exms`.`User` (`userID` ) ON DELETE NO ACTION ON UPDATE NO ACTION) ENGINE = InnoDB; -- ----------------------------------------------------- -- Table `exms`.`User_Role` -- ----------------------------------------------------- DROP TABLE IF EXISTS `exms`.`User_Role` ; CREATE TABLE IF NOT EXISTS `exms`.`User_Role` ( `userID` INT NOT NULL , `roleID` INT NOT NULL , INDEX `fk_User_Role_User` (`userID` ASC) , INDEX `fk_User_Role_Role` (`roleID` ASC) , PRIMARY KEY (`userID`, `roleID`) , CONSTRAINT `fk_User_Role_User` FOREIGN KEY (`userID` ) REFERENCES `exms`.`User` (`userID` ) ON DELETE NO ACTION ON UPDATE NO ACTION, CONSTRAINT `fk_User_Role_Role` FOREIGN KEY (`roleID` ) REFERENCES `exms`.`Role` (`roleID` ) ON DELETE NO ACTION ON UPDATE NO ACTION) ENGINE = InnoDB; -- 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

16 years, 1 month

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3686) Sybase - QueryCacheTest.testQueryCacheInvalidation fails

by Gail Badner (JIRA)

Sybase - QueryCacheTest.testQueryCacheInvalidation fails -------------------------------------------------------- Key: HHH-3686 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3686 Project: Hibernate Core Issue Type: Bug Reporter: Gail Badner Assignee: Gail Badner By default, Sybase string comparisons are case-insensitive. It can be configured to be case-insensitive. It may be possible to determine which is configured by looking at DatabaseMetaData to return the appropriate value for SybaseDialect.areStringComparisonsCaseInsensitive(). -- 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

16 years, 1 month

2
9
0 / 0

[Hibernate-JIRA] Created: (EJB-315) unnecessary update when merge managed entity

by Jifeng Liu (JIRA)

unnecessary update when merge managed entity -------------------------------------------- Key: EJB-315 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-315 Project: Hibernate Entity Manager Issue Type: Bug Affects Versions: 3.3.1.GA Environment: Hibernate Core 3.2.5.ga Hibernate Annotations 3.3.0 GA hsqldb Reporter: Jifeng Liu Attachments: testcase.zip If the entity in em.merge(entity) is managed entity, the merge operation should be ignored. However it issues a update statement in the test case even if there is no changes. In the test case, Parent entity has a list of Image entity with Many-To-Many relation. em.merge() somehow marks the list as dirty, which causes the update statement. The following is trace log of the test case. 07.20,23 INFO ASTQueryTranslatorFactory - Using ASTQueryTranslatorFactory 07.20,601 DEBUG SQL - /* insert test.Parent */ insert into Parent (updateDateTime, Parent_No) values (?, ?) 07.20,617 DEBUG SQL - /* insert test.Image */ insert into Image (name, imageNo) values (?, ?) 07.20,617 DEBUG SQL - /* insert collection row test.Parent.images */ insert into Parent_Image (Parent_Parent_No, images_ imageNo) values (?, ?) 07.20,632 DEBUG SQL - /* load test.Parent */ select parent0_.Parent_No as Parent1_0_0_, parent0_.updateDateTime as updat eDa2_0_0_ from Parent parent0_ where parent0_.Parent_No=? 07.20,648 DEBUG SQL - /* load collection test.Parent.images */ select images0_.Parent_Parent_No as Parent1_1_, images0_. images_imageNo as images2_1_, image1_.imageNo as imageNo1_0_, image1_.name as name1_0_ from Parent_Image images0_ left o uter join Image image1_ on images0_.images_imageNo=image1_.imageNo where images0_.Parent_Parent_No=? 07.20,679 DEBUG SQL - /* update test.Parent */ update Parent set updateDateTime=? where Parent_No=? and updateDateTime=? 07.20,679 DEBUG SQL - /* delete collection test.Parent.images */ delete from Parent_Image where Parent_Parent_No=? 07.20,679 DEBUG SQL - /* insert collection row test.Parent.images */ insert into Parent_Image (Parent_Parent_No, images_ imageNo) values (?, ?) -- 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

16 years, 1 month

4
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3560) Assume entities relationships as unversioned by default

by Adam Warski (JIRA)

Assume entities relationships as unversioned by default ------------------------------------------------------- Key: HHH-3560 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3560 Project: Hibernate Core Issue Type: New Feature Components: envers Reporter: Adam Warski http://www.jboss.com/index.html?module=bb&op=viewtopic&t=141471 Assume that each relation between entities is unversioned unless entity is explicitly annotated with @Versioned. In current implementation if versioned entity has reference to non-versioned entity an MappingException is being thrown unless the @Unversioned annotation is used in appropriate field. If there is a lot of entities that are referenced but not versioned it requires to apply lot of @Unversioned annotations. This is quite error-prone while it is easy to forgot about some fields. I've suggest to treat each reference to entity as it is annotated with @Unversioned unless the entity is annotated with @Versioned. In other words treat entities ralationships as implicitly @Unversioned unless @Versioned is not set explicitly. -- 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

16 years, 1 month

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-4010) support auditing of entity having reference (many-to-one relation) to not audited entity

by Tomasz Bech (JIRA)

support auditing of entity having reference (many-to-one relation) to not audited entity ---------------------------------------------------------------------------------------- Key: HHH-4010 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4010 Project: Hibernate Core Issue Type: New Feature Components: envers Affects Versions: 3.3.2 Reporter: Tomasz Bech There is an annotated (with @Audited) entity class (lets say - class A), it has ManyToOne reference to another class (lets named this class as B). For various reason, class B should stay as not audited - for example because B is a static dictionary class with milion of records, so duplications in the Audited table is not advised or possible. Currently this is not supported by evners (target entity must me audited as well for now). Related topic on forum: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=157846 We are going to implement this feature and provide the patch 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

16 years, 1 month

2
3
0 / 0

[Hibernate-JIRA] Created: (HV-186) ResourceBundleMessageInterpolator has to allow all characters as message parameter

by Hardy Ferentschik (JIRA)

ResourceBundleMessageInterpolator has to allow all characters as message parameter ---------------------------------------------------------------------------------- Key: HV-186 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-186 Project: Hibernate Validator Issue Type: Bug Affects Versions: 4.0.0.Beta2 Reporter: Hardy Ferentschik Fix For: 4.0.0.GA At the moment only word characters and '.' are allowed. This excludes for example '-'. However, does it really make sense to allow any character? -- 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

16 years, 1 month

1
5
0 / 0

[Hibernate-JIRA] Created: (HHH-2830) Insert error ignored when using sybase generated identity column

by Martin van Dijken (JIRA)

Insert error ignored when using sybase generated identity column ---------------------------------------------------------------- Key: HHH-2830 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2830 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.2 Environment: Hibernate 3.2.2, Sybase 12.5.3 Reporter: Martin van Dijken All our tables have a single database generated identity column. This column is specified in Sybase as: objectId numeric(12) identity A little while ago, Hibernate started throwing NonUniqueObjectExceptions upon insert of a certain object. It turns out, the insert statement could not possibly succeed as the value of one of the columns was larger than the database column. The error is however ignored because Hibernate generates a query: insert into objectTable (objectName, objectNumericErrorField) values (?,?) select @@ identity The value of objectNumericErrorField was larger than the database column allows. The insert statement would therefore fail. The select @@identity however would succeed, only because no new row was inserted it would return the previous ID. Hibernate then assumes the entire query worked fine and would assign the already assigned id to a different object. It would then check whether or not the id was already in use and throw a NonUniqueObjectException -- 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

16 years, 1 month

5
6
0 / 0

[Hibernate-JIRA] Created: (HHH-2656) Using EntityMode.DOM4J results in an exception when mapping more than one collection to the root node (node=".")

by Andries Schutte (JIRA)

Using EntityMode.DOM4J results in an exception when mapping more than one collection to the root node (node=".") ---------------------------------------------------------------------------------------------------------------- Key: HHH-2656 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2656 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.4.sp1 Environment: Hibernate 3.2.4 SP1, tested with MySQL 5.0. Reporter: Andries Schutte When mapping multiple collections to the root node, an exception results (mapping and exception stack trace is shown below). This works fine if only one collection is mapped to the root node, or if one explicitly specifies unique names for each collection parent node. We are unfortunately restricted by having to use customer-defined XSDs, so this is a show-stopper for us. <?xml version="1.0"?> <!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD 3.0//EN" "http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd"> <hibernate-mapping> <class entity-name="ProcessImpl" table="PROCESSES" node="Process"> <id name="sysID" column="PROCESS_ID" node="sysID" type="string"/> <property name="version" column="PROCESS_VERSION" node="version" type="string"/> <property name="processType" column="PROCESS_TYPE" node="processType" type="string"/> <property name="status" column="PROCESS_STATE" node="status" type="string"/> <property name="createDate" column="PROCESS_CREATE_DATE" node="createDate" type="timestamp"/> <property name="creator" column="PROCESS_CREATOR" node="creator" type="string"/> <property name="transactionNumber" column="PROCESS_TX_NUMBER" node="transactionNumber" type="long"/> <property name="modifiedDate" column="PROCESS_MOD_DATE" node="modifiedDate" type="timestamp"/> <property name="modifier" column="PROCESS_MODIFIER" node="modifier" type="string"/> <property name="title" column="PROCESS_TITLE" node="title" type="string"/> <property name="timer" column="PROCESS_TIMER" node="timer" type="string"/> <property name="currentCSTime" column="PROCESS_CS_TIME" node="currentCSTime" type="timestamp"/> <bag name="requiredActivities" table="REQ_ACTIVITIES" node = "." embed-xml="true" lazy="false" cascade="all"> <key column="PROCESS_ID" not-null="true"/> <element column="REQ_ACTIVITY" type="text" node="requiredActivity"/> </bag> <bag name="retractedGuidelines" table="RET_GUIDELINES" node = "." embed-xml="true" lazy="false" cascade="all"> <key column="PROCESS_ID" not-null="true"/> <element column="RET_GUIDELINE" type="text" node="retractedGuideline"/> </bag> <set name="suspendedGuidelines" node = "." embed-xml="true" lazy="false" cascade="all"> <key column="PROCESS_ID" not-null="true"/> <one-to-many entity-name="SuspendedGuidelineImpl" embed-xml="true" node="suspendedGuideline"/> </set> </class> </hibernate-mapping> Exception stack trace: [6/6/07 22:11:41:246 GMT] 00000012 SystemErr R org.hibernate.HibernateException: Found shared references to a collection: ProcessImpl.retractedGuidelines at org.hibernate.engine.Collections.processReachableCollection(Collections.java:163) at org.hibernate.event.def.FlushVisitor.processCollection(FlushVisitor.java:37) at org.hibernate.event.def.AbstractVisitor.processValue(AbstractVisitor.java:101) at org.hibernate.event.def.AbstractVisitor.processValue(AbstractVisitor.java:61) at org.hibernate.event.def.AbstractVisitor.processEntityPropertyValues(AbstractVisitor.java:55) at org.hibernate.event.def.DefaultFlushEntityEventListener.onFlushEntity(DefaultFlushEntityEventListener.java:131) at org.hibernate.event.def.AbstractFlushingEventListener.flushEntities(AbstractFlushingEventListener.java:196) at org.hibernate.event.def.AbstractFlushingEventListener.flushEverythingToExecutions(AbstractFlushingEventListener.java:76) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:26) at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000) at com.resonant.persistence.ExternalDataMgrHibernateDom4jImpl.persistHibernateEntity(ExternalDataMgrHibernateDom4jImpl.java:194) at com.resonant.persistence.ExternalDataMgrHibernateDom4jImpl.store(ExternalDataMgrHibernateDom4jImpl.java:172) at com.resonant.persistence.PersistenceHibernateDom4jImpl.storeObject(PersistenceHibernateDom4jImpl.java:215) at com.resonant.persistence.ejb.PersistenceLocalBean.storeObject(PersistenceLocalBean.java:192) at com.resonant.persistence.ejb.EJSLocalStatelessPersistenceLocalEJB_68e55914.storeObject(EJSLocalStatelessPersistenceLocalEJB_68e55914.java:1179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at org.springframework.ejb.access.LocalSlsbInvokerInterceptor.invoke(LocalSlsbInvokerInterceptor.java:65) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at $Proxy2.storeObject(Unknown Source) at com.resonant.hub.processmanager.ProcessHubImpl.startProcess(ProcessHubImpl.java:179) at com.resonant.hub.processmanager.ejb.ProcessHubBean.startProcess(ProcessHubBean.java:138) at com.resonant.hub.processmanager.ejb.EJSRemoteStatelessProcessHubEJB_f45832db.startProcess(EJSRemoteStatelessProcessHubEJB_f45832db.java:208) at com.resonant.hub.processmanager.ejb._EJSRemoteStatelessProcessHubEJB_f45832db_Tie.startProcess(_EJSRemoteStatelessProcessHubEJB_f45832db_Tie.java:261) at com.resonant.hub.processmanager.ejb._EJSRemoteStatelessProcessHubEJB_f45832db_Tie._invoke(_EJSRemoteStatelessProcessHubEJB_f45832db_Tie.java:122) at com.ibm.CORBA.iiop.ServerDelegate.dispatchInvokeHandler(ServerDelegate.java:613) at com.ibm.CORBA.iiop.ServerDelegate.dispatch(ServerDelegate.java:466) at com.ibm.rmi.iiop.ORB.process(ORB.java:503) at com.ibm.CORBA.iiop.ORB.process(ORB.java:1552) at com.ibm.rmi.iiop.Connection.respondTo(Connection.java:2673) at com.ibm.rmi.iiop.Connection.doWork(Connection.java:2551) at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java:62) at com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.java:95) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1510) -- 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

16 years, 1 month

2
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues July 2009