September 2007 - hibernate-issues

[Hibernate-JIRA] Created: (HHH-2357) Patch to work around setDecimal() bug with Oracle JDBC driver < 10.2.0.4 and JDK >= 1.5 (bug 5527479

by Benoit Goudreault-Emond (JIRA)

Patch to work around setDecimal() bug with Oracle JDBC driver < 10.2.0.4 and JDK >= 1.5 (bug 5527479 ---------------------------------------------------------------------------------------------------- Key: HHH-2357 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2357 Project: Hibernate3 Type: Patch Components: core Versions: 3.2.1 Environment: Hibernate 3.2.1, Oracle 9i, Oracle 10g, JDK 1.5+ Reporter: Benoit Goudreault-Emond Attachments: WorkaroundForOracleBrokenSetDecimal.patch First, see http://www.javalobby.org/java/forums/t88158.html In a nutshell, JDK 1.5 changed the representation of BigDecimal; namely, they changed totally the way toString() works. Nobody is sure how Oracle parses out the BigDecimal for storage inside the database, but it seems BigDecimals with negative scales don't work well. It's not really this surprising, given that Sun did something a bit evil here (changing the contract of the scale property, for one). The proposed workarounds from Oracle: 1) stay with JDK 1.4 (not an option when you've written several thousand lines of generic-aware code, retroweaver nonwithstanding) 2) wait for their patched JDBC driver. However, they won't issue a patch for Oracle 9i, and those using the OCI driver are kinda stuck. Plus, Oracle's patch isn't there yet. This patch is not necessarily meant to go in the main Hibernate code; it is, after all, Oracle's bug. Still, the patch itself is harmless even for other databases (it simply rescales the BigDecimal), and if it's useful to someone, great. It seems to be a good solution in the meantime. I've marked this bug as MAJOR because it can lead to data corruption--the BigDecimal put in is not the one you get back. -- 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

17 years, 7 months

5
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2850) boolean substitution does not work

by Ivo Abeloos (JIRA)

boolean substitution does not work ---------------------------------- Key: HHH-2850 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2850 Project: Hibernate3 Issue Type: Bug Components: query-sql Affects Versions: 3.2.5 Environment: Windows XP, Hibernate 3.2.5, Derby Reporter: Ivo Abeloos Priority: Critical In hibernate configuration we have configured the following key: hibernate.query.substitutions=true '1', false '0', yes 'Y', no 'N' When the AST is transformed into SQL, the true is substituted by 1 instead of the '1' characters. After some examination we saw that the BooleanLiteralNode just uses the dialect to replace the boolean value and ignores the tokenReplacements of the QueryTranslatorImpl. -- 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

17 years, 7 months

5
4
0 / 0

[Hibernate-JIRA] Created: (EJB-266) lazy initialization of one-to-many bidirectional relationships through cascade.persist

by sara forghani (JIRA)

lazy initialization of one-to-many bidirectional relationships through cascade.persist -------------------------------------------------------------------------------------- Key: EJB-266 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-266 Project: Hibernate Entity Manager Type: Bug Components: EntityManager Versions: 3.2.1 Environment: hibernate 3.2.2, hibernate-entitymanager 3.2.1.ga Reporter: sara forghani Priority: Critical hibernate initializes lazy objects traversed by the persist operation; for example, in this case (the project is attached): class A has bidirectional one-to-many relationship to classes B1, B2, B3, B4 (b1List, b2List, b3List, b4List) B1 has bidirectional one-to-many relationship to C1 (c1List) B2 has bidirectional one-to-many relationship to C2 (c2List) if we try persisting C2, it will also initialize B1, C1, B4 ... and other existing C2's (you may find a more complete description of the issue at http://forum.hibernate.org/viewtopic.php?p=2340004#2340004) -- 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

17 years, 7 months

3
8
0 / 0

[Hibernate-JIRA] Created: (HHH-2741) Deleting objects on inverse end of many to many relationship

by James Roper (JIRA)

Deleting objects on inverse end of many to many relationship ------------------------------------------------------------ Key: HHH-2741 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2741 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.1 Reporter: James Roper I have a Class, Stock, that has a bidirectional many to many indexed relationship with itself. Here is the mapping: @ManyToMany @JoinTable(name = "input_output_stock", joinColumns = @JoinColumn(name = "id_output_stock"), inverseJoinColumns = @JoinColumn(name = "id_input_stock")) @IndexColumn(name = "ix_input_stock") @ForeignKey(name = "stock_output_fk", inverseName = "stock_input_fk") private List<Stock> inputStock; @ManyToMany(mappedBy = "inputStock") private List<Stock> outputStock; When I delete stock objects, Hibernate runs the following queries: Hibernate: delete from input_output_stock where id_output_stock=? Hibernate: delete from stock where id=? This causes problems when deleting objects that are at the inverse end of the relationship. Shouldn't Hibernate be running another query to delete where id_input_stock=? As far as I can see in the Hibernate documentation and the EJB3 spec, there is no mention that this is the case. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 7 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2119) reloading a detached object with a collection fails

by Gregory Kotsaftis (JIRA)

reloading a detached object with a collection fails --------------------------------------------------- Key: HHH-2119 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2119 Project: Hibernate3 Type: Bug Versions: 3.1.3 Environment: Hibernate 3.1.3 firebird 1.5.3.4870 with Jaybird-2.1.0 java 1.5.0_07 Reporter: Gregory Kotsaftis Hi, 1) I have a simple object <O> with a collection loaded and use <version> for both (no second level cache) 2) The object <O> is associated with session A, via <O> = load(CLASS, <ID>) 3) The session <A> is later closed because e.g. an exception occurs 4) Another session is opened later on, session B 5) If load(<O>, <ID>) is called an NonUniqueObjectException is thrown (a different object with the same identifier value was already associated with the session) 6) If instead I use the session.refresh(<O>) no exception is thrown, the object is reloaded ok. It seems this issue might be related with: http://opensource.atlassian.com/projects/hibernate/browse/HHH-511 but i cannot be sure. Part of the stacktrace: org.hibernate.NonUniqueObjectException: a different object with the same identifier value was already associated with the session: [gr.metadata.orthomed.db.Patient#23] at org.hibernate.event.def.DefaultLoadEventListener.load(DefaultLoadEventListener.java:132) at org.hibernate.event.def.DefaultLoadEventListener.returnNarrowedProxy(DefaultLoadEventListener.java:202) at org.hibernate.event.def.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:169) at org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:87) at org.hibernate.impl.SessionImpl.fireLoad(SessionImpl.java:862) at org.hibernate.impl.SessionImpl.load(SessionImpl.java:770) at gr.metadata.lib.hibernate.HibernateHelper.reloadObject(HibernateHelper.java:230) -- 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

