November 2006 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-2073) many-to-one join fetch with optional parent causing stray query to fire

by Adam Hardy (JIRA)

many-to-one join fetch with optional parent causing stray query to fire ----------------------------------------------------------------------- Key: HHH-2073 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2073 Project: Hibernate3 Type: Bug Reporter: Adam Hardy Priority: Minor Attachments: bugtest.zip I have a call centre application which uses a mature database and is therefore pushing Hibernate to accomplish the mappings I need. The issue here is extra queries that Hibernate is firing where I set up the mapping to do a join in one hit. I am fetching child objects which may or may not have a parent. The child's foreign key points to a non-primary key on the parent. This is not reflected by a foreign key constraint in the database (hence it allows child to have no parent). If the child object has the foreign key 0 instead of null, which is the protocol in this database, then the parent which doesn't exist is not (& cannot) be instantiated, no problem, but then after processing the resultset, Hibernate fires off another query to fetch the parent that it could not find data for in the first query. This is obviously unnecessary in this context and degrades the performance on large searches on this child. I have classified it as minor since I suspect there may be work-arounds but I have not researched that yet. I didn't know whether I could put the mapping XML in the query, so I have attached a simplistic testcase example that demonstrates the problem. The following forum messages are relevant and the latter contains the mappings, which is easier than extracting them out of the testcase zip: http://forum.hibernate.org/viewtopic.php?t=960522 http://forum.hibernate.org/viewtopic.php?t=964211 -- 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

16 years, 2 months

2
1
0 / 0

[Hibernate-JIRA] Created: (ANN-442) Support @GenericGenerators

by Emmanuel Bernard (JIRA)

Support @GenericGenerators -------------------------- Key: ANN-442 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-442 Project: Hibernate Annotations Type: New Feature Components: binder Reporter: Emmanuel Bernard Priority: Minor To support more than one generic generator in package-info.java -- 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

16 years, 3 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2222) SpringFramework 2.0 uses ASM.JAR versions 2.2.2. This is incompatible with Hibernate 3.2 as it uses and "unknown" previous version of ASM.JAR

by Greg McGregor (JIRA)

SpringFramework 2.0 uses ASM.JAR versions 2.2.2. This is incompatible with Hibernate 3.2 as it uses and "unknown" previous version of ASM.JAR ---------------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-2222 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2222 Project: Hibernate3 Type: Improvement Versions: 3.2.0.ga Environment: Hibernate 3.2.0ga Reporter: Greg McGregor SpringFramework 2.0 uses ASM.JAR from ObjectWeb version 2.2.2. However, Hibernate 3.2.0ga utilizes an "unknown" previous version of the ASM.JAR. The issue is that the method signatures and classes have changed between the two versions. Therefore, Hibernate 3.2.0ga won't run with the new ASM.JAR and Spring 2.0 won't run with the previous ASM.JAR. Mushing the two JARs together in an attempt to get something going results in a NoSuchMethodError (which would make sense). Although this isn't a direct Hibernate3 bug, it does preclude stable use with Spring 2.0/ -- 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

16 years, 4 months

9
25
0 / 0

[Hibernate-JIRA] Created: (HHH-2159) Query that previously worked in 3.2.0CR2 does not work anymore

by Andy Dale (JIRA)

Query that previously worked in 3.2.0CR2 does not work anymore --------------------------------------------------------------- Key: HHH-2159 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2159 Project: Hibernate3 Type: Bug Versions: 3.2.0.ga Environment: hibernate 3.2.0GA, PostgreSQL 8.1.4 (using build 407 of the JDBC driver). JDK 1.5.0_06, JBoss 4.0.4GA, Operating system is Fedora Core 5 Reporter: Andy Dale Attachments: hibernate_testcase.tar.gz First off i do not know if this bug belongs to the Hibernate3(core) or Hibernate EntityManger branch, but have entered it against core because that is where the exception occurs (in org.hibernate.hql.ast.tree.FromClause.findIntendedAliasedFromElementBasedOnCrazyJPARequirements). I have a relativley simple entity setup up to test a proof of concept. Persisting the data to the database is not a problem in the new version 3.2.0.GA, but the problems occurs when trying to perform a query on the persisted data, the very same query works with 3.2.0CR2 but gives a nullPointException in 3.2.0GA. I have attached the java source for the entities + session bean (in hibernate_testcase.tar.gz/entities file) and the java class (in hibernate_testcase.tar.gz/service file) that is used to persist and query the data, and because this was only meant to be a proof of concept i have also included the .ear archive as apart from the entity definitions and session bean the only other thing it contains is a JBoss .sar archive which calls the static persist and query methods in the session bean (service test.testcase). Please note to use the .ear archive you need a datasource called Postgres_Test -- 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

