April 2009 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HV-139) BeanMetaDataCache and ConstraintValidatorDefinitionsCache should not be static

by Hardy Ferentschik (JIRA)

BeanMetaDataCache and ConstraintValidatorDefinitionsCache should not be static ------------------------------------------------------------------------------- Key: HV-139 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-139 Project: Hibernate Validator Issue Type: Bug Affects Versions: 4.0.0.Alpha3 Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 4.0.0.Beta1 Also look at the static fields in ConfigurationImpl -- 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

15 years, 1 month

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3148) Exception thrown by debug trace code: ComponentType toLoggableString

by Pete Geraghty (JIRA)

Exception thrown by debug trace code: ComponentType toLoggableString -------------------------------------------------------------------- Key: HHH-3148 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3148 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.6 Environment: Hibernate 3.2.6.ga HibernateAnnotations 3.3.0.ga Oracle 10g Express Edition Reporter: Pete Geraghty Priority: Minor Attachments: ToLoggableStringExample.txt The method toLoggableString in ComponentType is used to provide tracing output when running with log level DEBUG. In some circumstances it throws a ClassCastException. This is not a good idea in tracing code and obscures underlying problems. In my case the underlying problem was a previous incorrect call to set a parameter value in a query. I saw that previous JIRA issues have mentioned this ClassCastException as a side effect of other underlying problems - it is a distraction and time-waster. Lines 375-378 read: EntityMode entityMode = tuplizerMapping.guessEntityMode( value ); if ( entityMode == null ) { throw new ClassCastException( value.getClass().getName() ); } A better solution would be to just us String.valueOf EntityMode entityMode = tuplizerMapping.guessEntityMode( value ); if ( entityMode == null ) { return String.valueOf(value); } Another possibility would be to concatenate some diagnostic message with String.valueOf, but personally I don't think that be helpful. Stack trace is: Exception in thread "main" java.lang.ClassCastException: java.lang.String at org.hibernate.type.ComponentType.toLoggableString(ComponentType.java:377) at org.hibernate.pretty.Printer.toString(Printer.java:76) at org.hibernate.engine.QueryParameters.traceParameters(QueryParameters.java:277) at org.hibernate.engine.query.HQLQueryPlan.performIterate(HQLQueryPlan.java:210) at org.hibernate.impl.SessionImpl.iterate(SessionImpl.java:1192) at org.hibernate.impl.QueryImpl.iterate(QueryImpl.java:46) at hib.example.EntityWithEmbeddable.main(EntityWithEmbeddable.java:44) Example code for the classes and schema to reproduce is pasted into the attachment. -- 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

15 years, 1 month

5
5
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-359) Fix usage of deprecated Hibernate commons-annotations methods

by Sanne Grinovero (JIRA)

Fix usage of deprecated Hibernate commons-annotations methods ------------------------------------------------------------- Key: HSEARCH-359 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-359 Project: Hibernate Search Issue Type: Task Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 3.2.0 org.hibernate.annotations.common.util.ReflectHelper moved to org.hibernate.util.ReflectHelper and org.hibernate.annotations.common.util.StringHelper moved to org.hibernate.util.StringHelper maybe others -- 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

15 years, 1 month

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3859) Correction: Hibernate Reference Documentation 3.3.1 (pdf).

by G Prathamesh (JIRA)

Correction: Hibernate Reference Documentation 3.3.1 (pdf). ---------------------------------------------------------- Key: HHH-3859 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3859 Project: Hibernate Core Issue Type: Bug Components: documentation Affects Versions: 3.3.1 Environment: Hibernate Reference Documentation 3.3.1 pdf format. Reporter: G Prathamesh Priority: Minor Dear Team, There are overlappings of contents, making difficult to read/print, in Hibernate Reference Documentation 3.3.1 (online downloadable pdf copy http://www.hibernate.org/22.html#A5) at: 1. Pg50 (3.4. Optional Configuration properties) 2. Pg165 (Table 9.1. Features of inheritance mappings) Note: w.r.t http://forum.hibernate.org/viewtopic.php?t=996340 -- 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

15 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] Created: (HV-112) Map constraints using XML

