July 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HSEARCH-156) Retrofit FieldBridge.set lucene parameters into a LuceneOptions class

by Emmanuel Bernard (JIRA)

Retrofit FieldBridge.set lucene parameters into a LuceneOptions class --------------------------------------------------------------------- Key: HSEARCH-156 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-156 Project: Hibernate Search Issue Type: Improvement Components: mapping Reporter: Emmanuel Bernard Priority: Minor Fix For: 3.1.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

15 years, 10 months

2
4
0 / 0

[Hibernate-JIRA] Commented: (HHH-1657) hql update generate wrong sql with joined subclass hierarcy

by John Baker (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1657?page=c... ] John Baker commented on HHH-1657: --------------------------------- The above executes but doesn't do anything due to the use of the HT_ tables I have linked this to another bug on this issue. The only solution to my problem is raw SQL, which is also the simplest! > hql update generate wrong sql with joined subclass hierarcy > ----------------------------------------------------------- > > Key: HHH-1657 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1657 > Project: Hibernate3 > Issue Type: Bug > Components: query-hql > Environment: Hibernate 3.2.0cr1, Hibernate 3.1.3 > Reporter: Alexey Romanchuk > Assignee: Gail Badner > Priority: Critical > Fix For: 3.2.x, 3.3.x > > > Let suppose that we have two joined subclass entities: Parent (id PK) and Child (id PK) that mapped with joined subclass method. > When I try to update Child by id with hql: > update Child c set c.field = 'value' where c.id = 1234 > hibernate generates joined tables like > insert into HT_parent select child0_.id as id from child child0_ inner join parent child0_1_ on child0_.id=child0_1_.id wher id in = 1234 > look at last condition. hibernate use id WITH OUT tables alias that cause sql exception: column reference "id" is ambiguous -- 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

15 years, 10 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1657) hql update generate wrong sql with joined subclass hierarcy

by John Baker (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1657?page=c... ] John Baker commented on HHH-1657: --------------------------------- Interestingly, when I execute delete from Event where time < x, the following statements are produced: Hibernate: insert into HT_Event select event0_.eventId as eventId from Event event0_ where time<? Hibernate: delete from ISSO where (eventId) IN (select eventId from HT_Event) Hibernate: delete from BasicLogin where (eventId) IN (select eventId from HT_Event) Hibernate: delete from IWALogin where (eventId) IN (select eventId from HT_Event) Hibernate: delete from Login where (eventId) IN (select eventId from HT_Event) Hibernate: delete from Event where (eventId) IN (select eventId from HT_Event) Hibernate: delete from HT_Event I guess this could all be reduced to one statement: delete from Event where time < ? > hql update generate wrong sql with joined subclass hierarcy > ----------------------------------------------------------- > > Key: HHH-1657 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1657 > Project: Hibernate3 > Issue Type: Bug > Components: query-hql > Environment: Hibernate 3.2.0cr1, Hibernate 3.1.3 > Reporter: Alexey Romanchuk > Assignee: Gail Badner > Priority: Critical > Fix For: 3.2.x, 3.3.x > > > Let suppose that we have two joined subclass entities: Parent (id PK) and Child (id PK) that mapped with joined subclass method. > When I try to update Child by id with hql: > update Child c set c.field = 'value' where c.id = 1234 > hibernate generates joined tables like > insert into HT_parent select child0_.id as id from child child0_ inner join parent child0_1_ on child0_.id=child0_1_.id wher id in = 1234 > look at last condition. hibernate use id WITH OUT tables alias that cause sql exception: column reference "id" is ambiguous -- 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

15 years, 10 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1657) hql update generate wrong sql with joined subclass hierarcy

by John Baker (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1657?page=c... ] John Baker commented on HHH-1657: --------------------------------- Alright, I am talking rubbish and Hibernate does not behave that way - this code I'm looking at deletes the classes in that order. However (!), there's another demonstration of the bug at hand. I find it curious that a couple SQL statements are issued where eventId is unqualified but doesn't fail. I wonder if it's because ISSO extends Event where as BasicLogin and IWALogin extend Login (which in turn extends Event)? > hql update generate wrong sql with joined subclass hierarcy > ----------------------------------------------------------- > > Key: HHH-1657 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1657 > Project: Hibernate3 > Issue Type: Bug > Components: query-hql > Environment: Hibernate 3.2.0cr1, Hibernate 3.1.3 > Reporter: Alexey Romanchuk > Assignee: Gail Badner > Priority: Critical > Fix For: 3.2.x, 3.3.x > > > Let suppose that we have two joined subclass entities: Parent (id PK) and Child (id PK) that mapped with joined subclass method. > When I try to update Child by id with hql: > update Child c set c.field = 'value' where c.id = 1234 > hibernate generates joined tables like > insert into HT_parent select child0_.id as id from child child0_ inner join parent child0_1_ on child0_.id=child0_1_.id wher id in = 1234 > look at last condition. hibernate use id WITH OUT tables alias that cause sql exception: column reference "id" is ambiguous -- 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

