August 2011 - 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, 5 months

4
6
0 / 0

[Hibernate-JIRA] Created: (HHH-6425) On Sybase ASE, insert a empty string '' to db, it stores it as single space ' '

by Ren Junyan (JIRA)

On Sybase ASE, insert a empty string '' to db, it stores it as single space ' ' ------------------------------------------------------------------------------- Key: HHH-6425 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6425 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.6.0 Environment: Hibernate 3.6.6, Sybase ASE15.5, JDK 1.6, Windows XP Reporter: Ren Junyan This is a defect of ASE, it fails the test below. testNewSerializableType(org.hibernate.test.lob.SerializableTypeTest) org.hibernate.type.SerializationException: could not deserialize at org.hibernate.util.SerializationHelper.doDeserialize(SerializationHelper.java:250) at org.hibernate.util.SerializationHelper.deserialize(SerializationHelper.java:306) at org.hibernate.type.descriptor.java.SerializableTypeDescriptor.fromBytes(SerializableTypeDescriptor.java:130) at org.hibernate.type.descriptor.java.SerializableTypeDescriptor.wrap(SerializableTypeDescriptor.java:116) at org.hibernate.type.descriptor.java.SerializableTypeDescriptor.wrap(SerializableTypeDescriptor.java:39) at org.hibernate.type.descriptor.sql.VarbinaryTypeDescriptor$2.doExtract(VarbinaryTypeDescriptor.java:62) at org.hibernate.type.descriptor.sql.BasicExtractor.extract(BasicExtractor.java:64) at org.hibernate.type.AbstractStandardBasicType.nullSafeGet(AbstractStandardBasicType.java:253) at org.hibernate.type.AbstractStandardBasicType.nullSafeGet(AbstractStandardBasicType.java:249) at org.hibernate.type.AbstractStandardBasicType.nullSafeGet(AbstractStandardBasicType.java:229) at org.hibernate.type.AbstractStandardBasicType.hydrate(AbstractStandardBasicType.java:330) at org.hibernate.persister.entity.AbstractEntityPersister.hydrate(AbstractEntityPersister.java:2283) at org.hibernate.loader.Loader.loadFromResultSet(Loader.java:1527) at org.hibernate.loader.Loader.instanceNotYetLoaded(Loader.java:1455) at org.hibernate.loader.Loader.getRow(Loader.java:1355) at org.hibernate.loader.Loader.getRowFromResultSet(Loader.java:611) at org.hibernate.loader.Loader.doQuery(Loader.java:829) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:274) at org.hibernate.loader.Loader.loadEntity(Loader.java:2037) at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:86) at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:76) at org.hibernate.persister.entity.AbstractEntityPersister.load(AbstractEntityPersister.java:3293) at org.hibernate.event.def.DefaultLoadEventListener.loadFromDatasource(DefaultLoadEventListener.java:496) at org.hibernate.event.def.DefaultLoadEventListener.doLoad(DefaultLoadEventListener.java:477) at org.hibernate.event.def.DefaultLoadEventListener.load(DefaultLoadEventListener.java:227) at org.hibernate.event.def.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:285) at org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:152) at org.hibernate.impl.SessionImpl.fireLoad(SessionImpl.java:1090) at org.hibernate.impl.SessionImpl.get(SessionImpl.java:1005) at org.hibernate.impl.SessionImpl.get(SessionImpl.java:998) at org.hibernate.test.lob.SerializableTypeTest.testNewSerializableType(SerializableTypeTest.java:82) Caused by: java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2280) at java.io.ObjectInputStream$BlockDataInputStream.readUnsignedShort(ObjectInputStream.java:2761) at java.io.ObjectInputStream$BlockDataInputStream.readUTF(ObjectInputStream.java:2819) at java.io.ObjectInputStream.readString(ObjectInputStream.java:1598) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1319) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1946) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1870) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1752) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1328) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:350) at org.hibernate.util.SerializationHelper.doDeserialize(SerializationHelper.java:244) ... 60 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-853) Review OptimizerStrategy API

by Sanne Grinovero (JIRA)

Review OptimizerStrategy API ---------------------------- Key: HSEARCH-853 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-853 Project: Hibernate Search Issue Type: Improvement Reporter: Sanne Grinovero Fix For: 4.0.0.Alpha2 Not sure if we should still expose the IndexWriter to it. In all cases, interactions OptimizerStrategy <-> Workspace is currently tricky and should be simplified. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

2
6
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-829) Example IdHashShardingStrategy doesn't handle PurgeAll properly

by Sanne Grinovero (JIRA)