by Hardy Ferentschik (JIRA)

Map constraints using XML ------------------------- Key: HV-112 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-112 Project: Hibernate Validator Issue Type: Task Components: engine Reporter: Hardy Ferentschik Fix For: 4.0.0.Beta1 -- 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

15 years, 1 month

1
2
0 / 0

[Hibernate-JIRA] Commented: (HHH-1936) IdentityGenerator doesn't support BigInteger as a valid identity type.

by Michel Nolard (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1936?page=c... ] Michel Nolard commented on HHH-1936: ------------------------------------ Maybe nobody noticed it yet but this issue is nearly 3 years old ! It needs to be tackled down in an elegant and quick way for it appears in a very common use case : when using DBMS native ID systems E.g: using Oracle, one creates a table whose ID is a value generated from a sequence -> the bug occurs E.g: using Sybase, one creates a table whose ID is an auto-incremented value -> the bug occurs E.g: using SQL Server, one creates a table whose ID is an auto-incremented value -> the bug occurs ... the complete list is quite long. I think 3 years for this simple thing is quite long... don't you think ? Instead of adding the "not so JDBC standard compliant" implementation in the main IdentifierGeneratorFactory ( which is bad and I understand it), there should at least be an optional not fully compliant (but USEFUL) implementation providing the following seamless mappings: Oracle's NUMBER( p, 0 ) -> BigInteger Sybase-SqlServer's auto-increment -> BigInteger Thanks by advance, Michel Nolard > IdentityGenerator doesn't support BigInteger as a valid identity type. > ---------------------------------------------------------------------- > > Key: HHH-1936 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1936 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.0.5 > Environment: Hibernate 3.0.5, Sybase 12.05, Window/ Unix > Reporter: Leonid Shtivelman > Attachments: IdentifierGeneratorFactory.java > > > Identity generator strategy doesn't support BigInteger as a valid id type. This causes problem with Sybase which requires identity column to be numeric. It would seem an obvious way to get around this problem is to set column mapping to long in hibernate xml and the actual java object. This will solve obvious problem of creating identity, but will cause performance problem on selection. In order for Sybase to use index for parameter query the variable type of the parameter and column index type has to be the same. If ones maps column type to Long, Hibernate will use JDBC method setLong(long) to set value in the prepared statement. This will cause mismatch between parameter type and column index type, and Sybase will not use index to locate index. As you can see this is a big problem for anyone that is using identity columns Sybase and Hibernate -- 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

15 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-817) Aggregate projection aliases should not be applied to where-clause