16 years, 5 months

12
56
0 / 0

[Hibernate-JIRA] Created: (HHH-2211) A createQuery() caused ORA-00904 error

by sodia (JIRA)

A createQuery() caused ORA-00904 error -------------------------------------- Key: HHH-2211 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2211 Project: Hibernate3 Type: Bug Components: query-hql Versions: 3.2.0.ga Environment: JDK1.5.0+Eclipse3.2.1+Hibernate3.2.0.ga+Oracle9.2.0+WinXp(Prof)Sp2 Reporter: sodia Priority: Trivial Attachments: hiber-grammar-sql-and-errlog.zip, hiber-grammar-test.zip I want to try the following sql under hibernate,it failed. (The project is build on the basis of hibernate3.2's tutorial) String hqlAlias = "insert into EventHistory ( id, date, title )" + " select id, date, title from Event e" + " where e.title like 'BUY%'" + " and exists" + " ( select 1 from PersonEvent p" + " where p.id=e.id)"; int resultAlias = session.createQuery(hqlAlias).executeUpdate(); But it works nice under sqlplus. INSERT INTO EVENTS_HISTORY SELECT * FROM EVENTS WHERE TITLE LIKE 'BUY%' AND EXISTS ( SELECT 1 FROM PERSON_EVENT WHERE EVENT_ID=EVENTS.EVENT_ID); The 4 lines of error log is like this: 15:33:29,906 DEBUG SQL:393 - insert into EVENTS_HISTORY ( EVENT_ID, EVENT_DATE, title ) select event0_.EVENT_ID as col_0_0_, event0_.EVENT_DATE as col_1_0_, event0_.title as col_2_0_ from EVENTS event0_ where (event0_.title like 'BUY%') and (exists (select 1 from PERSON_EVENT personeven1_ where personeven1_.EVENT_ID=EVENTS.EVENT_ID)) Hibernate: insert into EVENTS_HISTORY ( EVENT_ID, EVENT_DATE, title ) select event0_.EVENT_ID as col_0_0_, event0_.EVENT_DATE as col_1_0_, event0_.title as col_2_0_ from EVENTS event0_ where (event0_.title like 'BUY%') and (exists (select 1 from PERSON_EVENT personeven1_ where personeven1_.EVENT_ID=EVENTS.EVENT_ID)) 15:33:29,984 WARN JDBCExceptionReporter:71 - SQL Error: 904, SQLState: 42000 15:33:29,984 ERROR JDBCExceptionReporter:72 - ORA-00904: "EVENTS"."EVENT_ID": 无效的？？符 Is there any wrong with the hql,or it's alias? Thanks to anyone who pay attetion to this trivial question which I search the forum and google without solutions. Or if I missed them,I would be grateful that you might tell me where can I find the right answer to fix this hql grammar error. -- 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

16 years, 5 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2110) Proxied object causes ClassCastException when method returns 'this' in a composite hierarchy

by Philip Nightingale (JIRA)

Proxied object causes ClassCastException when method returns 'this' in a composite hierarchy -------------------------------------------------------------------------------------------- Key: HHH-2110 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2110 Project: Hibernate3 Type: Bug Components: core Versions: 3.0.5 Environment: Hibernate 3, any database (test case uses HSQL, issue found using Oracle) Reporter: Philip Nightingale Attachments: HibernateClassCastExceptionTest.zip If a proxied object has a method that returns 'this' and the proxy type extends the same base class as the target object and the return type of the method is the target class type then a ClassCastException is thrown. The error can be tracked down to the method CGLibLazyInitializer::intercept(Object, Method, Object[], MethodProxy). In this method, if the object returned from the method call on the target object is the same as the target object, then instead of returning the object itself the proxy is returned. This is fine in most cases, but in the special case described, in which the proxy extends a base class that is also extended by the target class, then the CCE occurs. In the submitted test case I have a simple composite hierarchy with an abstract base type and two concrete subtypes. Either type can contain children, but only one can be the root of the hierarchy (and cannot itslef be a child). There is a many-to-one relationship defined from the sub-type that may be a child to the base class. The submitted test case is configured to use Hypersonic DB so hsqldb.jar is required on the classpath. Further details and code snippets from the original code that caused the exception are posted on the Hibernate user forum (topic "ClassCastException with CGLIB Lazy Initialization") -- 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

16 years, 5 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2048) Incomplete MappingException at org.hibernate.mapping.SimpleValue

