October 2006 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Updated: (HHH-1931) verify that the instrument tasks actually work

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1931?page=all ] Steve Ebersole updated HHH-1931: -------------------------------- Fix Version: 3.2.0.cr5 (was: 3.2.0.cr4) (was: 3.2.1) > verify that the instrument tasks actually work > ---------------------------------------------- > > Key: HHH-1931 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1931 > Project: Hibernate3 > Type: Task > Components: core > Reporter: Steve Ebersole > Assignee: Scott Marlow > Fix For: 3.2.0.cr5 > Attachments: InstrumentBugTest.zip > > > It appears they may not in all cases. -- 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

19 years, 3 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-160) New query parser does not allow bitwise operations

by Chris Wood (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-160?page=co... ] Chris Wood commented on HHH-160: -------------------------------- BTW: the registerFunction line for bit_and and bit_or can take advantage of org.hibernate.dialect.function.VarArgsSQLFunction. Using this you can get rid of the inner class, and just do the following in the constructor: registerFunction("bit_not", new SQLFunctionTemplate(Hibernate.INTEGER, "~?1")); registerFunction("bit_and", new VarArgsSQLFunction(Hibernate.INTEGER, "(", "&", ")")); registerFunction("bit_or", new VarArgsSQLFunction(Hibernate.INTEGER, "(", "|", ")")); Note the additional surrounding brackets, this ensures the function-like behaviour rather than using the DB's operator precidence. > New query parser does not allow bitwise operations > -------------------------------------------------- > > Key: HHH-160 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-160 > Project: Hibernate3 > Type: Improvement > Components: core > Versions: 3.0 rc 1 > Environment: Hibernate 3.0 rc1, MySQL > Reporter: Markus Jessenitschnig > Priority: Minor > > > The new query parser does not allow bitwise operations like bitwise-and and bitwise-or. > Example: > SELECT FIRSTNAME, SURNAME FROM EMPLOYEE WHERE (STATUS & 1) > 0 > The Exception is: > org.hibernate.QueryException: unexpected char: '&' -- 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

19 years, 3 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1714) Session.get() behavior

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1714?page=c... ] Steve Ebersole commented on HHH-1714: ------------------------------------- because at the time i was not anticipating another cr release. Unfortunately I need to do a cr5. > Session.get() behavior > ---------------------- > > Key: HHH-1714 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1714 > Project: Hibernate3 > Type: Bug > Components: core > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Fix For: 3.2.1 > > > The behavior of Session.get() should be as follows: > 1) if the entity to get is already associated with the session: > a) as a proxy, return the proxy making sure it gets initialized (potentially resulting in a ONFE) > b) as a naked entity, return that entity > 2) if the entity to get is not already associated with the session, attempt to load it either returning null if not found or the "naked" loaded entity > Currently (1.a) is messed up in that the proxy is returned but not forced to initialize -- 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

19 years, 3 months

1
0
0 / 0

[Hibernate-JIRA] Reopened: (HHH-1661) merge of a deleted object results in a insert?

by Emmanuel Bernard (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1661?page=all ] Emmanuel Bernard reopened HHH-1661: ----------------------------------- My bad, If we know for use that it's a detached instance we should throw an exception. *know for sure* still has to be defined though > merge of a deleted object results in a insert? > ---------------------------------------------- > > Key: HHH-1661 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1661 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.1.3 > Environment: Hibernate 3.1.3, SQL Server > Reporter: Tu-Thach > > > A persistent object is loaded from a session and deleted, then close the session. Using that same object in another session and call merge results in the object being inserted into the database. Here's the sample code: > Session session = factory.getCurrentSession(); > session.beginTransaction(); > MyClass obj = (MyClass)session.load(MyClass.class, new Integer(10)); > session.delete(obj); > session.getTransaction().commit(); > session = factory.getCurrentSession(); > session.beginTransaction(); > session.merge(obj); > session.getTransaction().commit(); > Since the object is already deleted, merge could not find it and thus proceeds with a INSERT. Shouldn't it throw an exception instead? -- 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

19 years, 3 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-160) New query parser does not allow bitwise operations

