December 2006 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-2207) Suggested fix for HQL - MySQL setMaxResults issue

by Toby Moore (JIRA)

Suggested fix for HQL - MySQL setMaxResults issue ------------------------------------------------- Key: HHH-2207 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2207 Project: Hibernate3 Type: Bug Components: query-hql Versions: 3.2.0.ga Environment: Hi 3.2.0.ga MySQL Reporter: Toby Moore Hi, After some experimentation, we'd like to suggest an easy fix to a problem we encountered. When using HQL with the Hibernate 3 entity manager to limit the number of records returned ( at the database level, via generated SQL, not in memory) we were getting an exception due to the query builder trying to attach a parameter to the prepared statement that was out of bounds : by: java.sql.SQLException: Parameter index out of range (4 > number of parameters, which is 3). at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:910) at com.mysql.jdbc.PreparedStatement.setInternal(PreparedStatement.java:2556) at com.mysql.jdbc.PreparedStatement.setInternal(PreparedStatement.java:2584) at com.mysql.jdbc.PreparedStatement.setInt(PreparedStatement.java:2540) at com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.setInt(NewProxyPreparedStatement.java:677) at org.hibernate.loader.Loader.bindLimitParameters(Loader.java:1616) at org.hibernate.loader.Loader.prepareQueryStatement(Loader.java:1560) at org.hibernate.loader.Loader.doQuery(Loader.java:661) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:224) at org.hibernate.loader.Loader.doList(Loader.java:2156) ... 10 more On looking at the code in the method bindParameterValues in org.hibernate.loader.hql.QueryLoader ( line 491 ) the method returns the next parameter position that needs to be set, not the amount of parameters it has added, which is expected in Loader.java on the line col += bindParameterValues( st, queryParameters, col, session ); This causes the parameter count to get out of sync and thus throw the expcetion saying that it can't add a parameter out of range. A simple fix for this is to change the return line in QueryLoader to be return position - startPosition; which will return the amount of parameters this method added. We've tested this on our mysql implementation and it works, and run the unit tests to check that no extra errors are generated. If this seems like a good fix then i'll submit it as a patch via the JIRA, but would like to hear any thoughts first? Kind regards, TobyM - MindCandyDesign London -- 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

18 years

6
32
0 / 0

[Hibernate-JIRA] Updated: (HHH-1538) aggregations functions in EJBQL queries does not return the appropriate types

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1538?page=all ] Steve Ebersole updated HHH-1538: -------------------------------- Comment: was deleted > aggregations functions in EJBQL queries does not return the appropriate types > ----------------------------------------------------------------------------- > > Key: HHH-1538 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1538 > Project: Hibernate3 > Type: Improvement > Components: core > Versions: 3.2.0.alpha1 > Reporter: Emmanuel Bernard > Fix For: 3.2.0.cr2 > > > EJB3 requires a Long, not an Integer -- 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

18 years

1
0
0 / 0

Annotation Exception: Use of @OneToMany or @ManyToMany targeting an unmapped class

by Tim Downey

