March 2007 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (ANN-551) @SQLInsert. Columns in sql comes in different order depending on the application server used

by Søren Pedersen (JIRA)

@SQLInsert. Columns in sql comes in different order depending on the application server used -------------------------------------------------------------------------------------------- Key: ANN-551 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-551 Project: Hibernate Annotations Type: Bug Components: binder Versions: 3.2.1 Environment: Hibernate-core 3.2.2, hibernate-annotations 3.2.1. WebLogic 9.2 and JBoss 4.0.5. Oracle 10. Reporter: Søren Pedersen Problem: The columns in the sql you specify in SQLInsert annotation has be ordered in the same way hibernate sorts its properties when constructing the insert sql. Example: When WebLogic 9.2 is used the sql should look like this: "insert into acount (name, address, country) values (?,?,?)" But when JBoss 4.0.5 is used the sql should look like this: "insert into acount (address, country, name) values (?,?,?)" The above are only examples. Consequence: I have to have different SQLInsert's for every JEE apllication server we support, because the properties comes in different order depending on the application server used. Suggested solution: In the method org.hibernate.cfg.AnnotationBinder.addElementsOfAClass(List<PropertyData> elements, PropertyHolder propertyHolder, boolean isPropertyAnnotated,String propertyAccessor, final XClass annotatedClass, ExtendedMappings mappings) This property list shown below should be sorted to make sure that the properties also come in the same order: List<XProperty> properties = annotatedClass.getDeclaredProperties( accessType ); -- 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

4
8
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

16 years, 3 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2457) UnsupportedOperationException with WebSphereExtendedJTATransactionLookup

by Erik Post (JIRA)

UnsupportedOperationException with WebSphereExtendedJTATransactionLookup ------------------------------------------------------------------------ Key: HHH-2457 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2457 Project: Hibernate3 Type: Bug Versions: 3.2.2 Reporter: Erik Post Using the WebSphereExtendedJTATransactionLookup as transaction manager lookup class results in an UnsupportedOperationException being thrown by WebSphereExtendedJTATransactionLookup$TransactionManagerAdapter.getStatus(). This method is called by JTATransactionFactory.isTransactionInProgress(). Would a solution be to have the TransactionManagerAdapter#getStatus method delegate to the TransactionAdapter#getStatus method? Also see http://forum.hibernate.org/viewtopic.php?t=966463 -- 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

11
13
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

16 years, 3 months

2
1
0 / 0

[Hibernate-JIRA] Created: (ANN-591) SchemaExport throws ConcurrentModificationException for entity containing list of lists

by Ivan O'Connor (JIRA)

SchemaExport throws ConcurrentModificationException for entity containing list of lists --------------------------------------------------------------------------------------- Key: ANN-591 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-591 Project: Hibernate Annotations Issue Type: Bug Components: binder Affects Versions: 3.2.1 Environment: Hibernate 3.2.1.GA, Oracle 10 Reporter: Ivan O'Connor Attachments: hbm2ddl.zip I have a class, let's call it A, that contains a List of class B. Each instance of B has a List of class C. I'm trying to generate the DDL for this, so I've annotated the code and run it through SchemaExport, which throws a ConcurrentModificationException. My environment: Java 1.5, Oracle 10, Hibernate 3.2.1ga. The problem seems to be caused by having an entity (A) containing an embedded collection (of B), each element of which contains a collection (of C). SchemaExport generates correct DDL when the annotations are modified to make B and/or C an entity, but not when they are both components. I realise this is considered something of an exotic case, but I'd like to know why the DDL doesn't generate. See bugReport.txt in attached zip for further details. -- 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

6
12
0 / 0

[Hibernate-JIRA] Created: (ANN-590) Table name problem

by Eddie Man (JIRA)

Table name problem ------------------ Key: ANN-590 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-590 Project: Hibernate Annotations Issue Type: Bug Components: binder Affects Versions: 3.2.1 Reporter: Eddie Man Priority: Critical Attachments: src.zip Problem: When I run the test.Main in the attachment, an mapping exception thrown while passing the annotation: Exception in thread "main" org.hibernate.MappingException: Unable to find column with logical name: customerID in ShoppingBasket at org.hibernate.cfg.Ejb3JoinColumn.checkReferencedColumnsType(Ejb3JoinColumn.java:383) at org.hibernate.cfg.BinderHelper.createSyntheticPropertyReference(BinderHelper.java:88) at org.hibernate.cfg.FkSecondPass.doSecondPass(FkSecondPass.java:63) at org.hibernate.cfg.AnnotationConfiguration.processFkSecondPassInOrder(AnnotationConfiguration.java:428) at org.hibernate.cfg.AnnotationConfiguration.secondPassCompile(AnnotationConfiguration.java:286) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1286) at test.Main.main(Main.java:19) But when I change the table name of ShoppingBaskets to "Basket", then the problem solved. -- 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

4
11
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, 4 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2384) Patch for using case-expression("case ... when ... end") in aggregate functions

by Florian Rock (JIRA)

Patch for using case-expression("case ... when ... end") in aggregate functions ------------------------------------------------------------------------------- Key: HHH-2384 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2384 Project: Hibernate3 Type: Patch Components: query-hql Versions: 3.2.2 Reporter: Florian Rock Priority: Minor Attachments: aggrcasehql.patch using a case-expression in aggregate functions causes a QuerySyntaxException.. ie.: "count(case when fubar > 0 then 1 else null end)" i changed some things in the grammar to solve this, patch is attached. -- 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

4
3
0 / 0

[Hibernate-JIRA] Created: (ANN-582) Joda User Types

by Martin Gilday (JIRA)

Joda User Types --------------- Key: ANN-582 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-582 Project: Hibernate Annotations Type: New Feature Versions: 3.2.1 Reporter: Martin Gilday Attachments: jodaUserTypes.zip As discussed on the forums http://forum.hibernate.org/viewtopic.php?t=972083 here are some user types for Joda Time. It covers LocalDate, LocalDateTime and LocalTime checked against Joda 1.4. Currently it has been used with MySql4.x. It relies on using date patterns for converting the joda objects and then setting them as Strings. This should work for any database that uses the same date/time formats. One possible improvement might be to convert to java.sql.Date etc and allow JDBC to handle the setting in the DB. Although I do not know how this would affect timezones, which was the reason for using LocalXxx. -- 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
2
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, 5 months

9
25
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues March 2007