February 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (ANN-527) reference a target entity (in a collection) by entity name

by Armin Haaf (JIRA)

reference a target entity (in a collection) by entity name ---------------------------------------------------------- Key: ANN-527 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-527 Project: Hibernate Annotations Type: New Feature Components: binder Reporter: Armin Haaf It is only possible to reference a targetEntity by class. @ManyToMany(targetEntity = TestImpl.class) List<Test> myList; This makes it impossible to exchange TestImpl.class implemention by another implemention by the mappings definition. It would be helpful to reference a targetEntity by name. @ManyToMany(targetEntityName = "Test") This would help a lot to implement moduls and frameworks. Another way to support this would be to search for a implementation of the collection elements (which are typically Interfaces) in the mapped entities -- 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

17 years, 5 months

5
10
0 / 0

[Hibernate-JIRA] Created: (HHH-2546) fetch="select" doesn't work when there are no mapped columns in joined except <key

by Derar Bakr (JIRA)

fetch="select" doesn't work when there are no mapped columns in joined except <key ---------------------------------------------------------------------------------- Key: HHH-2546 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2546 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.3 Environment: Windows XP Pro Reporter: Derar Bakr java.lang.StringIndexOutOfBoundsException: String index out of range: -2 at java.lang.String.substring(String.java:1768) at java.lang.String.substring(String.java:1735) at org.hibernate.persister.entity.AbstractEntityPersister.renderSelect(AbstractEntityPersister.java:2899) at org.hibernate.persister.entity.SingleTableEntityPersister.generateSequentialSelect(SingleTableEntityPersister.java:647) at org.hibernate.persister.entity.SingleTableEntityPersister.postInstantiate(SingleTableEntityPersister.java:696) .... Everything is very simple. There is stupid code in SelectFragment class, method toFragmentString, line 94. String that is being created there, contains list of fields, like a "f1, f2, f3, ..., fn". ", " is being added in every iteration, without check for it is first iteration. And in class AbstractEntityPersister., method renderSelect, line 2899, where that method is called, this first ", " is deleted using substring(2). So no check for empty string. I suggest to add check :))) I just create dynamic mappings programmatically, so create empty join subclass mappings - and in created table there are no fields by default except foreing key. -- 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

17 years, 5 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HBX-860) cfg.xml generation should have option if it should generate <mappings>

by Max Rydahl Andersen (JIRA)

cfg.xml generation should have option if it should generate <mappings> ---------------------------------------------------------------------- Key: HBX-860 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-860 Project: Hibernate Tools Type: Improvement Reporter: Max Rydahl Andersen Fix For: 3.2beta10 adding <mapping> for class when JPA does not make sense. -- 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

17 years, 5 months

2
7
0 / 0

[Hibernate-JIRA] Created: (HBX-888) Option for enable/disable schemaexport and databasemetadata introspection

by Max Rydahl Andersen (JIRA)

Option for enable/disable schemaexport and databasemetadata introspection ------------------------------------------------------------------------- Key: HBX-888 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-888 Project: Hibernate Tools Type: New Feature Components: consoleconfiguration Versions: 3.2beta10 Reporter: Max Rydahl Andersen Fix For: 3.2beta10 schemaexport might be relevant/wanted for some users to automatically run... databasemetadata introspection is probably only relevant for users that does not specify a dialect. -- 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

17 years, 5 months

1
6
0 / 0

[Hibernate-JIRA] Created: (HBX-843) handle types with scale/precision explicit instead of relying on defaults

by Max Rydahl Andersen (JIRA)

handle types with scale/precision explicit instead of relying on defaults ------------------------------------------------------------------------- Key: HBX-843 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-843 Project: Hibernate Tools Type: Improvement Versions: 3.2beta8 Reporter: Max Rydahl Andersen Fix For: 3.2beta9 hibernate defaults is different than jpa thus cannot use them to indicate if scale-precision is required. http://jira.jboss.com/jira/browse/JBSEAM-596 -- 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

17 years, 5 months

1
7
0 / 0

[Hibernate-JIRA] Created: (HBX-777) [hbmlint] bidirectional check

by Max Rydahl Andersen (JIRA)

[hbmlint] bidirectional check ----------------------------- Key: HBX-777 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-777 Project: Hibernate Tools Type: New Feature Reporter: Max Rydahl Andersen Fix For: 3.2beta9 nverse-true-on-bidirectional ie 2 association mapped to the same table same FK columns should raise a warning if one of them does not have inverse="true or is not insert=false update=false -- 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

17 years, 5 months

1
8
0 / 0

[Hibernate-JIRA] Created: (HHH-2258) Bad SQL Grammer: Implicit join when using r.fooClass.attributes[?]=?

by Darryl Miles (JIRA)

