January 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-5569) Hibernate should not use LONG type for Oracle

by Mindaugas Žakšauskas (JIRA)

Hibernate should not use LONG type for Oracle --------------------------------------------- Key: HHH-5569 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5569 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0.Beta-1 Environment: 3.5.0.Beta-1, Oracle 9i Reporter: Mindaugas Žakšauskas This is a spin-off from http://stackoverflow.com/questions/3719905/why-has-hibernate-switched-to-.... With the changes introduced in HHH-3892 Hibernate started to use Oracle LONG type instead of CLOB for properties of type="text". This is a bad idea because of the following: * it creates huge amount of pain for people who depend on Hibernate automatically creating table structure for them. Tables created with the same mapping will have different structure than tables created with earlier version of Hibernate * Oracle LONG type has a limitation: there can be _only one_ column of this type within a single table; * Oracle has deprecated LONG type many years ago and advised against using this type ever since 8i. See http://www.orafaq.com/wiki/LONG. Defining a property to have type="clob" is not really a solution; other databases might have other, more suitable types to store this type of data (not necessarily CLOB). At the moment the only workaround is to define custom dialact and use it; but this is a very poor solution in the long term. -- 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

14 years, 1 month

3
5
0 / 0

[Hibernate-JIRA] Created: (HHH-5885) Hibernate not insert re-attached collection

by Ed Bras (JIRA)

Hibernate not insert re-attached collection ------------------------------------------- Key: HHH-5885 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5885 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.6.0 Reporter: Ed Bras See the forum post: https://forum.hibernate.org/viewtopic.php?f=1&t=1009281&start=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

14 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5883) @Lob annotated field throws MappingException

by Jaroslaw Kijanowski (JIRA)

@Lob annotated field throws MappingException -------------------------------------------- Key: HHH-5883 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5883 Project: Hibernate Core Issue Type: Bug Components: envers Affects Versions: 3.6.0 Reporter: Jaroslaw Kijanowski I have a field annotated with @Lob and get: [hibernatetool] org.hibernate.MappingException: Type not supported for auditing: org.hibernate.type.SerializableToBlobType, on entity org.test.MyEntityClass, property 'myField'. -- 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

14 years, 1 month

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-5881) Add getter for "namedParameters" to QueryKey

by Nikita Koksharov (JIRA)

Add getter for "namedParameters" to QueryKey -------------------------------------------- Key: HHH-5881 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5881 Project: Hibernate Core Issue Type: Improvement Components: core Affects Versions: 3.6.0 Reporter: Nikita Koksharov Priority: Critical Attachments: QueryKey.patch I has introduced some useful mechanism in hibernate cache system in my project, that's why i need getter for "namedParameters" in org.hibernate.cache.QueryKey class. -- 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

14 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] Created: (HV-418) The annotation processor shouldn't report @Past/@Future given at Joda types as errors

by Gunnar Morling (JIRA)

The annotation processor shouldn't report @Past/@Future given at Joda types as errors ------------------------------------------------------------------------------------- Key: HV-418 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-418 Project: Hibernate Validator Issue Type: Bug Components: annotation-processor Reporter: Gunnar Morling Fix For: 4.2.0.Beta2 While HV core supports @Past/@Future at types from the Joda time API with 4.2, this is not yet the case for the annotation processor, resulting in wrong compiler errors, when the annotations are specified at one of the Joda 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

14 years, 1 month

1
3
0 / 0

[Hibernate-JIRA] Created: (JPA-11) @Lob annotation applies to both key and value of Map

by Panayiotis Karabassis (JIRA)

@Lob annotation applies to both key and value of Map ---------------------------------------------------- Key: JPA-11 URL: http://opensource.atlassian.com/projects/hibernate/browse/JPA-11 Project: Java Persistence API Issue Type: Bug Environment: Hibermate 3.6.0.Final MySQL Reporter: Panayiotis Karabassis When using the @Lob annotation on a java.util.Map I find that both the value and key of the Map are mapped to a BLOB. This is in violation of the JPA 2.0 specification which states: {quote}The Lob annotation may be used in conjunction with the Basic annotation or with the ElementCollection[100] annotation when the element collection value is of basic type. ... [100] If the element collection is a Map, this applies to the map value.{quote} To reproduce: {quote}@Entity public class Entry { @Id @GeneratedValue private long identifier; @ElementCollection @Column(nullable = false) private Map<String, String> titles; @ElementCollection @Column(nullable = false) @Lob private Map<String, String> contents; // Getters and setters, other fields and methods }{quote} This produces the following error during schema creation: {quote}Unsuccessful: create table myblog.Entry_contents (Entry_identifier bigint not null, contents longtext not null, contents_KEY longtext, primary key (Entry_identifier, contents_KEY)) type=InnoDB BLOB/TEXT column 'contents_KEY' used in key specification without a key length{quote} Workarounds include defining column type with @MapKeyColumn(columnDefinition = "...") or using @Embeddable as a wrapper for values. (thanks to axtavt and Sean Patrick Floyd) -- 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

14 years, 1 month

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-5870) Cache invalidation bug: createSQLQuery(String sql) creates SQLQueryImpl with null querySpaces, making UpdateTimestampsCache:isUpToDate always return true

by nodje (JIRA)