17 years, 7 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-2605) Since 3.2.4 no value specified for row id

by Igor A Tarasov (JIRA)

Since 3.2.4 no value specified for row id ----------------------------------------- Key: HHH-2605 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2605 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.4 Environment: hibernate-3.2.4 mysql-5.0.27-1.fc6 mysql-connector-java-5.0.5-bin.jar Reporter: Igor A Tarasov Problem starts in 3.2.4 version, but in 3.2.3 was all right. Row ID column is specified as parameter in query, but no value is specified. Row ID column is autoincrement in MySQL tabled. 10.05.07 14:26:29 DEBUG [btpool0-0]: SQL - insert into PaymentDO (_version, comment, created, customer_id, nalichka, newBalance, payDate, sum, id) values (?, ?, ?, ?, ?, ?, ?, ?, ?) 10.05.07 14:26:29 TRACE [btpool0-0]: AbstractBatcher - preparing statement 10.05.07 14:26:29 TRACE [btpool0-0]: AbstractEntityPersister - Dehydrating entity: [org.dicr.isp.data.PaymentDO#<null>] 10.05.07 14:26:29 TRACE [btpool0-0]: LongType - binding '0' to parameter: 1 10.05.07 14:26:29 TRACE [btpool0-0]: StringType - binding null to parameter: 2 10.05.07 14:26:29 TRACE [btpool0-0]: TimestampType - binding '2007-05-10 14:26:29' to parameter: 3 10.05.07 14:26:29 TRACE [btpool0-0]: VersionValue - version unsaved-value strategy UNDEFINED 10.05.07 14:26:29 TRACE [btpool0-0]: IdentifierValue - id unsaved-value: 0 10.05.07 14:26:29 TRACE [btpool0-0]: LongType - binding '18128' to parameter: 4 10.05.07 14:26:29 TRACE [btpool0-0]: BooleanType - binding 'false' to parameter: 5 10.05.07 14:26:29 TRACE [btpool0-0]: FloatType - binding '3.0' to parameter: 6 10.05.07 14:26:29 TRACE [btpool0-0]: TimestampType - binding '2007-05-10 00:00:00' to parameter: 7 10.05.07 14:26:29 TRACE [btpool0-0]: FloatType - binding '3.0' to parameter: 8 10.05.07 14:26:29 DEBUG [btpool0-0]: AbstractBatcher - about to close PreparedStatement (open PreparedStatements: 1, globally: 1) 10.05.07 14:26:29 TRACE [btpool0-0]: AbstractBatcher - closing statement 10.05.07 14:26:29 DEBUG [btpool0-0]: JDBCExceptionReporter - could not insert: [org.dicr.isp.data.PaymentDO] [insert into PaymentDO (_version, comment, created, customer_id, nalichka, newBalance, payDate, sum, id) values (?, ?, ?, ?, ?, ?, ?, ?, ?)] java.sql.SQLException: No value specified for parameter 9 at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:910) at com.mysql.jdbc.PreparedStatement.fillSendPacket(PreparedStatement.java:1674) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1512) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1455) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1440) at org.hibernate.id.IdentityGenerator$GetGeneratedKeysDelegate.executeAndExtract(IdentityGenerator.java:73) at org.hibernate.id.insert.AbstractReturningDelegate.performInsert(AbstractReturningDelegate.java:33) at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:2158) at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:2638) at org.hibernate.action.EntityIdentityInsertAction.execute(EntityIdentityInsertAction.java:48) at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:250) at org.hibernate.event.def.AbstractSaveEventListener.performSaveOrReplicate(AbstractSaveEventListener.java:298) at org.hibernate.event.def.AbstractSaveEventListener.performSave(AbstractSaveEventListener.java:181) at org.hibernate.event.def.AbstractSaveEventListener.saveWithGeneratedId(AbstractSaveEventListener.java:107) at org.hibernate.ejb.event.EJB3PersistEventListener.saveWithGeneratedId(EJB3PersistEventListener.java:49) at org.hibernate.event.def.DefaultPersistEventListener.entityIsTransient(DefaultPersistEventListener.java:131) at org.hibernate.event.def.DefaultPersistEventListener.onPersist(DefaultPersistEventListener.java:87) at org.hibernate.event.def.DefaultPersistEventListener.onPersist(DefaultPersistEventListener.java:38) at org.hibernate.impl.SessionImpl.firePersist(SessionImpl.java:618) at org.hibernate.impl.SessionImpl.persist(SessionImpl.java:592) at org.hibernate.impl.SessionImpl.persist(SessionImpl.java:596) at org.hibernate.ejb.AbstractEntityManagerImpl.persist(AbstractEntityManagerImpl.java:213) at org.dicr.isp.data.HibernateDataManager.createPayment(HibernateDataManager.java:692) -- 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

17 years, 7 months

14
27
0 / 0

[Hibernate-JIRA] Created: (ANN-484) Do not filter classes on queries when we know that Directory <-> Entity is a one to one relationship

by Emmanuel Bernard (JIRA)

Do not filter classes on queries when we know that Directory <-> Entity is a one to one relationship ---------------------------------------------------------------------------------------------------- Key: ANN-484 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-484 Project: Hibernate Annotations Type: Improvement Components: lucene Reporter: Emmanuel Bernard Priority: 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

17 years, 7 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HV-36) DefaultValidatorMessages_ja.properties

