August 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (METAGEN-34) VTA-1710M2 cummins, engine V28 fittings cleaner, air 3021645

by cqcummins (JIRA)

VTA-1710M2 cummins,engine V28 fittings cleaner,air 3021645 ---------------------------------------------------------- Key: METAGEN-34 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-34 Project: Hibernate Metamodel Generator Issue Type: Bug Components: documentation Environment: CQ Kang cummins diesel engine parts Ltd. Reporter: cqcummins Assignee: Hardy Ferentschik Attachments: CQ Kang cummins diesel engine parts Ltd.ppt ESN: 25208148Application: Marinemarineboatpost boatbore-[in]: 5.5Stroke-[in]: 6bore&Stroke-[in]: 5.50x6.00Displacement-liter[in³]: 28 [1710]Cylinders: 12Fuel Pump: 3059773injector: noneHead,Cylinder: noneFlywheel housing: noneengine upper set:noneheater: nonefuel consumption--L/hr[g/hr]:noneengine length--mm[in]:noneengine width--mm[in]:noneengine height--mm[in]:noneengine LxWxH--(in):noneengine Weight--(kg):nonecleaner,air 3021645Model: VTA-1710M2Series: V28DATA: 1993standard oil pan capacity--[g]:none VTA-1710M2 cummins,engine V28 fittings cleaner,air 3021645 -- 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, 4 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5483) Better use of annotations for custom types

by Xavier Dury (JIRA)

Better use of annotations for custom types ------------------------------------------ Key: HHH-5483 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5483 Project: Hibernate Core Issue Type: Improvement Components: annotations Reporter: Xavier Dury Priority: Minor Better use of annotations for custom types. Allow org.hibernate.annotations.Type to be used on annotations like this: public interface AnnotationConfiguredType<A extends Annotation> { void configure(A configuration); } @Retention(RUNTIME) @Target({FIELD, METHOD}) @Type(type = "...CustomDateType") public @interface CustomDate { String pattern() default "yyyy-MM-dd"; boolean lenient() default true; ... } public class CustomDateType implements UserType, AnnotatedConfiguredType<CustomDate> { public void configure(CustomDate configuration) { ... } ... } @Entity public class MyEntity { @CustomDate(pattern = "dd/MM/yyyy") private Date date; ... } -- 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, 4 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5180) StandardQueryCache.get() does not handle EntityNotFoundException for natural key lookups

by Gail Badner (JIRA)

StandardQueryCache.get() does not handle EntityNotFoundException for natural key lookups ---------------------------------------------------------------------------------------- Key: HHH-5180 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5180 Project: Hibernate Core Issue Type: Bug Components: caching (L2), core Reporter: Gail Badner Assignee: Gail Badner Fix For: 3.6 This is the same as HHH-3478, except it's for 3.6. In 3.6 we can use JPA exceptions, so the fix will be different. -- 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, 4 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5393) @MapKey with embeddable value

by Harald Wellmann (JIRA)

@MapKey with embeddable value ----------------------------- Key: HHH-5393 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5393 Project: Hibernate Core Issue Type: Bug Components: annotations Affects Versions: 3.5.3 Environment: Hibernate 3.5.3, PostgreSQL 8.4.3 Reporter: Harald Wellmann Map<Basic, Embeddable> does not work, when the map key is a persistent field of the value. The map key shall not be represented as a separate table column, this is why the example uses @MapKey and not @MapKeyColumn. Example: {code:java} @Embeddable public class LocalizedString { private String language; private String text; } @Entity public class MultilingualString { @Id private long id; @ElementCollection(fetch=FetchType.EAGER) @MapKey(name = "language") @CollectionTable(schema = "jpa", name = "multilingual_string_map", joinColumns = @JoinColumn(name = "string_id")) private Map<String, LocalizedString> map = new HashMap<String, LocalizedString>(); } {code} Hibernate appears to expect an Entity as map value: org.hibernate.AnnotationException: Associated class not found: LocalizedString Detailed discussion of this use case: http://hwellmann.blogspot.com/2010/07/jpa-20-mapping-map.html -- 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, 4 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-5481) Consider promoting dynamic-map entity mode to standard feature

by Marko Topolnik (JIRA)

Consider promoting dynamic-map entity mode to standard feature -------------------------------------------------------------- Key: HHH-5481 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5481 Project: Hibernate Core Issue Type: Improvement Components: core Reporter: Marko Topolnik Priority: Minor I would like to put a good word in for the dynamic-map entity mode. From the amount of content available on the web discussing this feature it seems to me that few people use it -- and it's still experimental. Dynamic maps have a very important role when using Hibernate from dynamic JVM languages. I work for a company that uses Clojure as its primary language in enterprise-class software solutions. We have come to rely extensively on Hibernate for a number of its great features, database portability being for us perhaps the most important. It is a real pleasure to combine dynamic map entities with clojure maps. We can construct a complex, nested data structure using the Clojure map literal and save it to db, all in a single expression. Without dynamic maps, we would have to burden our projects with precompiled Java code and maintain that code as our data model evolves. This way, we only change the Hibernate mappings, which for us play the role of database schema definitions with no redundancies in other models. So far we have had no performance issues with dynamic map entity mode, quite to the contrary. We have successfully used them even for batch inserts that require one query per record to determine whether it should be inserted. Even on my development laptop I get over a thousand records processed per second. I hope this feature lives on and becomes a standard part of Hibernate. As the JVM world turns increasingly towards dynamic languages, it may yet gain some serious traction. -- 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, 4 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HV-355) RangeDef's min() and max() are just wrong