Cache invalidation bug: createSQLQuery(String sql) creates SQLQueryImpl with null querySpaces, making UpdateTimestampsCache:isUpToDate always return true --------------------------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-5870 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5870 Project: Hibernate Core Issue Type: Bug Components: caching (L2) Affects Versions: 3.6.0 Environment: OS X 10.6.6 - Java 1.6.0_22 Reporter: nodje Priority: Blocker While investigating a regression seemingly caused by cache problem on an application, I stumbled upon UpdateTimestampsCache:89 method public synchronized boolean isUpToDate(Set spaces, Long timestamp) throws HibernateException always returning true when parameter spaces Set empty. This is the cause of my regression: QueryCache gets hit even though returned entities have been updated after the query fired first time. While trying to understand what caused Set spaces to be empty - which to me is the cause of the error - I realized it is just created like that in SQLQueryImpl:138. SQLQueryImpl(String sql, SessionImplementor session, ParameterMetadata parameterMetadata) { super( sql, null, session, parameterMetadata ); queryReturns = new ArrayList<NativeSQLQueryReturn>(); querySpaces = null; callable = false; } While there's probably a way to specify querySpaces (I can only trace it to using addSynchronizedQuerySpace in SQLQuery - which is not referenced in the doc), I believe everybody expect a default behavior, i-e a default querySpace to work with, so that isUpToDate check can work properly. -- 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

14 years, 1 month

2
7
0 / 0

[Hibernate-JIRA] Created: (HHH-5810) Database MYSQL supports recursive but populate doesn't work

by Raul Romanillos Llorente (JIRA)

Database MYSQL supports recursive but populate doesn't work ----------------------------------------------------------- Key: HHH-5810 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5810 Project: Hibernate Core Issue Type: Task Components: query-sql Affects Versions: 3.3.0.GA Environment: Hibernate 3.3.0 GA, MySQL 5.1.41 Reporter: Raul Romanillos Llorente After running on the screen we see that the field_3 field_1 fields have the same value. Hibernate has the same value assigned to the fields valueField_1, valueField_2 and valueField_3 and the database are different values. Hibernate did not return good results with createSQLQuery (query). ... String query = "SELECT i.id_route, i.route_name, ii.route_name, iii.route_name,"; query += " FROM routes i"; query += " LEFT JOIN routes ii ON i.id_route_parent=i.id_route"; query += " LEFT JOIN routes iii ON ii.id_route_parent=iii.id_route tx = session.getTransaction(); tx.begin(); result = session.createSQLQuery(query).list(); tx.commit();"; String valueField_0, valueField_1, valueField_2, valueField_3; if (result!=null) { for (Object obj: result) { Object [] cols= (Object []) irObj; valueField_0=(cols[0]!=null?cols[0].toString():""); valueField_1=(cols[1]!=null?cols[1].toString():""); valueField_2=(cols[2]!=null?cols[2].toString():""); valueField_3=(cols[3]!=null?cols[3].toString():""); System.out.println("field_1:"+valueField_1+"\nfield_2:"+valueField_2+"\nfield_3:"+valueField_3); } } -- 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

14 years, 1 month

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5878) Add ability to mark keywords as protected dynamically to prevent table aliasing when using @Formula

by Ian Simpson (JIRA)

Add ability to mark keywords as protected dynamically to prevent table aliasing when using @Formula --------------------------------------------------------------------------------------------------- Key: HHH-5878 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5878 Project: Hibernate Core Issue Type: New Feature Components: annotations, core Affects Versions: 3.2.5 Environment: 3.2.5.ga/Oracle 11g database Reporter: Ian Simpson Using the following in a @Formula does not work due to keywords being aliased to the entity the formula is part of: {code} @Formula("(select count(1) from sometable st " + "where st.othertable_id in ( " + "select distinct id from othertable ot " + "start with ot.id = id " + "connect by nocycle prior ot.id = ot.parent_id " + "))" ) {code} The end result is: {code} (SELECT COUNT(1) FROM sometable st AND st.othertable_id IN ( SELECT DISTINCT otherta0_.id FROM othertable ot otherta0_.start otherta0_.with cc.id = otherta0_.id otherta0_.connect BY otherta0_.nocycle otherta0_.prior cc.id = cc.parent_id ) ) {code} What (I think) might be preferable is being able to indicate that certain parts are keywords and that they shouldn't be aliased. The inverse is already doable by adding backticks to a field/table/whatever that does match a protected keyword. For example: {code} @Formula("(select count(1) from sometable st " + "where st.othertable_id in ( " + "select distinct id from othertable ot " + "!!start !!with ot.id = id " + "!!connect by nocycle !!prior ot.id = ot.parent_id " + "))" ) {code} ... or something of that nature which Hibernate can seek out a know to process differently. I have no idea if "!!" would be usable, but I think you get what I'm saying. -- 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

14 years, 1 month

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5875) @OnDelete available also on @ManyToMany relationships

by Zdenek Hrib (JIRA)

@OnDelete available also on @ManyToMany relationships ----------------------------------------------------- Key: HHH-5875 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5875 Project: Hibernate Core Issue Type: Improvement Components: annotations Affects Versions: 3.6.0 Reporter: Zdenek Hrib When using @ManyToMany annotation and it creates a mapping table (eg. ACCOUNTS, PERSONS, ACOUNTS_PERSONS) it is not possible to mark the field with @OnDelete(action=OnDeleteAction.CASCADE). Therefore both foreign key contraints on the mapping table are created as "ON UPDATE NO ACTION ON DELETE NO ACTION". It would be great to use the @OnDelete(action=OnDeleteAction.CASCADE) to change it to "ON UPDATE NO ACTION ON DELETE CASCADE". If I comment out the following lines line in org\hibernate\mapping\Collection.java then one of the two FK contraints could be created as "ON UPDATE NO ACTION ON DELETE CASCADE" by using @OnDelete(action=OnDeleteAction.CASCADE), but still I cannot change it on the second FK constraint. public void validate(Mapping mapping) throws MappingException { // if ( getKey().isCascadeDeleteEnabled() && ( !isInverse() || !(isOneToMany()) ) ) { // throw new MappingException( // "only inverse one-to-many associations may use on-delete=\"cascade\": " // + getRole() ); // } I had attached the example source. -- 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

14 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues January 2011