Bad SQL Grammer: Implicit join when using r.fooClass.attributes[?]=? -------------------------------------------------------------------- Key: HHH-2258 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2258 Project: Hibernate3 Type: Bug Components: core Versions: 3.1.3 Environment: MySQL server this has been tested with. Reporter: Darryl Miles Priority: Critical Attachments: test_joinedmapfilter.zip Please find this test case atteched to demonstrate the bug, maybe you can add to the hibernate distribution for future testing and piece of mind for me. The error: Testsuite: org.hibernate.test.joinedmapfilter.JoinedMapFilterTest Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0.498 sec Testcase: testJoinedMapFilter took 0.495 sec Caused an ERROR could not execute query org.hibernate.exception.SQLGrammarException: could not execute query at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:67) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) at org.hibernate.loader.Loader.doList(Loader.java:2147) at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2028) at org.hibernate.loader.Loader.list(Loader.java:2023) at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:393) at org.hibernate.hql.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:338) at org.hibernate.engine.query.HQLQueryPlan.performList(HQLQueryPlan.java:172) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1121) at org.hibernate.impl.QueryImpl.list(QueryImpl.java:79) at org.hibernate.test.joinedmapfilter.JoinedMapFilterTest.testJoinedMapFilter(JoinedMapFilterTest.java:116) at org.hibernate.test.TestCase.runTest(TestCase.java:250) at org.hibernate.test.TestCase.runBare(TestCase.java:316) Caused by: java.sql.SQLException: Unknown table 'productdet1_' in where clause at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2928) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1571) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1666) at com.mysql.jdbc.Connection.execSQL(Connection.java:2994) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:936) at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:1030) at org.hibernate.jdbc.AbstractBatcher.getResultSet(AbstractBatcher.java:186) at org.hibernate.loader.Loader.getResultSet(Loader.java:1668) at org.hibernate.loader.Loader.doQuery(Loader.java:662) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:224) at org.hibernate.loader.Loader.doList(Loader.java:2144) ... 25 more SELECT r FROM com.company.Toplevel AS r WHERE r.toplevel=? AND rec.productDetail.attributes[?]=? Also my recent post: http://forum.hibernate.org/viewtopic.php?t=966374&start=0&postdays=0&post... This testcase has been tested with 3.1.3 and 3.2.0-ga. 2nd problem: There is also another situation in the testcase which I found through serendipity which causes a NPE inside hibernate because I misspelled "r" as "rec". Check out the commented out section and swap over the createQuery() lines to demonstrate that NPE. -- 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

17 years, 5 months

1
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2922) DML - update does not support component property in the set-clause

by Roman Pichlík (JIRA)

DML - update does not support component property in the set-clause ------------------------------------------------------------------ Key: HHH-2922 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2922 Project: Hibernate3 Issue Type: Bug Components: query-hql Affects Versions: 3.2.4.sp1 Reporter: Roman Pichlík Using of component property in in the set-clause of HQL update query leads to: org.springframework.orm.hibernate3.HibernateQueryException: unexpected AST node: AND near line 1, column 43 [update x a set a.component = : where a._revision = :revision and a._uuid = :uuid]; nested exception is org.hibernate.hql.ast.QuerySyntaxException: unexpected AST node: AND near line 1, column 43 [update artifactBase a set a._artifactData = :artifactData where a._revision = :revision and a._uuid = :uuid] -- 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

17 years, 5 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3062) Incompleted Collection Returned from Joined Fetch

by Tony Lin (JIRA)

Incompleted Collection Returned from Joined Fetch ------------------------------------------------- Key: HHH-3062 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3062 Project: Hibernate3 Issue Type: Bug Components: query-hql Affects Versions: 3.2.5 Environment: Windows XP SP2, JDK 1.6_03, MySQL 5, Toncat 5.5.25 Reporter: Tony Lin Attachments: subsets.sql Executing the following query: select subset from com.alphait.domain.snomed.object.SubsetImpl as subset join fetch subset.members as members left join fetch members.parent The members returned after the first subset are not complete, all but the first member are missing. The classes are attached in HHH-3056. The test data is in the attached file, please load it to a mysql database. After investigation, the problem seems be in Loader.java's sequentialLoad method: try { do { Object loaded = getRowFromResultSet( resultSet, session, queryParameters, getLockModes( queryParameters.getLockModes() ), null, hydratedObjects, loadedKeys, returnProxies ); if ( result == null ) { result = loaded; } } while ( keyToRead.equals( loadedKeys[0] ) && resultSet.next() ); } catch ( SQLException sqle ) { throw JDBCExceptionHelper.convert( factory.getSQLExceptionConverter(), sqle, "could not perform sequential read of results (forward)", getSQLString() ); } initializeEntitiesAndCollections( hydratedObjects, resultSet, session, queryParameters.isReadOnly() ); session.getPersistenceContext().initializeNonLazyCollections(); return result; It will fetch the next subset also, but only the first member, and the member's parent. These three are hydrated, and resolved when initializeEntitiesAndCollections is called. This makes the members collection to be freezed, and no member can be added. We put the following: key = getKeyFromResultSet( 0, persisters[0], null, resultSet, session ); if (!keyToRead.equals(key)) { // we are done, no moving forward break; } before calling getRowFromResultSet(). This temporarily solved the problem for us. Also this kind of query cannot have order by containing only the members' properties as it will return rows not ordered by Subset's ID. I think the HQL query parser should not permit this. -- 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

17 years, 5 months

2
4
0 / 0

[Hibernate-JIRA] Created: (ANN-603) Using @CollectionOfEelements with FetchMode.JOIN and FetchType.EAGER to map a Map breaks Example criteria

by Philippe Laflamme (JIRA)

Using @CollectionOfEelements with FetchMode.JOIN and FetchType.EAGER to map a Map breaks Example criteria --------------------------------------------------------------------------------------------------------- Key: ANN-603 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-603 Project: Hibernate Annotations Issue Type: Bug Components: search Affects Versions: 3.3.0.ga Environment: hibernate-core-3.2.2.jar Reporter: Philippe Laflamme Attachments: ann-example_eager_join.patch I'm using CollectionOfElements to map a Map<String, @Embeddable>. I want it to eagerly join the associated table to fill the map. When I load the Entity using its PK, I obtain a single object with multiple entries in the Map, which is the expected behaviour. If I load the same Entity using an Example criteria (matching one of its property), I get one Entity per entry in the Map. If you use FetchMode.SELECT, the resulting Example query returns a single entity with multiple values in the Map (expected behaviour). Attached is a patch against annotations_3_3_0_GA that creates a test case in CollectionElementTest that reproduces the problem. -- 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

17 years, 5 months

4
3
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 February 2008