by WATANABE Takashi (JIRA)

DefaultValidatorMessages_ja.properties -------------------------------------- Key: HV-36 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-36 Project: Hibernate Validator Issue Type: Patch Reporter: WATANABE Takashi Priority: Trivial Attachments: 20070705_2145.patch.txt, 20070705_2145.sample.DefaultValidatorMessages_ja.png http://anonsvn.jboss.org/repos/hibernate/trunk/HibernateExt/validator/src... I'm not a professional translator, and turned to translators of the JJBug(Japan JBoss User Group; www.jbug.jp). http://lists.sourceforge.jp/mailman/archives/japan-jbug-translators/2007-... Mr. Kimura gave me some good advice there, and (I believe) I managed to translate it into Japanese that is not only straightforward, but also respectful of the original text. I assumed the messages of assertFalse, assertTrue, notNull, notEmpty, and pattern were meant for programmers rather than end users because of the existence of words such as "assertion", "null", and "regex(and match)". I hope that's useful. -- 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

17 years, 7 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HV-14) Minor typo in regular expression in class EmailValidator

by Talal Al-Tamimi (JIRA)

Minor typo in regular expression in class EmailValidator -------------------------------------------------------- Key: HV-14 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-14 Project: Hibernate Validator Issue Type: Bug Components: validators Affects Versions: 3.0.0.ga Reporter: Talal Al-Tamimi Priority: Trivial It looks like there is a small mistake in the regular expression below from class EmailValidator: private static String ATOM = "[^\\x00-\\x1F^\$^\$^\\<^\\>^\\@^\\,^\\(;^\\:^\\\\^\\\"^\\.^\\[^\\]^\\s]"; The substring to exclude a semicolon should be "^\\;" but above it is shown as "^\\(;" Instead of excluding a semicolon, this will exclude the left parenthesis (which is already done earlier in the regular expression) and allow a semicolon. Also, the initialize method is instantiating instance variable 'pattern' twice. The first seems to be an older line of code, so it might be a good idea to comment it out. This is not a bug though, since the first instance is just discarded. -- 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

17 years, 7 months

3
6
0 / 0

[Hibernate-JIRA] Created: (HHH-2506) Make javassist the default ByteCodeProvider

by Mike Youngstrom (JIRA)

Make javassist the default ByteCodeProvider ------------------------------------------- Key: HHH-2506 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2506 Project: Hibernate3 Type: Improvement Components: core Versions: 3.2.2 Reporter: Mike Youngstrom See HHH-2505 -- 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

17 years, 7 months

2
4
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues September 2007