by Serge P. Nekoval (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-817?page=co... ] Serge P. Nekoval commented on HHH-817: -------------------------------------- I agree. Its almost 4 years open and still Minor. We've added lots of weird workarounds like SQL groupings, but it seems that Hibernate team keeps ignoring anything related to Criterias. Are criterias dead? > Aggregate projection aliases should not be applied to where-clause > ------------------------------------------------------------------ > > Key: HHH-817 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-817 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.0.5 > Environment: Oracle 9.2.0.6, Hibernate 3.0.5, Spring Framework 1.2.2 based application working on Jakarta Tomcat 5.0.28 > Reporter: Michal Jastak > Priority: Minor > Attachments: HHH-817.patch > > > following java code: > protected Entity loadEntityLightweight(Serializable entityId) throws DataAccessException { > Criteria criteria = getSession().createCriteria(Entity.class); > ProjectionList projectionList = Projections.projectionList(); > projectionList.add(Property.forName(BaseEntity.PROP_ID), BaseEntity.PROP_ID); > projectionList.add(Property.forName(BaseEntity.PROP_TYPE), BaseEntity.PROP_TYPE); > criteria.setProjection(projectionList); > criteria.add(Restrictions.eq(BaseEntity.PROP_ID, entityId)); > criteria.setResultTransformer(new AliasToBeanResultTransformer(Entity.class)); > return (Entity) criteria.uniqueResult(); > } > generates following SQL query: > select this_.id as y0_, this_.type as y1_ from entities this_ left outer join facilities this_1_ on this_.id=this_1_.id left outer join users this_2_ on this_.id=this_2_.id left outer join addresses address2_ on this_.address_id=address2_.id left outer join entities entity3_ on this_2_.employer_id=entity3_.id left outer join facilities entity3_1_ on entity3_.id=entity3_1_.id left outer join users entity3_2_ on entity3_.id=entity3_2_.id where y0_=? > y0_ = ? expression in where clause is causing a 904 error on Oracle 9: > ORA-00904: "Y0_": invalid identifier > hibernate dialect: org.hibernate.dialect.Oracle9Dialect > mapping for Entity class: > <?xml version="1.0"?> > <!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD 3.0//EN" > "http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd"> > <hibernate-mapping default-lazy="false" default-cascade="save-update"> > > <class name="Entity" table="entities" mutable="true"> > <id name="id" type="java.lang.Long" unsaved-value="null"> > <generator class="sequence"> > <param name="sequence">entities_id_seq</param> > </generator> > </id> > <many-to-one name="address" class="Address" column="address_id" /> > ... >  > <joined-subclass name="Facility" table="facilities"> > <key column="id" /> > ... > <set name="users" inverse="true" lazy="true"> > <key column="facility_id" /> > <one-to-many class="User" /> > </set> > </joined-subclass> >  > <joined-subclass name="User" table="users" dynamic-insert="true" dynamic-update="true"> > <key column="id" /> > <many-to-one name="employer" class="Entity" column="employer_id" cascade="none" /> > ... > <set name="userAuthorities" inverse="true" cascade="all-delete-orphan"> > <key column="user_id" /> > <one-to-many class="Authority" /> > </set> > </joined-subclass> > </class> > </hibernate-mapping> -- 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

15 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-347) Adding a blackhole backend

by Sanne Grinovero (JIRA)

Adding a blackhole backend -------------------------- Key: HSEARCH-347 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-347 Project: Hibernate Search Issue Type: New Feature Components: engine Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 3.1.1 Add a new backend (can be configured to replace the jms or lucene backends) called "blackhole" as the same named MySQL engine. It doesn't to anything, basically it sends all changes to index to /dev/null. Should be useful to set indexing parameters and identifying performance bottlenecks. -- 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

15 years, 1 month

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3785) HQL parser not throwing error for unmatched parantheses

by Amaresh wakkar (JIRA)

HQL parser not throwing error for unmatched parantheses ------------------------------------------------------- Key: HHH-3785 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3785 Project: Hibernate Core Issue Type: Bug Components: query-hql Affects Versions: 3.2.6 Environment: Hibernate 3.2.6, Sybase ASE 12, Windows XP SP2 Reporter: Amaresh wakkar I have following query which I would have expected HQL parser to throw QuerySyntaxException:unexpected token. ================================ from WebAuditLog wal where wal.tmstampLastModified >= convert(date, '18-FEB-09', 111) and wal.tmstampLastModified <= convert(date, '18-FEB-09', 111)) and wal.sourceId = 'I' order by wal.client.clientId, wal.tmstampLastModified ==================================== The problem with this query is that on Line#2, there is a redundant unmatched right parantheses i.e. ')' . Ideally this should have been reported as Query syntax exception by HQL parser. Unfortunately, what HQL parses does is 1. ignores everything beyond that errorneous right parantheses 2. Executes such terminated query and returns results which gives impression to user that query is syntactically valid and errors must be either with data or logic of query. Workaround: In absensce of HQL parses throwing error, we must ensure that the HQL is correctly written by reviewing it carefully. Steps to replicate: 1.Create any table which has 2 or 3 columns 2. Try writing a HQL which uses parantheses e.g. functions like convert etc. Add an extra right parantheses at the end of such function's closing right parantheses 3. add additional where clause filtering criteria after step-2 4. Execute the query. 5. In the result you would notice that the where clause criteria mentioned in step-3 is ignored and query is executed as if the query terminated at step-2 I have done a quick search through existing bugs but couldn't find any matching right away so reporting it here. Hope it helps to make Hibernate HQL parser even more robust Thanks and regards, Amaresh Wakkar -- 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

