March 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Closed: (HBX-180) NPE with hashcode method

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-180?page=co... ] Steve Ebersole closed HBX-180. ------------------------------ Closing stale resolved issues > NPE with hashcode method > ------------------------ > > Key: HBX-180 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-180 > Project: Hibernate Tools > Issue Type: Bug > Components: hbm2java > Reporter: Henri Dupre > > The current hashCode() method generates code like "castOther.getxxxx().hashCode()". When the field xxxx is null an NPE will be raised. I suggest to go back to Apache HashCodeBuilder, I can submit a patch for that. -- 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, 1 month

1
0
0 / 0

[Hibernate-JIRA] Closed: (HHH-1362) Using Transactions while loading an object results in unwanted Update query.

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1362?page=c... ] Steve Ebersole closed HHH-1362. ------------------------------- Closing stale resolved issues > Using Transactions while loading an object results in unwanted Update query. > ------------------------------------------------------------------------------ > > Key: HHH-1362 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1362 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.0.5 > Environment: Hibernate 3.0.5, MySQL 5.0 database. > Reporter: Nico De Groote > Priority: Blocker > Attachments: HibernateTest.rar > > > Using Transactions while loading an object results in unwanted Update query. > Attached is the Eclipse project. Add the Hibernate 3.0.5 jars to run the test case. Running with transactions adds an extra update Query when this is not expected. -- 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, 1 month

1
0
0 / 0

[Hibernate-JIRA] Closed: (HHH-1531) NPE with many-to-many and property-ref

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1531?page=c... ] Steve Ebersole closed HHH-1531. ------------------------------- Closing stale resolved issues > NPE with many-to-many and property-ref > -------------------------------------- > > Key: HHH-1531 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1531 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.1.2 > Reporter: Emmanuel Bernard > Assignee: Steve Ebersole > Fix For: 3.2.0.alpha2, 3.1.3 > > -- 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, 1 month

1
0
0 / 0

[Hibernate-JIRA] Closed: (HHH-920) CLONE -Session.isDirty() flushes data

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-920?page=co... ] Steve Ebersole closed HHH-920. ------------------------------ Closing stale resolved issues > CLONE -Session.isDirty() flushes data > ------------------------------------- > > Key: HHH-920 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-920 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.0 final > Reporter: Lenny Marks > > When calling Session.isDirty() (Hibernate 3.0.0, non-classic) it looks like DefaultDirtyCheckEventListener performs actual flush. I'm not sure is this an intended behaviour. In fact, javadoc for Session.isDirty() says that it should only check are there any pending changed and would database update happen on Session.flush(). Please advise. -- 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, 1 month

1
0
0 / 0

[Hibernate-JIRA] Closed: (HHH-985) Sessions created via SessionFactory.openSession(Connection) have invalid timestamp

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-985?page=co... ] Steve Ebersole closed HHH-985. ------------------------------ Closing stale resolved issues > Sessions created via SessionFactory.openSession(Connection) have invalid timestamp > ---------------------------------------------------------------------------------- > > Key: HHH-985 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-985 > Project: Hibernate Core > Issue Type: Bug > Affects Versions: 3.0.5 > Environment: 3.0.5 > MySql > Reporter: Patrick Casey > > Create Two sessions: > Session s = HibHelper.getSessionFactory().openSession(); > Session temp = HibHelper.getSessionFactory().openSession(s.connection()); > temp is a child of s in that it's using the same connection. > Session s gets a proper timestamp : 4619002056560640 > Session temp gets an arbitrarily negative one: -9223372036854775808 > This means that anything you do via temp will fail when it tries to use the secondary cache because every entity in the cache will fail "freshness" relative to temp's timestamp. > I'd think temp should either get its own timestamp based on its creation or inherit it's parten't timestamp. The large negative default value though means I can't use a derived session and the L2 cache :(. -- 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, 1 month

1
0
0 / 0

[Hibernate-JIRA] Closed: (HHH-965) On deleting parent object , child references should be set to null , not deleted, this is a scenario i face but am unable to implement it in hiberante

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-965?page=co... ] Steve Ebersole closed HHH-965. ------------------------------ Closing stale resolved issues > On deleting parent object ,child references should be set to null ,not deleted,this is a scenario i face but am unable to implement it in hiberante > --------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: HHH-965 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-965 > Project: Hibernate Core > Issue Type: Improvement > Components: core > Reporter: nitin sareen > Assignee: Steve Ebersole > -- 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, 1 month