Example IdHashShardingStrategy doesn't handle PurgeAll properly --------------------------------------------------------------- Key: HSEARCH-829 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-829 Project: Hibernate Search Issue Type: Task Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 4.0 A PurgeAll command is handled by invoking shardStrategy.getDirectoryProvidersForDeletion(Class<?> entity, Serializable id, String idInString) and passing in null for the second and third arguments. IdHashShardingStrategy should handle this case and return all indexmanagers. Check the documentation to point this out as well. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-745) Empty Index and FacetManagerImpl.getFacets() NullPointerException

by Mike Pugmire (JIRA)

Empty Index and FacetManagerImpl.getFacets() NullPointerException ----------------------------------------------------------------- Key: HSEARCH-745 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-745 Project: Hibernate Search Issue Type: Bug Components: engine Affects Versions: 3.4.0.Final Environment: Hibernate 3.6.4.Final, H2 Reporter: Mike Pugmire When an index is empty and an attempt is made to retrieve a facet with facetManager.getFacets(facetingName) a NullPointerException is thrown as facetResults is null when facetResult.get( facetingName ) is called on line 112. {code} java.lang.NullPointerException at org.hibernate.search.query.engine.impl.FacetManagerImpl.getFacets(FacetManagerImpl.java:112) {code} I'm guessing an empty List<Facet> is an appropriate return value for this situation? -- 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, 5 months

4
9
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-784) Ensure all Analyzers are closed at shutdown

by Sanne Grinovero (JIRA)

Ensure all Analyzers are closed at shutdown ------------------------------------------- Key: HSEARCH-784 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-784 Project: Hibernate Search Issue Type: Bug Components: analyzer Affects Versions: 3.4.0.Final, 3.3.0.Final Reporter: Sanne Grinovero Fix For: 4.0 At least ImmutableSearchFactory is containing a map of analyzers which are not closed at shutdown (close these, and check for similar cases in other components) -- 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, 5 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-854) OptimizerStrategy should be invoked by the backend

by Sanne Grinovero (JIRA)

OptimizerStrategy should be invoked by the backend -------------------------------------------------- Key: HSEARCH-854 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-854 Project: Hibernate Search Issue Type: Task Components: optimizer Reporter: Sanne Grinovero Fix For: 4.0.0.Alpha2 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

3
6
0 / 0

[Hibernate-JIRA] Created: (HHH-5963) TS:Oracle, PostgreSQL: Transaction#commit() throws TransientObjectException, expected JDBCexception - MultiPathCircleCascadeCheckNullibilityFalseTest

by Ondrej Zizka (JIRA)

TS:Oracle, PostgreSQL: Transaction#commit() throws TransientObjectException, expected JDBCexception - MultiPathCircleCascadeCheckNullibilityFalseTest ----------------------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-5963 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5963 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.6.2 Environment: Oracle 10g PostgreSQL 8.2, 8.3 Reporter: Ondrej Zizka Assignee: Strong Liu In MultiPathCircleCascadeCheckNullibilityFalseTest#testMergeEntityWithNonNullableTransientEntity(), TransientObjectException is thrown on commit, whilst JDBCException is expected. For other DBs, it behaves as expectd. -- 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, 5 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5785) HQL UPDATE omits alias when referencing an entity

by Ondrej Medek (JIRA)

HQL UPDATE omits alias when referencing an entity ------------------------------------------------- Key: HHH-5785 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5785 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.3.1 Environment: Hibernate 3.3.1 in JBoss AS 5.1.0, org.hibernate.dialect.HSQLDialect Reporter: Ondrej Medek HQL UPDATE: UPDATE Lesson e SET e.state = 'N' WHERE EXISTS (SELECT 1 FROM LessonOrder lso WHERE lso.lesson = e) produces wrong SQL: update LESSON set lsn_state='N' where exists (select 1 from LESSON_ORDER lessonorde1_ where lessonorde1_.lsn_id=lsn_id) since in the database exists columns if the same name: LESSON.lsn_id and LESSON_ORDER.lsn_id. The problem is, that Hibernate omits the alias "e" in the SQL. When I make a little different query: UPDATE Lesson e SET e.state = 'N' WHERE EXISTS (SELECT 1 FROM LessonOrder lso WHERE lso.lesson.id = e.id) then the resulting SQL is right: update LESSON set lsn_state='N' where exists (select 1 from LESSON_ORDER lessonorde1_ where lessonorde1_.lsn_id=LESSON.lsn_id) However, I think the Hibernate should not omit the alias "e" in either 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

14 years, 5 months

2
1
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, 5 months

2
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues August 2011