by Diego Pires Plentz (JIRA)

Incomplete MappingException at org.hibernate.mapping.SimpleValue ---------------------------------------------------------------- Key: HHH-2048 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2048 Project: Hibernate3 Type: Improvement Versions: 3.2.0.cr4 Reporter: Diego Pires Plentz When a mapped class has a wrong type, an exception is throwed, but it doesnt say nothing about what class/table is mapped wrongly. public Type getType() throws MappingException { if (typeName==null) { throw new MappingException("No type name"); } Type result = TypeFactory.heuristicType(typeName, typeParameters); if (result==null) { String msg = "Could not determine type for: " + typeName; if(columns!=null && columns.size()>0) { msg += ", for columns: " + columns; } throw new MappingException(msg); } return result; } Can become something like this... public Type getType() throws MappingException { if (typeName==null) { throw new MappingException("No type name"); } Type result = TypeFactory.heuristicType(typeName, typeParameters); if (result==null) { String msg = "Could not determine type for: " + typeName; if(table != null){ msg += ", at table: " + table.getName(); } if(columns!=null && columns.size()>0) { msg += ", for columns: " + columns; } throw new MappingException(msg); } return result; } -- 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

16 years, 5 months

3
6
0 / 0

[Hibernate-JIRA] Created: (HBX-733) Updated DAO code generation as discussed over the email

by Alex Kalinovsky (JIRA)

Updated DAO code generation as discussed over the email ------------------------------------------------------- Key: HBX-733 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-733 Project: Hibernate Tools Type: Patch Components: hbm2java, ant Versions: 3.1alpha5 Environment: I have tested the patch on the latest version of Hibernate Tools I got from SVN 2 weeks ago. Reporter: Alex Kalinovsky Attachments: dao_generation.patch This should be a complete implementation of DAO generation according to the design we have discussed over the email. I've tested this on our project so the DAOs should be good to go, but of course a more diverse testing would be needed before releasing it to public. I'm open for recommendations and suggestions, so I see this as the first draft. Below is a list of files and comments. Contact me at kalinovsky(a)yahoo.com. src/java/org/hibernate/tool/hbm2x DAONewExporter.java This class is coded mainly to accept additional parameters such as dao package name and provide flexible file naming that is used by Ant task. It would not be needed if I integrate my changes into GenericExporter. src/templates/dao crudDao.ftl template for regeneratable CRUD interface crudDaoImpl.ftl template for regeneratable CRUD DAO implementation dao.ftl template for customizable DAO interface that extends CRUD interface daoImpl.ftl template for customizable DAO implementation that extends CRUD implementation src/templates/dao/base dao.ftl base interface for all DAOs queryDao.ftl base interface for all read-only entities crudDao.ftl base interface for all editable entities src/templates/dao/base/hibernate abstractDao.ftl base implementation of DAO using Hibernate abstractQueryDao.ftl base implementation of DAO for read-only entities using Hibernate abstractCrudDao.ftl base implementation of DAO for editable entities using Hibernate src/testsupport codegen.properties Test configuration to see DAO generation in action codegen-build.xml Test build file that generates DAOs for Author and Article and compiles generated code -- 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

16 years, 6 months

7
16
0 / 0

[Hibernate-JIRA] Created: (HHH-2161) hibernate.dialect = org.hibernate.dialect.PostgreSQLDialect, sqltype = char, NUL but not NULL.

by Shutra (JIRA)

hibernate.dialect = org.hibernate.dialect.PostgreSQLDialect, sqltype = char, NUL but not NULL. ---------------------------------------------------------------------------------------------- Key: HHH-2161 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2161 Project: Hibernate3 Type: Bug Environment: hibernate-3.2.0.cr5.jar, postgresql 8.1.x Reporter: Shutra When insert, if the sql type is char and the value is null, then the generated sql is like this: insert into table (column) values(?), then the postgresql said: insert into table(column) values(NUL) but not insert into table(column) value(NULL). Important: the sql type is character(in mapping file) and the java type is char. -- 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

16 years, 6 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2114) Teradata Dialect Implementation

by Mike Hazelwood (JIRA)

Teradata Dialect Implementation ------------------------------- Key: HHH-2114 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2114 Project: Hibernate3 Type: Patch Versions: 3.1.3 Environment: Hibernate 3.1.3. Teradata version V2R6 Reporter: Mike Hazelwood Priority: Minor Attachments: TeradataDialect.java Teradata Dialect for Hibernate 3.1 that uses identity columns to generate IDs and uses the "qualify row_number" syntax to implement limit functionality. -- 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

16 years, 6 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues November 2006