1
0
0 / 0

[Hibernate-JIRA] Closed: (HHH-687) Exception QuerySyntaxError not really serializable

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-687?page=co... ] Steve Ebersole closed HHH-687. ------------------------------ Closing stale resolved issues > Exception QuerySyntaxError not really serializable > -------------------------------------------------- > > Key: HHH-687 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-687 > Project: Hibernate Core > Issue Type: Bug > Affects Versions: 3.0.5 > Environment: Hibernate 3.0.5 > Reporter: Roberto Italia > Assignee: Steve Ebersole > Priority: Minor > Fix For: 3.2.0.alpha1 > > > I have a QuerySyntaxError Exception which has a MismatchedTokenException (from antlr) as cause. The field token of the MismatchedTokenException points to a HqlToken, which descends from antlr.CommonToken. The latter is not serializable, so also HqlToken is not. As a result, the QuerySyntaxError cannot be serialized. > I'm not sure, whether you (by making a HqlToken serializable some how) or antlr (by making CommonToken or Token serializable) should fix 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, 1 month

1
0
0 / 0

[Hibernate-JIRA] Closed: (HHH-1084) incorrect method name "sql" in Restrictions example, should be "sqlRestriction"

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1084?page=c... ] Steve Ebersole closed HHH-1084. ------------------------------- Closing stale resolved issues > incorrect method name "sql" in Restrictions example, should be "sqlRestriction" > ------------------------------------------------------------------------------- > > Key: HHH-1084 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1084 > Project: Hibernate Core > Issue Type: Bug > Components: documentation > Affects Versions: 3.0.5 > Reporter: Walter Gillett > Fix For: 3.1 rc3 > > > Section 16.2 of the documentation (http://www.hibernate.org/hib_docs/v3/reference/en/html/querycriteria.html) has this example: > List cats = sess.createCriteria(Cat.class) > .add( Restrictions.sql("lower({alias}.name) like lower(?)", "Fritz%", Hibernate.STRING) ) > .list(); > which doesn't compile, because instead of "Restrictions.sql" above, the correct method call is "Restrictions.sqlRestriction". -- 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, 1 month

1
0
0 / 0

[Hibernate-JIRA] Closed: (HHH-1203) lazy="extra" and cascade="all" broken

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1203?page=c... ] Steve Ebersole closed HHH-1203. ------------------------------- Closing stale resolved issues > lazy="extra" and cascade="all" broken > ------------------------------------- > > Key: HHH-1203 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1203 > Project: Hibernate Core > Issue Type: Bug > Affects Versions: 3.1 rc3 > Reporter: Mathias Bogaert > -- 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, 1 month

1
0
0 / 0

[Hibernate-JIRA] Closed: (HHH-1412) Collection fetches and firstResult/maxRows

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1412?page=c... ] Steve Ebersole closed HHH-1412. ------------------------------- Closing stale resolved issues > Collection fetches and firstResult/maxRows > ------------------------------------------ > > Key: HHH-1412 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1412 > Project: Hibernate Core > Issue Type: Improvement > Components: query-criteria, query-hql > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Priority: Blocker > Fix For: 3.2.0.alpha1 > > > Collection fetches and firstResult/maxRows currently do not return logical results, since the firstResult/maxRows are applied at the database level. We need to recognize this scenario and perform the firstResult/maxRows in memory (plus generously warn the user). -- 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, 1 month

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 March 2011