15 years, 10 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1657) hql update generate wrong sql with joined subclass hierarcy

by John Baker (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1657?page=c... ] John Baker commented on HHH-1657: --------------------------------- Can I add some more thought to this discussion? I have a simple class hierarchy: class Event class ISSO extends Event class Login extends Event class BasicLogin extends Login class IWALogin extends Login And it's mapped using the <joined-subclass> syntax. The database's cascade functionality will delete rows in the relevant tables when a row is deleted from Event. If I issue the HQL: delete from Event where time < 10 then instead of simply executing this, Hibernate issues statements for each type of subclass. While probably not incorrect, it's not very efficient given it only needs to issue one delete statement. This is what I see in the logs: Hibernate: insert into HT_BasicLogin select basiclogin0_.eventId as eventId from BasicLogin basiclogin0_ inner join Login basiclogin0_1_ on basiclogin0_.eventId=basiclogin0_1_.eventId inner join Event basiclogin0_2_ on basiclogin0_.eventId=basiclogin0_2_.eventId where eventId in (select basiclogin1_.eventId from BasicLogin basiclogin1_ inner join Login basiclogin1_1_ on basiclogin1_.eventId=basiclogin1_1_.eventId inner join Event basiclogin1_2_ on basiclogin1_.eventId=basiclogin1_2_.eventId where basiclogin1_2_.time<?) Hibernate: delete from BasicLogin where (eventId) IN (select eventId from HT_BasicLogin) Hibernate: delete from Login where (eventId) IN (select eventId from HT_BasicLogin) Hibernate: delete from Event where (eventId) IN (select eventId from HT_BasicLogin) Hibernate: delete from HT_BasicLogin Hibernate: insert into HT_IWALogin select iwalogin0_.eventId as eventId from IWALogin iwalogin0_ inner join Login iwalogin0_1_ on iwalogin0_.eventId=iwalogin0_1_.eventId inner join Event iwalogin0_2_ on iwalogin0_.eventId=iwalogin0_2_.eventId where eventId in (select iwalogin1_.eventId from IWALogin iwalogin1_ inner join Login iwalogin1_1_ on iwalogin1_.eventId=iwalogin1_1_.eventId inner join Event iwalogin1_2_ on iwalogin1_.eventId=iwalogin1_2_.eventId where iwalogin1_2_.time<?) Hibernate: delete from IWALogin where (eventId) IN (select eventId from HT_IWALogin) Hibernate: delete from Login where (eventId) IN (select eventId from HT_IWALogin) Hibernate: delete from Event where (eventId) IN (select eventId from HT_IWALogin) Hibernate: delete from HT_IWALogin Hibernate: insert into HT_ISSO select isso0_.eventId as eventId from ISSO isso0_ inner join Event isso0_1_ on isso0_.eventId=isso0_1_.eventId where eventId in (select isso1_.eventId from ISSO isso1_ inner join Event isso1_1_ on isso1_.eventId=isso1_1_.eventId where isso1_1_.time<?) 11-07 14:44:46,295 WARN JDBCExceptionReporter.logExceptions:77 - SQL Error: 918, SQLState: 42000 11-07 14:44:46,295 ERROR JDBCExceptionReporter.logExceptions:78 - ORA-00918: column ambiguously defined The last insert statement fails because eventId hasn't been qualified it's immediately after the first where statement). While this bug does need fixing, perhaps someone on the Hibernate team can optimise the DELETE HQL functionality? > hql update generate wrong sql with joined subclass hierarcy > ----------------------------------------------------------- > > Key: HHH-1657 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1657 > Project: Hibernate3 > Issue Type: Bug > Components: query-hql > Environment: Hibernate 3.2.0cr1, Hibernate 3.1.3 > Reporter: Alexey Romanchuk > Assignee: Gail Badner > Priority: Critical > Fix For: 3.2.x, 3.3.x > > > Let suppose that we have two joined subclass entities: Parent (id PK) and Child (id PK) that mapped with joined subclass method. > When I try to update Child by id with hql: > update Child c set c.field = 'value' where c.id = 1234 > hibernate generates joined tables like > insert into HT_parent select child0_.id as id from child child0_ inner join parent child0_1_ on child0_.id=child0_1_.id wher id in = 1234 > look at last condition. hibernate use id WITH OUT tables alias that cause sql exception: column reference "id" is ambiguous -- 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