I am using Hibernate Annotations 3.2.0.GA. I have just upgraded from Hibernate Annotations Hibernate Annotations 3.0.beta2. In the earlier release, I created a class that had a property for an array of strings. This array is being populated from a HTML form. This is running in a servlet and I use hbm2ddl to create the tables. The class looks like this. @Entity public class ComplexDataPersistent { ... private String[] extra; @OneToMany @IndexColumn(name="extra_pos", base=0) public String[] getExtra() { return extra; } public void setExtra(String extra) { this.extra = extra; } ... } In the earlier release, a table was created for ComplexDataPersistent and a related table was created for String array, named ComplexDataPersistent_extra. All was good. In the new release, when I run the code, I get this error. ERROR 2006-12-11 09:25:52,526 - Error in bean; could not initialize Hibernate. org.hibernate.AnnotationException: Use of @OneToMany or @ManyToMany targeting an unmapped class: ch6.complexPersistent.ComplexDataPersistent.extra[java.lang.String] at org.hibernate.cfg.annotations.CollectionBinder.bindManyToManySecondPass(CollectionBinder.java:979) at org.hibernate.cfg.annotations.CollectionBinder.bindStarToManySecondPass(CollectionBinder.java:530) at org.hibernate.cfg.annotations.ListBinder$1.secondPass(ListBinder.java:65) at org.hibernate.cfg.CollectionSecondPass.doSecondPass(CollectionSecondPass.java:43) at org.hibernate.cfg.Configuration.secondPassCompile(Configuration.java:1127) at org.hibernate.cfg.AnnotationConfiguration.secondPassCompile(AnnotationConfiguration.java:296) at org.hibernate.cfg.Configuration.generateDropSchemaScript(Configuration.java:756) at org.hibernate.tool.hbm2ddl.SchemaExport.<init>(SchemaExport.java:93) at org.hibernate.tool.hbm2ddl.SchemaExport.<init>(SchemaExport.java:61) at utilities.HibernateUtil.initSessionFactory(HibernateUtil.java:45) I looked into the code source for both versions and found the following difference in CollectionBinder for the new release. //check for user error if ( ! isCollectionOfEntities ) { if ( property.isAnnotationPresent( ManyToMany.class ) || property.isAnnotationPresent( OneToMany.class ) ) { String path = collValue.getOwnerEntityName() + "." + joinColumns[0].getPropertyName(); throw new AnnotationException( "Use of @OneToMany or @ManyToMany targeting an unmapped class: " + path + "[" + collType + "]" ); } else { JoinTable joinTableAnn = property.getAnnotation( JoinTable.class ); if ( joinTableAnn != null && joinTableAnn.inverseJoinColumns().length > 0 ) { String path = collValue.getOwnerEntityName() + "." + joinColumns[0].getPropertyName(); throw new AnnotationException( "Use of @JoinTable.inverseJoinColumns targeting an unmapped class: " + path + "[" + collType + "]" ); } } } This code is executed when the servlet starts and tries to drop the previous tables. It is unable to find the table for the string array, so an exception is thrown. The exception is preventing the tables from being created the first time. I modified the code so that an error is written to the log instead of having an exception thrown and my code now works in the new version. if ( property.isAnnotationPresent( ManyToMany.class ) || property.isAnnotationPresent( OneToMany.class ) ) { String path = collValue.getOwnerEntityName() + "." + joinColumns[0].getPropertyName(); //throw new AnnotationException( log.error("Use of @OneToMany or @ManyToMany targeting an unmapped class: " + path + "[" + collType + "]"); //); } Now the table for the string array is created as it was before and the application is running as it did before.

18 years

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1538) aggregations functions in EJBQL queries does not return the appropriate types

by john john (JIRA)

18 years

1
0
0 / 0

[Hibernate-JIRA] Commented: (HB-655) Oracle limitation: large "where x in (....)'

by Ritesh (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HB-655?page=com... ] Ritesh commented on HB-655: --------------------------- Hi Emmanuel, We have a similar issue where the no of elements in a criteria in clause is more then 1000. See that the issue status is Won't Fix. IN that case possibly we will have to find a workaround in the code. But can you let us know why was it decided against fixing this issue and what were the possible concerns . > Oracle limitation: large "where x in (....)' > -------------------------------------------- > > Key: HB-655 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HB-655 > Project: Hibernate2 > Type: Improvement > Components: core > Versions: 2.1.1 > Environment: Hibernate 2.1.1 > Oracle 8i > Reporter: Christian Gruber > Assignee: Emmanuel Bernard > > > Hello! > There is a problem with queries with named parameters that consist of big lists with Oracle. An example: > Collection idList = new LinkedList(); > for (int i=0; i<1001; i++) { > idList.add(new Integer(i)); > } > Query query = session.createQuery("from Geneticelem as geneticelem where geneticelem.id in (:ids)"); > query.setParameterList("ids", idList, Hibernate.INTEGER); > Iterator geneticelems = query.iterate(); > This code results in an ORA-01795 exception, because not more than 1000 elements are allowed for "in". > In OJB, this is solved by splitting the "in" condition is split up in chunks: http://db.apache.org/ojb/api/org/apache/ojb/broker/query/Criteria.html#ad... > Can something like this also be implemented in Hibernate? I know, it's a limitation that will rarely be encountered, but still it's a limitation. > Thanks, > Christian -- 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

18 years

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-980) FetchMode.SELECT javadoc wrong

by Baptiste MATHUS (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-980?page=co... ] Baptiste MATHUS commented on HHH-980: ------------------------------------- What's the meaning of lazy. I mean, I think I know it but, from what I understood, that's : Say you have A which contains a list of B * Retrieve A with a criteria query like session.createCriteria(A.class).setFetchMode("b",FetchMode.SELECT); * close the session * access a.getB() without receiving a LazyInitException ? I just re-tried this use case and received a LazyInitException... Maybe I've not understood something, I'll certainly post a thread in the forum so as this behaviour can be explained further. > FetchMode.SELECT javadoc wrong > ------------------------------ > > Key: HHH-980 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-980 > Project: Hibernate3 > Type: Bug > Components: documentation > Versions: 3.1 beta 2 > Reporter: Dave Brondsema > Priority: Minor > > > FetchMode.SELECT says "Fetch eagerly, using a separate select." but it should say "Fetch lazily, using a separate select." > This is quite misleading -- 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