15 years, 1 month

3
2
0 / 0

[Hibernate-JIRA] Commented: (HHH-817) Aggregate projection aliases should not be applied to where-clause

by David (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-817?page=co... ] David commented on HHH-817: --------------------------- this bug is especially potent because it's the recommended technique for avoiding lazy-loaded properties! http://www.hibernate.org/hib_docs/reference/en/html/performance.html " A different (better?) way to avoid unnecessary column reads, at least for read-only transactions is to use the projection features of HQL or Criteria queries. This avoids the need for buildtime bytecode processing and is certainly a preferred solution. " If lazy-loading is the most requested feature, like the documentation says, and if people are expected to use the ProjectionList behavior in criteria searches to avoid loading their blobs, etc... It's crazy this hasn't been fixed. For everything that hibernate does, I'm really surprised someone hasn't addressed this massively basic use case. I shouldn't have to create two tables and two classes because of one simple column. > Aggregate projection aliases should not be applied to where-clause > ------------------------------------------------------------------ > > Key: HHH-817 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-817 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.0.5 > Environment: Oracle 9.2.0.6, Hibernate 3.0.5, Spring Framework 1.2.2 based application working on Jakarta Tomcat 5.0.28 > Reporter: Michal Jastak > Priority: Minor > Attachments: HHH-817.patch > > > following java code: > protected Entity loadEntityLightweight(Serializable entityId) throws DataAccessException { > Criteria criteria = getSession().createCriteria(Entity.class); > ProjectionList projectionList = Projections.projectionList(); > projectionList.add(Property.forName(BaseEntity.PROP_ID), BaseEntity.PROP_ID); > projectionList.add(Property.forName(BaseEntity.PROP_TYPE), BaseEntity.PROP_TYPE); > criteria.setProjection(projectionList); > criteria.add(Restrictions.eq(BaseEntity.PROP_ID, entityId)); > criteria.setResultTransformer(new AliasToBeanResultTransformer(Entity.class)); > return (Entity) criteria.uniqueResult(); > } > generates following SQL query: > select this_.id as y0_, this_.type as y1_ from entities this_ left outer join facilities this_1_ on this_.id=this_1_.id left outer join users this_2_ on this_.id=this_2_.id left outer join addresses address2_ on this_.address_id=address2_.id left outer join entities entity3_ on this_2_.employer_id=entity3_.id left outer join facilities entity3_1_ on entity3_.id=entity3_1_.id left outer join users entity3_2_ on entity3_.id=entity3_2_.id where y0_=? > y0_ = ? expression in where clause is causing a 904 error on Oracle 9: > ORA-00904: "Y0_": invalid identifier > hibernate dialect: org.hibernate.dialect.Oracle9Dialect > mapping for Entity class: > <?xml version="1.0"?> > <!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD 3.0//EN" > "http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd"> > <hibernate-mapping default-lazy="false" default-cascade="save-update"> > > <class name="Entity" table="entities" mutable="true"> > <id name="id" type="java.lang.Long" unsaved-value="null"> > <generator class="sequence"> > <param name="sequence">entities_id_seq</param> > </generator> > </id> > <many-to-one name="address" class="Address" column="address_id" /> > ... >  > <joined-subclass name="Facility" table="facilities"> > <key column="id" /> > ... > <set name="users" inverse="true" lazy="true"> > <key column="facility_id" /> > <one-to-many class="User" /> > </set> > </joined-subclass> >  > <joined-subclass name="User" table="users" dynamic-insert="true" dynamic-update="true"> > <key column="id" /> > <many-to-one name="employer" class="Entity" column="employer_id" cascade="none" /> > ... > <set name="userAuthorities" inverse="true" cascade="all-delete-orphan"> > <key column="user_id" /> > <one-to-many class="Authority" /> > </set> > </joined-subclass> > </class> > </hibernate-mapping> -- 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

15 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues April 2009