15 years, 10 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3385) Unable to join fetch a key-many-to-one with Criteria API

by Julien HENRY (JIRA)

Unable to join fetch a key-many-to-one with Criteria API -------------------------------------------------------- Key: HHH-3385 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3385 Project: Hibernate3 Issue Type: Bug Components: query-criteria Affects Versions: 3.3.x Environment: Latest Hibernate trunk Reporter: Julien HENRY Attachments: key-many-to-one-fetch.patch Using setFetchMode("xxx", FetchMode.JOIN) on a key-many-to-one attribute has no result. I'm unable to force initialisation with one query. Please find attached test case. It is very important for me because I'm working on a legacy DB model full of key-many-to-one attributes. -- 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

15 years, 10 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3384) uniqueConstraints={@UniqueConstraint does not work inside the @JoinTable

by Shankar Mandal (JIRA)

uniqueConstraints={@UniqueConstraint does not work inside the @JoinTable ------------------------------------------------------------------------ Key: HHH-3384 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3384 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.3.0.CR1 Reporter: Shankar Mandal I have a Entity where I am trying to put a Unique constraint on the columns of a Join Table. Eclipse does not compile and gives error: UniqueConstraint cannot resolved to a Type Classpath is correctly set because I can use the @UniqueConstraint inside the @Table annotation. @ManyToMany(cascade = CascadeType.ALL) @JoinTable(name="ENVSLifecycle_NextLifecycle", uniqueConstraints={@UniqueConstraint(columnNames={"LIFECYCLE_ID", "NEXTLIFECYCLES_ID"})} ) public Set<Lifecycle> getNextLifecycles() { return nextLifecycles; } -- 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

15 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (EJB-275) CLONE -JarVisitor fails on exploded archives with spaces in path

by Sylvain Laurent (JIRA)

CLONE -JarVisitor fails on exploded archives with spaces in path ---------------------------------------------------------------- Key: EJB-275 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-275 Project: Hibernate Entity Manager Type: Bug Components: EntityManager Versions: 3.2.0.ga Environment: Windows XP, Cygwin Reporter: Sylvain Laurent Assigned to: Emmanuel Bernard Fix For: 3.2.1 When run within a path with spaces, the following test fails due to incorrect conversion of URLs to file paths: org.hibernate.ejb.test.PackagedEntityManagerTest.testExplodedPar The attached patch fixes 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

15 years, 11 months

5
11
0 / 0

[Hibernate-JIRA] Created: (EJB-244) JarVisitor fails on exploded archives with spaces in path

by Mark Hobson (JIRA)

JarVisitor fails on exploded archives with spaces in path --------------------------------------------------------- Key: EJB-244 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-244 Project: Hibernate Entity Manager Type: Bug Components: EntityManager Versions: 3.2.0.ga Environment: Windows XP, Cygwin Reporter: Mark Hobson Attachments: patch.txt When run within a path with spaces, the following test fails due to incorrect conversion of URLs to file paths: org.hibernate.ejb.test.PackagedEntityManagerTest.testExplodedPar The attached patch fixes 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

15 years, 11 months

4
5
0 / 0

[Hibernate-JIRA] Commented: (HHH-1718) Have multiple bag fetches revert to subselect fetching for all but one of the bags

by Morten Andersen-Gott (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1718?page=c... ] Morten Andersen-Gott commented on HHH-1718: ------------------------------------------- I guess it would be 2.1.8 with sub sections, although it's not easy to find the actually quote where it says "vendor implementations should not blow up if more than one List relationship is used without a vendor-specific-annotation". Obviously someone will argue that this means that blowing up is according to the spec :-P > Have multiple bag fetches revert to subselect fetching for all but one of the bags > ---------------------------------------------------------------------------------- > > Key: HHH-1718 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1718 > Project: Hibernate3 > Issue Type: Improvement > Components: core, query-criteria, query-hql > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Fix For: hql+collection > > Attachments: hibernate_eksempel.zip > > > Follow on to HHH-1413. Multiple bag fetches were simply disallowed as the resolution to that particular case in the interest of working around that issue. > The correct longer term solution is to not fetch all the bags at once, ideally reverting to subselect fetching for all but one of the bags. -- 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

15 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues July 2008