by Chris Wood (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-160?page=co... ] Chris Wood commented on HHH-160: -------------------------------- To me it makes sense to include the bitwise operators as part of the syntax, rather than as functions, because then the correct operator precidence is available. > New query parser does not allow bitwise operations > -------------------------------------------------- > > Key: HHH-160 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-160 > Project: Hibernate3 > Type: Improvement > Components: core > Versions: 3.0 rc 1 > Environment: Hibernate 3.0 rc1, MySQL > Reporter: Markus Jessenitschnig > Priority: Minor > > > The new query parser does not allow bitwise operations like bitwise-and and bitwise-or. > Example: > SELECT FIRSTNAME, SURNAME FROM EMPLOYEE WHERE (STATUS & 1) > 0 > The Exception is: > org.hibernate.QueryException: unexpected char: '&' -- 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

19 years, 3 months

1
0
0 / 0

[Hibernate-JIRA] Created: (EJB-234) Inefficiency during the flush operation

by Emmanuel Bernard (JIRA)

Inefficiency during the flush operation --------------------------------------- Key: EJB-234 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-234 Project: Hibernate Entity Manager Type: Improvement Components: EntityManager Reporter: Emmanuel Bernard Assigned to: Emmanuel Bernard Fix For: 3.2.0.cr3 esp with big persistence contexts and lots of cascade PERSIST -- 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

19 years, 3 months

1
1
0 / 0

[Hibernate-JIRA] Updated: (EJB-152) Check JBossEJB3 entityexception tests for missing Exceptions

by Emmanuel Bernard (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/EJB-152?page=all ] Emmanuel Bernard updated EJB-152: --------------------------------- Fix Version: (was: 3.2.0.cr3) > Check JBossEJB3 entityexception tests for missing Exceptions > ------------------------------------------------------------ > > Key: EJB-152 > URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-152 > Project: Hibernate Entity Manager > Type: Bug > Components: EntityManager > Versions: 3.1beta7 > Reporter: Emmanuel Bernard > Assignee: 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

19 years, 3 months

1
0
0 / 0

[Hibernate-JIRA] Created: (EJB-221) TransientObjectException with FetchType.LAZY on @ManyToOne and field access on target entity

by Christian Bauer (JIRA)

TransientObjectException with FetchType.LAZY on @ManyToOne and field access on target entity -------------------------------------------------------------------------------------------- Key: EJB-221 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-221 Project: Hibernate Entity Manager Type: Bug Components: EntityManager Reporter: Christian Bauer Priority: Blocker Attachments: fetchtest.jar Latest SVN of everything: em = factory.createEntityManager(); em.getTransaction().begin(); Soldier2 soldier = em.find(Soldier2.class, mickey.getId()); System.out.println("### TRYING TO ACCESS PROXY ID..."); // This triggers a SELECT, it shouldn't System.out.println("### PROXY ID : " + soldier.getTroop().getId()); // This throws a TransientObjectException em.flush(); The @ManyToOne troop in Soldier2.java has only FetchType.LAZY, the CascadeType.PERSIST is removed. I expect the problem to be in CascadingAction PERSIST_ON_FLUSH.noCascade() somewhere, apparently the proxy has no Id anymore during flush-time and is considered transient (how can a proxy be transient?). The problems appear as soon as I move the annotations from getters to fields in Troop2.java. The attached tests are for HEM. -- 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

19 years, 3 months

2
9
0 / 0

[Hibernate-JIRA] Created: (ANN-447) Introduce @WhereJoinTable to complete @Where on association involving a join table

by Emmanuel Bernard (JIRA)

Introduce @WhereJoinTable to complete @Where on association involving a join table ---------------------------------------------------------------------------------- Key: ANN-447 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-447 Project: Hibernate Annotations Type: New Feature Components: binder Reporter: Emmanuel Bernard Assigned to: Emmanuel Bernard Priority: Minor Fix For: 3.2.0 This break the use of @Where on @ManyToMany and @OneToMany @JoinTable -- 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

19 years, 3 months

1
2
0 / 0

[Hibernate-JIRA] Updated: (ANN-336) @OrderBy and @CollectionOfElements support (Sylvain Vieujot)

by Emmanuel Bernard (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-336?page=all ] Emmanuel Bernard updated ANN-336: --------------------------------- Fix Version: 3.2.1 (was: 3.2.0.cr3) > @OrderBy and @CollectionOfElements support (Sylvain Vieujot) > ------------------------------------------------------------ > > Key: ANN-336 > URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-336 > Project: Hibernate Annotations > Type: Improvement > Components: binder > Reporter: Emmanuel Bernard > Assignee: Emmanuel Bernard > Fix For: 3.2.1 > > > No unit test though -- 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

19 years, 3 months

1
0
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 October 2006