March 2009 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-3367) Add support to OpenEdge RDMS (Progress 10) in DialectFactory

by Glaucio Scheibel (JIRA)

Add support to OpenEdge RDMS (Progress 10) in DialectFactory ------------------------------------------------------------ Key: HHH-3367 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3367 Project: Hibernate3 Issue Type: Patch Components: core Affects Versions: 3.2.6 Reporter: Glaucio Scheibel Attachments: DialectFactory.java, DialectFactory.patch This patch adds OpenEdge (formely Progress Database) support to DialectFactory class. -- 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, 3 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2654) Ingres dialect patch to support bit_length

by Chris Bredesen (JIRA)

Ingres dialect patch to support bit_length ------------------------------------------ Key: HHH-2654 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2654 Project: Hibernate3 Issue Type: Patch Components: core Reporter: Chris Bredesen Assignee: Steve Ebersole Priority: Minor Attachments: IngresDialect.diff This patch from Daniel fixes the Ingres dialect to support bit_length. -- 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, 3 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3733) Introduce an annotation to disable ad-hoc null semantic of Hibernate components

by Vladimir Kovalyuk (JIRA)

Introduce an annotation to disable ad-hoc null semantic of Hibernate components ------------------------------------------------------------------------------- Key: HHH-3733 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3733 Project: Hibernate Core Issue Type: Improvement Components: core Reporter: Vladimir Kovalyuk see http://forums.hibernate.org/viewtopic.php?t=993972 For the model @Entity public class Person { private Address name = new Address(); ... @Embedded Address getAddress() {} } @Embeddable public class Address { public String getCity() {} public String getStreet() {} } the following xhtml excerpt causes NPE constantly when editing a person which address properties hasn't been filled in yet <h:inputText value="#{person.address.city}" /> I suggest introducing an annotation @Static which could be applied to Address class and lead to disabling null ad-hoc semantic on its instances. For some environments such as user interface this may be considered as the default behavior. I suggest introducing an Hibernate configuration parameter which would switch off the semantic. I would propose to consider embeddable classes as static mixins from OO design, not as just limited entities without identity. This point of view explains that embedded instance is a part of entity so it's lifecycle is the same as the entity's lifecycle. Thus constant presence of embeddable instance (property is never null) is the default behavior. Thus configuration parameter is "must have", not the thing which is "nice to have". >From the other hand null ad-hoc semantic is like dynamic mixins. So it would be nice to have a @Dynamic annotation to force this semantic for some 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

11 years, 3 months

4
6
0 / 0

[Hibernate-JIRA] Created: (HHH-2308) Adjusting the Outer Join Predicate using Criteria Query

by Ben Grant (JIRA)

Adjusting the Outer Join Predicate using Criteria Query ------------------------------------------------------- Key: HHH-2308 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2308 Project: Hibernate3 Type: New Feature Components: query-criteria Versions: 3.2.1 Environment: Linux Using MS SQLServer Reporter: Ben Grant I have two tables Table A ||Col_1||Col_2|| |London| UK | |Liverpool| UK | | New York | USA | Table B ||Col_1||Col_2|| Col_3|| | UK | Europe | 0 | USA | Americas | 1 Using the Criteria class, Restriction Class and FetchMode, Hibernate manages to create a query that looks like this select distinct top 2000 this_.Col_1 as y0_, TableB3_.Col2 as y1_ from TableA this_ left outer join TableB TableB3_ on this_.Col_2= TableB3_.Col_1 where TableB3_.Col_3=1 When really i need the query to be like this select distinct top 2000 this_.Col_1 as y0_, TableB3_.Col2 as y1_ from TableA this_ left outer join TableB TableB3_ on this_.Col_2= TableB3_.Col_1 AND TableB3_.Col_3=1 currently their isn't any know way for hibernate to adjust or apply filters within the join clause. -- 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, 3 months

12
27
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, 3 months

4
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, 3 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2058) puhs SessionImplementor.getInterceptor up into Session

by Max Rydahl Andersen (JIRA)

puhs SessionImplementor.getInterceptor up into Session ------------------------------------------------------ Key: HHH-2058 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2058 Project: Hibernate3 Type: Improvement Components: core Reporter: Max Rydahl Andersen Being able to get the actual interceptor used for a certain Session is beneficial. any reason why it is not exposed on Session ? -- 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, 3 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3129) Null Role in PersitentCollection during a onCollectionRecreate() in an Interceptor

by Jose CHILLAN (JIRA)

