July 2007 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (ANN-634) @CollectionOfElements cannot be combined with @Filter or @Where

by Emmanuel Bernard (JIRA)

@CollectionOfElements cannot be combined with @Filter or @Where --------------------------------------------------------------- Key: ANN-634 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-634 Project: Hibernate Annotations Issue Type: Bug Components: binder Affects Versions: 3.3.0.ga Reporter: Emmanuel Bernard Assignee: Emmanuel Bernard Fix For: 3.3.1 Caused by: org.hibernate.MappingException: @ManyToMany or @CollectionOfElements defining filter or where without join fetching not valid within collection using join fetching[xxxx] at org.hibernate.cfg.annotations.CollectionBinder.checkFilterConditions(CollectionBinder.java:1249) at org.hibernate.cfg.annotations.CollectionBinder.bindManyToManySecondPass(CollectionBinder.java:1235) at org.hibernate.cfg.annotations.CollectionBinder.bindStarToManySecondPass(CollectionBinder.java:576) at org.hibernate.cfg.annotations.MapBinder$1.secondPass(MapBinder.java:79) at org.hibernate.cfg.CollectionSecondPass.doSecondPass(CollectionSecondPass.java:43) at org.hibernate.cfg.Configuration.secondPassCompile(Configuration.java:1130) at org.hibernate.cfg.AnnotationConfiguration.secondPassCompile(AnnotationConfiguration.java:316) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1286) at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:915) -- 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

1
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2722) incorrect sql on custom types when using dynamic update, optimistic-lock="dirty", select-before-update when null value in where clause

by Alex McCarrier (JIRA)

incorrect sql on custom types when using dynamic update, optimistic-lock="dirty", select-before-update when null value in where clause -------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-2722 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2722 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.2 Environment: hibernate 3.2.2, oracle 10g Reporter: Alex McCarrier Priority: Minor We are using optimistic-lock="dirty", dynamic-update="true" and select-before-update="true" on some of our classes. This seems to be isolated to cases where we are using custom types that implement the UserType interface. The SQL that is generated by hibernate for the PreparedStatement looks something like this: delete from TABLE_NAME where PK = :1 and SOME_NUMBER = :2 The problem happens when the value for SOME_NUMBER is null. It still tries to use the above sql, rather than using the correct: delete from TABLE_NAME where PK = :1 and SOME_NUMBER is null. In this case, SOME_NUMBER is defined in Oracle as a FLOAT, and in the mapped object as double. Interestingly, another one of our custom types which is a Binary type (Hibernate.BINARY.sqlType) has no problems. -- 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

1
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2730) Define TypeFactory as an interface that can be user defined

by David CLEMENT (JIRA)

Define TypeFactory as an interface that can be user defined ----------------------------------------------------------- Key: HHH-2730 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2730 Project: Hibernate3 Issue Type: New Feature Components: core Reporter: David CLEMENT Priority: Minor If it could be user defined, we could use our own default type implementations. We could also use user defined entity types. -- 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

1
0
0 / 0

[Hibernate-JIRA] Created: (HBX-963) make "generated by" statement optional (or remove it)

by Dan Allen (JIRA)

make "generated by" statement optional (or remove it) ----------------------------------------------------- Key: HBX-963 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-963 Project: Hibernate Tools Issue Type: Improvement Components: hbm2java Affects Versions: 3.2beta9, 3.2beta10 Reporter: Dan Allen Priority: Minor If you are using a version control system to manage the Java classes generated by the hbm2java task, then every single time you run the task, it will appear as if every single file has changed, even when there are no changes to the Java code. The reason this happens is because the Pojo.ftl template includes a "generated by" statement that inserts the current date and time. JAXB does this as well and it drives me insane! I would prefer we just take out the date and time. There just isn't a good reason to have it and the headaches that it causes are not worth it. I have included a patch to remove 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, 5 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-2729) Inserts get done even when flushmode == manual and they are not necessary

by Frits Jalvingh (JIRA)

