January 2013 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] (HHH-7908) Logging level checking.

by Jeremy Whiting (JIRA)

11 years, 4 months

1
0
0 / 0

[Hibernate-JIRA] (HSEARCH-1249) Serialization protocol being logged without enough context

by Sanne Grinovero (JIRA)

11 years, 4 months

1
1
0 / 0

[Hibernate-JIRA] (HHH-759) problem for mixxing setmaxresults and setlockmode

by Brett Meyer (JIRA)

11 years, 4 months

1
0
0 / 0

[Hibernate-JIRA] (HHH-1729) Oracle9Dialect LockMode.UPGRADE conflicts with setMaxResults

by Brett Meyer (JIRA)

11 years, 4 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-2844) Limit and 'For Update' do not work on Oracle

by Michael Kopp (JIRA)

Limit and 'For Update' do not work on Oracle -------------------------------------------- Key: HHH-2844 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2844 Project: Hibernate3 Issue Type: Bug Components: query-sql Affects Versions: 3.2.2 Reporter: Michael Kopp Limits on oracle lead too: select * from (select x.y as xy_1 from table x) where rownum <= 5 when doing a for update that leads too select * from (select x.y as xy_1 from table x) where rownum <= 5 for update of x.y The problem is that the x.y is invalid and not found within the temporary view and leads to an oracle error. what would be valid is the name of the view column xy_1, meaning select * from (select x.y as xy_1 from table x) where rownum <= 5 for update of xy_1 Actually this should be valid in all cases when doing a alias for update lock. My Solution thus was to override the following in my own Oracle Dialect public String applyLocksToSql(final String sql, final Map aliasedLockModes, final Map keyColumnNames) { final String s = new ForUpdateFragment(this, aliasedLockModes, keyColumnNames) { @Override public ForUpdateFragment addTableAlias(final String alias) { // search for alias in sql final int i = sql.indexOf(alias); // check if the found string is followed by an ' as ' and thus has a column alias if (i != -1 && sql.length() > (i + alias.length() + 4) && sql.substring(i + alias.length(), i + alias.length() + 4).equals( " as ")) { // use the column alias return super.addTableAlias(sql.substring(i + alias.length() + 4, sql.indexOf(',',i + alias.length() + 4))); } return super.addTableAlias(alias); } }.toFragmentString(); return sql + s; -- 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

11 years, 4 months

4
6
0 / 0

[Hibernate-JIRA] (HHH-7907) Bind filter

by Strong Liu (JIRA)

11 years, 4 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-6982) ForeignKeys$Nullifier thinks a detached proxy is attached if another object with the same identifier is associated with the persistence context

by Martin Keßler (JIRA)

ForeignKeys$Nullifier thinks a detached proxy is attached if another object with the same identifier is associated with the persistence context ----------------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-6982 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6982 Project: Hibernate ORM Issue Type: Bug Components: core Affects Versions: 3.5.1 Environment: Hibernate 3.5.1, IBM DB2 9.7 on Win7 and AIX 6.1 Reporter: Martin Keßler 1. Create a transient object A which has a many-to-one property of type B 2. Create a proxy of type B with identifier x via Session.load(B.class, x) 3. Set the B-property in A to B 4. Flush and clear the persistence context; the B-proxy is now detached 5. Read the B-entity with identifier x through a query; a new object with id=x is now in the persistence context 6. Persist the A-entity (Session.save) 7. ForeignKeys$Nullifier.isNullifiable is called with the B-proxy, and checks if the persistence context contains an entity with the id x 8. The persistence context actually contains such an entity, but it's not the proxy 9. Hibernate tries to initialize the detached proxy, leading to a LazyInitializationException -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

3
6
0 / 0

[Hibernate-JIRA] Created: (HBX-939) Composite IDs and many-to-many relationships

by Markus Kramer (JIRA)

Composite IDs and many-to-many relationships -------------------------------------------- Key: HBX-939 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-939 Project: Hibernate Tools Issue Type: Bug Affects Versions: 3.2beta9 Environment: Hibrnate 3.2.1, Postgresql 8.1.8 Reporter: Markus Kramer Attachments: B.hbm.xml, testdb.sql The detection of many-to-many relationships doesn't work correctly if the primary key of one of the involved tables consists of more than one field. An example: One of two tables (table 'A') of a many-to-many relationship has a primary key consisting of two attributes (id1 and id2). The generated B.hbm.xml for the table 'B' contains this: <set name="as" inverse="true" table="a_b"> <key> <column name="b_id" not-null="true" /> </key> <many-to-many entity-name="test.A"> <column name="a_id1" not-null="true" /> </many-to-many> </set> But there should be another entry for the referenced primary key: <column name="a_id2" not-null="true" /> The SQL code for the used tables and the complete B.hbm.xml are attached. -- 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

11 years, 4 months

2
1
0 / 0

[Hibernate-JIRA] (HHH-7906) auto import unqualified entity name

by Strong Liu (JIRA)

11 years, 4 months

1
1
0 / 0

[Hibernate-JIRA] (HHH-7905) natural id column should not be force not null

by Strong Liu (JIRA)

11 years, 4 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues January 2013