May 2007 - hibernate-issues - Jboss List Archives

[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

15 years, 8 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

15 years, 8 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

15 years, 8 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

15 years, 8 months

1
3
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

15 years, 8 months

4
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2066) HSQL DB + multi-schema --> raised an exception (Problem to get an increment key [select max(id) from table)

by XOrangOutan (JIRA)

HSQL DB + multi-schema --> raised an exception (Problem to get an increment key [select max(id) from table) ----------------------------------------------------------------------------------------------------------- Key: HHH-2066 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2066 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.cr4 Environment: HSQL DB 1.8.x Reporter: XOrangOutan When trying to save an object that has an "incremental" primary key, Hibernate API tries to know what the max current id is by executing a "SELECT MAX". Though, in this particular sql query, schema name is not taken into account (in hsqldialect). This cause an error that prevents anyone from carrying out unit tests. This bug also exists on 3.x versions -- 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, 8 months

4
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2281) CLONE -Calling Session.connection() generates java.lang.IllegalArgumentException: interface org.hibernate.jdbc.ConnectionWrapper is not visible from class loader

by Sergey Polzunov (JIRA)

CLONE -Calling Session.connection() generates java.lang.IllegalArgumentException: interface org.hibernate.jdbc.ConnectionWrapper is not visible from class loader ----------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-2281 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2281 Project: Hibernate3 Type: Bug Versions: 3.2.1 Environment: Hibernate checked out from trunk; revision 10717 Reporter: Sergey Polzunov Calling Session.connection() always generates an exception. Here is the stacktrace I get from the attached test case: Exception in thread "main" java.lang.IllegalArgumentException: interface org.hibernate.jdbc.ConnectionWrapper is not visible from class loader at java.lang.reflect.Proxy.getProxyClass(Proxy.java:353) at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:581) at org.hibernate.jdbc.BorrowedConnectionProxy.generateProxy(BorrowedConnectionProxy.java:56) at org.hibernate.jdbc.ConnectionManager.borrowConnection(ConnectionManager.java:163) at org.hibernate.jdbc.JDBCContext.borrowConnection(JDBCContext.java:111) at org.hibernate.impl.SessionImpl.connection(SessionImpl.java:359) at TestSession.main(TestSession.java:16) Changing the Connection.class.getClassLoader() to BorrowedConnectionProxy.class.getClassLoader() on line 57 in the generateProxy() method solves the problem. I am not very familiar with class loaders so I don't know if this is likeley to cause other problems elsewhere. Removing the ConnectionWrapper.class from the PROXY_INTERFACES array in the org.hibernate.jdbc.BorrowedConnectionProxy also solves the problem, but I guess it was added for a reason. -- 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, 8 months

11
17
0 / 0

[Hibernate-JIRA] Created: (HHH-2254) A query validation bug produces QueryException: "Expected positional parameter count: 1, actual parameters: [Parent@bec357b] [from Child this where this.id.parent = ?]"

by Hernan Liendo (JIRA)

A query validation bug produces QueryException: "Expected positional parameter count: 1, actual parameters: [Parent@bec357b] [from Child this where this.id.parent = ?]" ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ Key: HHH-2254 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2254 Project: Hibernate3 Type: Bug Components: query-hql Versions: 3.2.0.ga Environment: Hibernate 3.2 using Sybase. However this is not an environment caused problem. It's supposed to happen in every environment. Reporter: Hernan Liendo -- Short description ============================================================================ -- A query validation bug produces QueryException: "Expected positional parameter count: 1, actual parameters: [Parent@bec357b] [from Child this where this.id.parent = ?]. Both Parent and Child use composite keys. -- Context ====================================================================================== -- Having composite keys for a Parent class and a Child class, I want to retrieve childs that belong to an specific Parent. -- Parent Definition ============================================================================ -- public class Parent { public ParentId ParentId; ... } public class ParentId { private String idField1; private int idField2; ... } // the parent mapping <hibernate-mapping> <class mutable="false" table="xx" name="Parent"> <composite-id class="ParentId" access="field" name="parentId"> <key-property column="idField1" access="field" name="idField1"/> <key-property column="idField2" access="field" name="idField2"/> </composite-id> </class> </hibernate-mapping> -- Child Definition ============================================================================ -- public class Child { public ChildId childId; ... } public class ChildId { public Parent parent; public String aditionalIdField; ... } // the mapping <hibernate-mapping> <class mutable="false" table="yyy" name="Child"> <composite-id class="ChildId" access="field" name="childId"> <key-many-to-one name="parent" class="Parent" access="field"> <column name="idField1" not-null="true" /> <column name="idField2" not-null="true" /> </key-many-to-one> <key-property column="aditionalIdField" access="field" name="aditionalIdField"/> </composite-id> </class> </hibernate-mapping> -- HQL Statement ============================================================================ -- from Child this where this.childId.parent = ? or from Child this where this.id.parent = ? // using aliased id -- The Exception ============================================================================ -- org.hibernate.QueryException: Expected positional parameter count: 1, actual parameters: [Parent@bec357b] [from Child this where this.childId.parent = ?] at org.hibernate.impl.AbstractQueryImpl.verifyParameters(AbstractQueryImpl.java:319) at org.hibernate.impl.AbstractQueryImpl.verifyParameters(AbstractQueryImpl.java:275) at org.hibernate.impl.QueryImpl.list(QueryImpl.java:75) ... -- The Problem ============================================================================ -- class: org.hibernate.impl.AbstractQueryImpl method: protected void verifyParameters(boolean reserveFirstParameter) throws HibernateException line: 286 The method validates parameters. It resolves the "positionalValueSpan" variable witch in my case gets the value of 2 (One for parent's idField1 and the other for parent's idField2). The method compares positionalValueSpan (2) with parameterMetadata.getOrdinalParameterCount() witch it is 1 (the quantity of "?" signs in the HQL statement". This bug only happens when: 1. composed keys are used (and) 2. having a parent-child relationship (and) 3. resolving children from certain parent. -- Hibernate user workaround ============================================================================ -- Not to use a parent instance variable in the Child class. Hope this helps. If you guys need the source code in order to check the bug, please let me know it. Good luck! Hernan -- 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, 9 months