Null Role in PersitentCollection during a onCollectionRecreate() in an Interceptor ---------------------------------------------------------------------------------- Key: HHH-3129 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3129 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.6 Environment: Any Reporter: Jose CHILLAN When the "onCollectionRecreate" is invoked on an Interceptor, the getRole() method returns null. After investigation, the problem is located in the class CollectionEntry in one of its constructors and is easily solved using the patch : public CollectionEntry(CollectionPersister persister, PersistentCollection collection) { // new collections that get found + wrapped // during flush shouldn't be ignored ignore = false; collection.clearDirty(); //a newly wrapped collection is NOT dirty (or we get unnecessary version updates) snapshot = persister.isMutable() ? collection.getSnapshot(persister) : null; // -- ADDED LINE HERE -- role = persister.getRole(); collection.setSnapshot(loadedKey, role, snapshot); } Thanks -- 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, 3 months

6
8
0 / 0

[Hibernate-JIRA] Created: (HHH-2847) THIS_"."NAME": invalid identifier when using createCriteria with addOrder

by Ashish Tiwari (JIRA)

THIS_"."NAME": invalid identifier when using createCriteria with addOrder ------------------------------------------------------------------------- Key: HHH-2847 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2847 Project: Hibernate3 Issue Type: Bug Components: query-criteria Affects Versions: 3.0.5 Environment: Oracle - 10.2.0 Reporter: Ashish Tiwari We are using hibernate 3.0.5 and once a while I see following error getting generated due to incorrect SQL generated by hibernate: Hibernate: select systembean0_.SYSTEMID as SYSTEMID12_0_, systembean0_.Version as Version12_0_, systembean0_.NAME as NAME12_0_, systembean0_.TYPE as TYPE12_0_, systembean0_.DESCRIPTION as DESCRIPT5_12_0_ from SDSYSTEM systembean0_ order by this_.NAME asc - SQL Error: 904, SQLState: 42000 - ORA-00904: "THIS_"."NAME": invalid identifier This normally works but occasionally we run into the issue mentioned above. I do not see alias "this_" in the sql query and I think that causes the error to happen. Issue is caused by alias not used consistently. In normal case the generated SQL looks like following: Hibernate: select this_.SYSTEMID as SYSTEMID7_0_, this_.Version as Version7_0_, this_.NAME as NAME7_0_, this_.TYPE as TYPE7_0_, this_.DESCRIPTION as DESCRIPT5_7_0_ from SDSYSTEM this_ order by this_.NAME asc I am not sure what causes this problem. Has anyone else see similar problem earlier? I appreciate any help with this. Below is other information: Hibernate version: 3.0.5 Mapping documents: <?xml version="1.0"?> <!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD 3.0//EN" "http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd"> <hibernate-mapping> <class name="com.avaya.coreservice.admin.toolkit.common.system.SystemBean" table="SDSYSTEM"> <id name="uniqueId" type="java.lang.String"> <column name="SYSTEMID" length="50" not-null="true"/> <generator class="uuid"/> </id> <version name="version" column="Version" /> <property name="name" type="java.lang.String"> <column name="NAME" length="512" not-null="true"/> </property> <property name="type" type="java.lang.String"> <column name="TYPE" length="50" not-null="false"/> </property> <property name="description" type="java.lang.String"> <column name="DESCRIPTION" length="1024" not-null="false"/> </property> <set name="resourceBeanSet"> <key> <column name="SYSTEMID" length="50" not-null="false"/> </key> <one-to-many class="com.avaya.coreservice.admin.toolkit.common.resource.ResourceBean"/> </set> <set name="siteBeanSet" order-by="name asc"> <key> <column name="SYSTEMID" length="50" not-null="false"/> </key> <one-to-many class="com.avaya.coreservice.admin.toolkit.common.site.SiteBean"/> </set> </class> </hibernate-mapping> Code between sessionFactory.openSession() and session.close(): HibernateUtil.getSession().createCriteria(SystemBean.class) .addOrder(Order.asc("name")).list(); Full stack trace of any exception that occurs: N/A Name and version of the database you are using: Oracle - 10.2.0 The generated SQL (show_sql=true): select systembean0_.SYSTEMID as SYSTEMID12_0_, systembean0_.Version as Version12_0_, systembean0_.NAME as NAME12_0_, systembean0_.TYPE as TYPE12_0_, systembean0_.DESCRIPTION as DESCRIPT5_12_0_ from SDSYSTEM systembean0_ order by this_.NAME asc I appreciate any help with this. Thanks, -- 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

7
10
0 / 0

[Hibernate-JIRA] Created: (HHH-3345) "select new" + "join fetch" = "owner of the fetched association was not present in the select list"

by Anthony Ogier (JIRA)

"select new" + "join fetch" = "owner of the fetched association was not present in the select list" --------------------------------------------------------------------------------------------------- Key: HHH-3345 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3345 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.4.sp1 Reporter: Anthony Ogier I want to create a List<B>, each B containing an entity with "A" type, and I also want for each A to force fetching of its "C" property. public class B { private A a; public B(A a) { this.a = a; } } @Entity public class A { @ManyToOne @JoinColumn private C c; // +get/setter ... } @Entity public class C { @Column private String d; // +get/setter ... // +@OneToMany } Here is the HQL : select new B(a) from A a left join fetch a.c I have that message : org.hibernate.QueryException: query specified join fetching, but the owner of the fetched association was not present in the select list When invoking only "from A a left join fetch a.c", all is good and I have ma List<A> with its "C" properties fetched. I think there is a little bug here ... or did I forget something ? -- 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
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues March 2009