18 years

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-952) Patch to allow subqueries with joins using Criteria API and Subqueries with DetachedCriteria

by Andrew Carroll (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-952?page=co... ] Andrew Carroll commented on HHH-952: ------------------------------------ This bug still exists in the 3.1.3 src tree and even in the 3.2 src tree. I've tested the subquery-patch-313.txt with Oracle 10g and it works well. > Patch to allow subqueries with joins using Criteria API and Subqueries with DetachedCriteria > -------------------------------------------------------------------------------------------- > > Key: HHH-952 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-952 > Project: Hibernate3 > Type: Patch > Components: core > Versions: 3.1 beta 1, 3.1 beta 2 > Environment: 3.1beta1 with MS SQL 2000 via jTDS > Reporter: John > Priority: Critical > Attachments: SubqueryExpression.java, subquery-patch-311.txt, subquery-patch-313.txt, subquery-patch-31beta3.txt, subquery-patch.txt, subquery-patch.txt > > > The existing code in SubqueryExpression.java constructed a select statement but did not have any provisions for creating joins. Therefore, it was not possible using the criteria API to create an exists subselect that had a join, even though running the source DetachedCriteria alone works perfectly. > For example, if this is the goal: > select * from foo f > where exists (select id from bar b join other o on b.o_id = o.id where o.prop = '123' and b.foo_id = f.id) > One might try something like this: > Criteria crit = session.createCriteria(Foo.class, fooAlias); > DetachedCriteria barCrit = DetachedCriteria.forClass(Bar.class, barAlias); > DetachedCriteria otherCrit = barCrit.createCriteria(Bar.OTHER_JOIN); > otherCrit.add( Restrictions.eq(Other.PROP, "123") ); > barCrit.add( Restrictions.eqProperty( -- props to join to foo here --) ); > barCrit.setProjection( Projections.id() ); > crit.add( Subqueries.exists(barCrit) ); > However, the existing code generates something like the following, which gets an error with an unknown alias 'o': > select * from foo f > where exists (select id from bar b where o.prop = '123' and b.foo_id = f.id) > This is also described here (at the end): http://forum.hibernate.org/viewtopic.php?t=942488 > The patch to SubqueryExpression.java fixes this to included the joins necessary for the filtering. This code was modeled (copied) off of code from CriteriaLoader. For me this works perfectly, but I don't understand the internals of this stuff enough to say how robust it is. Also included is a patch to the test case to enable testing of this, which was present but commented out. I did not change the contents of the test, which currently only attempts a joined subquery. This used to fail with an error, but now it works. The test does not check the results at all. (Inconsequential to the patch - Enrollment has two Ls.) > -----side notes > The patch file also has two other patches. The first increases the delay in BulkManipulationTest because I was getting inconsistent test results. I think that the precision on the version timestamp is not enough for 300 milliseconds delay to be enough to guarantee the test results. Also, in build.xml, there was a line that was meant to exclude the performance tests, but there was no **/*, on *, so they actually were not excluded. I changed this so the tests would complete in a reasonable amount of time. However, there is one other issue with testing that I worked around manually. After each test run, two databases (Users and Email) were left in the database. If I did not manually delete these then the number of failures on the next test run was different. This was really confusing until I figured it out because I was trying to make sure all the other testcases still passed with my patch, but even without the patch I was getting different results. -- 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

18 years

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-2298) Hibernate only uses info level on logger message to disencourage Hibernate Pool Manager. This should be a warning.

by Federico Chiesa (JIRA)

Hibernate only uses info level on logger message to disencourage Hibernate Pool Manager. This should be a warning. ------------------------------------------------------------------------------------------------------------------ Key: HHH-2298 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2298 Project: Hibernate3 Type: Improvement Components: core Environment: Hibernate 3.2.0, PostgreSQL 8.1.3, Windows. Reporter: Federico Chiesa Priority: Minor I usually work with Log4J set to WARN for Hibernate, and debug for my applications' log messages. I was testing some hibernate connection problems, and I enabled the INFO level for org.hibernate package. On a project I am testing, I got this message: INFO org.hibernate.connection.DriverManagerConnectionProvider - Using Hibernate built-in connection pool (not for production use!) Despite I knew that the connection pool of Hibernate is not for production use (because I read the documentation quite throughly), I believe that this should be a WARN level log message. This will help all novice users be warned by Hibernate itself about dangerous usage of the connection pool that might be overlooked when reading the documentation. -- 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

18 years

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1233) Allow mixing <union-subclass>and <subclass>

by Wouter Lievens (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1233?page=c... ] Wouter Lievens commented on HHH-1233: ------------------------------------- I would very much like to see this implemented. I'm using a single-root class hierarchy with almost a hundred domain classes in the tree. Some of these classess only contribute their change in type, and have few or no properties at all. Such a subtree could be collapsed into a single-class hierarchy if it were allowed. This will require a change to the DTD, and to the code as well. > Allow mixing <union-subclass>and <subclass> > ------------------------------------------- > > Key: HHH-1233 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1233 > Project: Hibernate3 > Type: Improvement > Components: core > Environment: N/A > Reporter: Gunther Schadow > > > BACKGROUND: > Hibernate allows mixing <subclass> and <joined-subclass> inheritance mappings but apparently not <subclass> and <union-subclass> mappings, however, this seems like the most useful combination. Example: > USE CASE: > We may have a hierarchy with very unevenly distributed mass, i.e., some subclasses have millions of objects, others have only a half-dozen. There may be a lot of different subclasses of the smaller sort. > Union-subclass seems ideal to work with a dozen different humongous tables, as they can be placed on different tablespaces and managed differently. However, for the 200 or so subclasses whith only a dozen objects each, it would be easier to map these into a single table per sub-hierarchy. > REQUESTED FEATURE: > Therefore it seems fair to suggest that <subclass> mappings should be supported underneath <union-subclass> mappings. To allow that the <discriminator> element would have to be handled inside a <union-subclass> element and same for the discriminator-value attribute. Perhaps one could limit the complexity by requiring that the outer mapping must be union-subclass and the inner can be subclass but not vica versa? > WORKAROUNDS: > As the documentation mentions one could just create several independent <class> hierarchies, thus effectively emulating the first level of union-subclass specializations. But that would not allow specifying polymorphic associations. > ESTIMATED EFFORT: > It could be difficult to implement support for this. But would like to know whether this is something that is somewhere on the radar screen for the future. -- 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

18 years

1
0
0 / 0

[Hibernate-JIRA] Created: (HBX-835) HibernateException when configuration file is missing

by Mike haller (JIRA)

HibernateException when configuration file is missing ----------------------------------------------------- Key: HBX-835 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-835 Project: Hibernate Tools Type: Bug Versions: 3.2beta9 Reporter: Mike haller Priority: Minor 1) Add configuration 2) Slect existing Java project 3) Do not specify hibernate configuration (Wizard does not complain) 4) Click finish 5) Open created configuration Error Tue Dec 05 12:53:09 CET 2006 org.hibernate.HibernateException: /hibernate.cfg.xml not found org.hibernate.HibernateException: /hibernate.cfg.xml not found at org.hibernate.util.ConfigHelper.getResourceAsStream(ConfigHelper.java:147) at org.hibernate.cfg.Configuration.getConfigurationInputStream(Configuration.java:1405) at org.hibernate.cfg.Configuration.configure(Configuration.java:1427) at org.hibernate.cfg.Configuration.configure(Configuration.java:1414) at org.hibernate.console.ConsoleConfiguration.loadConfigurationXML(ConsoleConfiguration.java:256) at org.hibernate.console.ConsoleConfiguration.configureStandardConfiguration(ConsoleConfiguration.java:479) at org.hibernate.console.ConsoleConfiguration.buildConfiguration(ConsoleConfiguration.java:460) at org.hibernate.console.ConsoleConfiguration.access$0(ConsoleConfiguration.java:441) at org.hibernate.console.ConsoleConfiguration$1.execute(ConsoleConfiguration.java:166) at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:56) at org.hibernate.console.ConsoleConfiguration.buildWith(ConsoleConfiguration.java:158) at org.hibernate.console.ConsoleConfiguration.build(ConsoleConfiguration.java:110) at org.hibernate.eclipse.console.workbench.ConsoleConfigurationWorkbenchAdapter.getChildren(ConsoleConfigurationWorkbenchAdapter.java:38) at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.getChildren(BasicWorkbenchAdapter.java:88) at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:94) at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:207) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58) -- 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

18 years

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 December 2006