4
6
0 / 0

[Hibernate-JIRA] Created: (EJB-287) Upload 3.3.1.GA to the Maven repository

by Aleksei Valikov (JIRA)

Upload 3.3.1.GA to the Maven repository --------------------------------------- Key: EJB-287 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-287 Project: Hibernate Entity Manager Issue Type: Improvement Components: EntityManager Affects Versions: 3.3.1.GA Reporter: Aleksei Valikov Priority: Minor Attachments: hibernate-entitymanager-3.3.1.ga.pom Would you please upload the entity manager as well as dependent artifacts to the Maven repository? This is quite important for Maven builds. Dependent artifacts are: hibernate-commons-annotations (3.0.0.ga) hibernate-validator (3.0.0.ga) jboss-archive-browsing (2.0.2.alpha) Below are the commands I used to deploy these artifacts, I hope this helps. I also attach the POM file for the entity manager. I hope you could reuse it in further versions. Thank you! mvn deploy:deploy-file -DgroupId=org.hibernate -DartifactId=hibernate-entitymanager -Dversion=3.3.1.ga -Dpackaging=jar -Dfile=hibernate-entitymanager-3.3.1.ga.jar -DpomFile=hibernate-entitymanager-3.3.1.ga.pom -Durl=file://C:/Projects/p2.external/maven2-repository/www/repository mvn deploy:deploy-file -DgroupId=org.hibernate -DartifactId=hibernate-commons-annotations -Dversion=3.0.0.ga -Dpackaging=jar -Dfile=hibernate-commons-annotations-3.0.0.ga.jar -Durl=file://C:/Projects/p2.external/maven2-repository/www/repository mvn deploy:deploy-file -DgroupId=org.hibernate -DartifactId=hibernate-validator -Dversion=3.0.0.ga -Dpackaging=jar -Dfile=hibernate-validator-3.0.0.ga.jar -Durl=file://C:/Projects/p2.external/maven2-repository/www/repository mvn deploy:deploy-file -DgroupId=jboss -DartifactId=jboss-archive-browsing -Dversion=2.0.2.alpha -Dpackaging=jar -Dfile=jboss-archive-browsing-2.0.2.alpha.jar -Durl=file://C:/Projects/p2.external/maven2-repository/www/repository -- 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, 9 months

4
10
0 / 0

[Hibernate-JIRA] Created: (EJB-279) Entity Listener defined in orm.xml does not work

by Gary Ip (JIRA)

Entity Listener defined in orm.xml does not work ------------------------------------------------ Key: EJB-279 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-279 Project: Hibernate Entity Manager Type: Bug Components: EntityManager Versions: 3.3.0.ga Environment: Hibernate core 3.2.2.GA, Hibernate Annotations 3.3.0.GA, Hibernate Entity Manager 3.3.0.GA, Spring 2.0.3, Tomcat 5.5.20, Oracle 9i Reporter: Gary Ip A default Entity Listener defined in orm.xml (this EJB3 deployment descriptor) worked in HEM and HAN 3.2.1 but not 3.3.0 http://forums.hibernate.org/viewtopic.php?t=972352&sid=95588b2c2391806158... -- 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, 9 months

4
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues May 2007