by Trond Valen (JIRA)

RangeDef's min() and max() are just wrong ----------------------------------------- Key: HV-355 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-355 Project: Hibernate Validator Issue Type: Bug Components: validators Affects Versions: 4.1.0.Final Environment: Hibernate 3.3.2.GA and Oracle XE 10.2.0 Reporter: Trond Valen Assignee: Hardy Ferentschik public RangeDef min(long min) { addParameter( "value", min ); return this; } public RangeDef max(long max) { addParameter( "value", max ); return this; } Do I need a test case for this? Shouldn't these methods run addParameter("min", min) and addParameter("max", max)? I got an exception with "Unknown parameters"... I made a MyRangeDef where I fixed this, and it was all good :) -- 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, 4 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5479) Upgrade jDocBook plugin to 2.3.0

by Steve Ebersole (JIRA)

Upgrade jDocBook plugin to 2.3.0 -------------------------------- Key: HHH-5479 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5479 Project: Hibernate Core Issue Type: Task Components: build Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.6.0.Beta3 Upgrade jDocBook plugin to 2.3.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, 4 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-5471) Not exception thrown when dealing with reserved words on Microsot SQL Server 2008

by Maximiliano Gomez Vidal (JIRA)

Not exception thrown when dealing with reserved words on Microsot SQL Server 2008 --------------------------------------------------------------------------------- Key: HHH-5471 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5471 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.2.1 Environment: Hibernate 3.2.1, Microsoft SQL Server 2008, jTDS JDBC Driver Reporter: Maximiliano Gomez Vidal I have an entity with the properties "user", "type" and "password", all being reserved words in SQL Server 2008. The exported schema shows the CREATE TABLE statement with the corresponding properties. However, the table is not created because of the use of the reserved word user (type and password are reserved but the creation is not aborted by them). I'll expect Hibernate to throw an exception as when using reserved words in other RDBMS like MySQL. Instead, it does not report any error and continues with the execution. -- 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, 4 months

2
1
0 / 0

[Hibernate-JIRA] Updated: (HHH-1643) Sub-query as function parameter - either sub-query is missed from SQL or NullPointerException raised

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1643?page=c... ] Steve Ebersole updated HHH-1643: -------------------------------- Assignee: Steve Ebersole Fix Version/s: 3.6.0.Beta3 3.5.5 > Sub-query as function parameter - either sub-query is missed from SQL or NullPointerException raised > ---------------------------------------------------------------------------------------------------- > > Key: HHH-1643 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1643 > Project: Hibernate Core > Issue Type: Bug > Components: query-hql > Affects Versions: 3.1.2, 3.1.3 > Environment: Hibernate 3.1.2 MS SQL Server 2K > Reporter: Andy Shelton > Assignee: Steve Ebersole > Fix For: 3.5.5, 3.6.0.Beta3 > > Attachments: hql-sql.patch > > > The HQL grammar HQL (hql.g) allows expressions and sub-queries as parameters to functions, however the SQL Tree Transform grammar (hql-sql.g) does not, it only allows expressions. This means if you pass a sub-query as a parameter to something like "cast" for example, you will get a NullPointerException. In other cases, typically the sub-query is missed out of the resulting SQL. This is easily remedied by changing the first line of the definition of functionCall within hql-sql.g from: > functionCall > : #(METHOD_CALL {inFunctionCall=true;} pathAsIdent ( #(EXPR_LIST (expr)* ) )? ) > to: > functionCall > : #(METHOD_CALL {inFunctionCall=true;} pathAsIdent ( #(EXPR_LIST (exprOrSubquery)* ) )? ) > This modification has been tested against all the existing UnitTests in Hibernate 3.1.2 and does not cause any problems. > I've included a patch for this. -- 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, 4 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5426) HQL update/delete does not invalidate the query cache

by Emond Papegaaij (JIRA)

HQL update/delete does not invalidate the query cache ----------------------------------------------------- Key: HHH-5426 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5426 Project: Hibernate Core Issue Type: Bug Components: caching (L2) Affects Versions: 3.5.4 Reporter: Emond Papegaaij Attachments: QueryCacheTest.java Update/delete queries performed via HQL do not invalidate the query cache. For example, a 'delete from Item' does not invalidate a 'select count(*) from Item' query performed earlier. The attached test case can be added to QueryCacheTest (in the testsuite) to demonstrate the problem. -- 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, 4 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues August 2010