Inserts get done even when flushmode == manual and they are not necessary ------------------------------------------------------------------------- Key: HHH-2729 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2729 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.3 Environment: Hibernate 3.2.3, HBEM 3.3.1, Tomcat 6.0.10, PostgresSQL 8.2, Seam 2.0.0B1 Reporter: Frits Jalvingh Attachments: hib.patch (See also http://jboss.com/index.html?module=bb&op=viewtopic&p=4064502#4064502) When the flushmode is manual (and in many other cases too) Hibernate should not do an insert when persist() gets called. The current code always forces an insert when a record is persist()ed with generated keys, even if the generator can be used without the insert. This causes trouble when an insert is used in seam's long running conversations (and when an entity is persisted while not all of it's fields have valid data - nullity etc). The problem is caused by a few problems in passing around a boolean requiresImmediateIdAccess) which gets set to true always in some calls. A fix which prevents Hibernate from doing the insert 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

17 years, 5 months

1
0
0 / 0

[Hibernate-JIRA] Created: (EJB-301) org.hibernate.criterion.Example.toSqlString()

by Nicholas Albion (JIRA)

org.hibernate.criterion.Example.toSqlString() --------------------------------------------- Key: EJB-301 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-301 Project: Hibernate Entity Manager Issue Type: Bug Components: Documentation Reporter: Nicholas Albion I'm trying to create a query by example, and hopefully adapt the SQL to include joins on non-HSQL columns. The documentation is confusing for org.hibernate.criterion.Example.toSqlString(Criteria criteria, CriteriaQuery criteriaQuery) I'm not sure how to obtain the CriteriaQuery parameter. Google only managed to find an unanswered forum posting asking the same question. The javadocs for CriteriaQuery only adds confusion to the matter: Interface CriteriaQuery: This interface is not used by application code. (http://www.hibernate.org/hib_docs/v3/api/org/hibernate/criterion/Criteria...) -- 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

3
3
0 / 0

[Hibernate-JIRA] Resolved: (HHH-1694) Documentation Outdated: "10.4.4. Queries in native SQL"

by Diego Pires Plentz (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1694?page=c... ] Diego Pires Plentz resolved HHH-1694. ------------------------------------- Resolution: Fixed > Documentation Outdated: "10.4.4. Queries in native SQL" > ------------------------------------------------------- > > Key: HHH-1694 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1694 > Project: Hibernate3 > Issue Type: Bug > Components: documentation > Affects Versions: 3.1.3 > Reporter: Gamigin > Assignee: Diego Pires Plentz > Priority: Minor > > // Trying code from Hibernate 3.1 docs (section 10.4.4) > List cats = session.createSQLQuery( > "SELECT {cat.*} FROM CAT {cat} WHERE ROWNUM<10", > "cat", > Cat.class > ).list(); > This doesn't compile. createSQLQuery takes only one string and there are no overloads. The JavaDoc (http://www.hibernate.org/hib_docs/v3/api/) agrees with the compiler. The documentation must be out of date. > Java 1.5.0_06 > Hibernate 3.1.2 -- 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

1
0
0 / 0

[Hibernate-JIRA] Assigned: (HHH-1694) Documentation Outdated: "10.4.4. Queries in native SQL"

by Diego Pires Plentz (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1694?page=c... ] Diego Pires Plentz reassigned HHH-1694: --------------------------------------- Assignee: Diego Pires Plentz > Documentation Outdated: "10.4.4. Queries in native SQL" > ------------------------------------------------------- > > Key: HHH-1694 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1694 > Project: Hibernate3 > Issue Type: Bug > Components: documentation > Affects Versions: 3.1.3 > Reporter: Gamigin > Assignee: Diego Pires Plentz > Priority: Minor > > // Trying code from Hibernate 3.1 docs (section 10.4.4) > List cats = session.createSQLQuery( > "SELECT {cat.*} FROM CAT {cat} WHERE ROWNUM<10", > "cat", > Cat.class > ).list(); > This doesn't compile. createSQLQuery takes only one string and there are no overloads. The JavaDoc (http://www.hibernate.org/hib_docs/v3/api/) agrees with the compiler. The documentation must be out of date. > Java 1.5.0_06 > Hibernate 3.1.2 -- 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

1
0
0 / 0

[Hibernate-JIRA] Created: (HBX-959) allow foreign key property name override

by Dan Allen (JIRA)

allow foreign key property name override ---------------------------------------- Key: HBX-959 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-959 Project: Hibernate Tools Issue Type: Improvement Components: hbm2java Affects Versions: 3.2beta9, 3.2beta10 Reporter: Dan Allen Priority: Minor Without any special settings, the hbm2java tool will assign the @ManyToOne property the same name as the target class. For instance, let's say you have an employee table. Each employee can have a manager, who is also an employee. The column name might be manager_id, but the hbm2java tool will name the property employee. In this case, it is desirable to override the name of the property to be manager instead of employee. Currently, there is no way to do this if foreign keys are active on the table. It IS possible if foreign keys are NOT defined on the table since then the foreign-key element in *.reveng.xml comes into play. The problem comes when you try to override the foreign-key, it just ends up created TWO @ManyToOne properties. What I am looking for (in hypothetical) is: <column name="manager_id" property="manager" /> Obviously, that syntax only works for basic types, not associations. There needs to be way to override the foreign-key settings WITHOUT creating a new foreign key relationship. The location in the code where the property name is decided is JDBCBinder#bindOutgoingForeignKeys() which then delegates to ReverseEngineeringStrategy#revengStrategy.foreignKeyToEntityName() -- 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
4
0 / 0

[Hibernate-JIRA] Created: (ANN-538) Give @IndexColumn a default name

by Sven Meier (JIRA)

Give @IndexColumn a default name -------------------------------- Key: ANN-538 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-538 Project: Hibernate Annotations Type: Improvement Versions: 3.2.1 Reporter: Sven Meier Priority: Minor It would be great, if the @IndexColumn annotation had a default 'name'. This would support users (e.g. me ;) in their effort to keep persistence annotations clear of database specifics. Additionally @IndexColumn is a rather often used annotation and it's tedious to repeat the same information (i.e. the 'name') over and over again. I'd propose 'hibernate_index', similar to the defaults in net.sf.hibernate.id.TableGenerator. Preferably this default would come from NamingStrategy, but I'm not sure how stable this interface is supposed to be. -- 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
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues July 2007