October 2006 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HB-1570) CLONE -dropIndex doesn't cound on Dialect

by Ohad Bruker (JIRA)

CLONE -dropIndex doesn't cound on Dialect ----------------------------------------- Key: HB-1570 URL: http://opensource.atlassian.com/projects/hibernate/browse/HB-1570 Project: Hibernate2 Type: Bug Components: core Versions: 2.1.6 Environment: Hibernate 2.1.6, MySql 4.?? Reporter: Ohad Bruker In class net.sf.hibernate.mapping.Index method sqlDropString(Dialect dialect) doesn't count on dialect, and always makes name of index qualified: return "drop index " + StringHelper.qualify( table.getQualifiedName(dialect), name); This will fail at least in case of MySql DB, because it doesn't understand {tablename}.{indexname} constructions, but {indexname} only. I propose next edition: return "drop index " + (dialect.qualifyIndexName() ? StringHelper.qualify( table.getQualifiedName(dialect), name) : name); Is it suitable? -- 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
7
0 / 0

[Hibernate-JIRA] Created: (HHH-2118) hibernate cant find dialect class and drivers cause of blanks in hibernate.property file

by Daniel Lärm (JIRA)

hibernate cant find dialect class and drivers cause of blanks in hibernate.property file ----------------------------------------------------------------------------------------- Key: HHH-2118 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2118 Project: Hibernate3 Type: Bug Components: core, build Versions: 3.2.0.cr4 Environment: Red Hat Enterprise Linux 4 Windows XP SP2 Ingres2006 Reporter: Daniel Lärm The ingres section in the hibernate.property file consists of 4 lines, where at the end of each line is an blank, that is not neccesary and causes errors when building hibernate and running the certification tests. The first line generates an error, that he cant find the ingres dialect class, the second, that he cant find the jdbc driver and so on. After removing these blanks, there are none of these errors and it is working fine. In the svn trunk of hibernate 3 there are also blanks there. Perhaps these problems are also with other database sections in the property file, but i didnt check them. Daniel -- 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: (HHH-2155) mysql dialect should not generate automatically index for foreign key

by Anthony Patricio (JIRA)

mysql dialect should not generate automatically index for foreign key --------------------------------------------------------------------- Key: HHH-2155 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2155 Project: Hibernate3 Type: Improvement Components: core Environment: MySQL Reporter: Anthony Patricio Priority: Minor Attachments: patch-mysqlDialect.txt MySQLDialect.getAddForeignKeyConstraintString(String, String[], String, String[], boolean) method is generating also index which is not wanted. Here is the modified method: public String getAddForeignKeyConstraintString( String constraintName, String[] foreignKey, String referencedTable, String[] primaryKey, boolean referencesPrimaryKey ) { String cols = StringHelper.join(", ", foreignKey); return new StringBuffer(30) //.append(" add index ") //.append(constraintName) //.append(" (") //.append(cols) //.append("), add constraint ") .append(" add constraint ") .append(constraintName) .append(" foreign key (") .append(cols) .append(") references ") .append(referencedTable) .append(" (") .append( StringHelper.join(", ", primaryKey) ) .append(')') .toString(); } -- 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: (EJB-217) Multiple @OneToMany(fetch=FetchType.EAGER) relationships not supported

by Michał Borowiecki (JIRA)

Multiple @OneToMany(fetch=FetchType.EAGER) relationships not supported ----------------------------------------------------------------------- Key: EJB-217 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-217 Project: Hibernate Entity Manager Type: Bug Versions: 3.2.0.cr1 Environment: JBoss4.0.4.GA Reporter: Michał Borowiecki Having more than one relationship on en entity annotated with @OneToMany(fetch=FetchType.EAGER) causes exception when deploying the ejb3 module: org.hibernate.HibernateException: cannot simultaneously fetch multiple bags. This bug is thoroughly explained here: http://www.jroller.com/page/eyallupu?entry=hibernate_exception_simultaneo... and depends on HHH-1718 "Have multiple bag fetches revert to subselect fetching for all but one of the bags" The temporary solution in HHH-1413 - disallowing multiple bag fetches is unsuitable to ejb3 environment, because the spec does not disallow it. -- 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, 6 months

3
3
0 / 0

[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

17 years, 6 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

17 years, 7 months

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

17 years, 9 months

12
56
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

17 years, 9 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

17 years, 9 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

17 years, 10 months

7
16
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues October 2006