March 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-3464) SimpleExpression.ignoreCase uses SQL server lowercase function for left part and JAVA lowercase function for right part of expression

by Vitaliy Tymchyshyn (JIRA)

SimpleExpression.ignoreCase uses SQL server lowercase function for left part and JAVA lowercase function for right part of expression ------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-3464 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3464 Project: Hibernate3 Issue Type: Bug Components: query-criteria Affects Versions: 3.2.6 Environment: tried with PostgreSQL Reporter: Vitaliy Tymchyshyn Priority: Minor When using SimpleExpression.ignoreCase (e.g. Restrictions.eq().ignoreCase, hibernate makes 'lower(field)=?' SQL expression, passing lowercased strings to '?' parameter. This may produce unpredictable results depending on Database server lower implementation and current JAVA locale (see JDK javadoc). For example, I've tried with '\u0130' character as in JDK JavaDoc. Postgresql produces: unhappy=> select lower('İ'); lower ------- i̇ (1 row) unhappy=> select char_length(lower('İ')); char_length ------------- 2 (1 row) While Java with default locale produces single-character 'i̇'. Of course the restriction will not work - it can not find 'İ' in database. I'd recommend to use 'lower(field)=lower(?)' to use same lower casing function for both parts of expression. -- 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

12 years, 5 months

2
2
0 / 0

[Hibernate-JIRA] Created: (OGM-22) Support Session#list and JP-QL queries

by Emmanuel Bernard (JIRA)

Support Session#list and JP-QL queries -------------------------------------- Key: OGM-22 URL: http://opensource.atlassian.com/projects/hibernate/browse/OGM-22 Project: Hibernate OGM Issue Type: New Feature Components: query Reporter: Emmanuel Bernard -- 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

12 years, 5 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2808) CLONE -Impossible to define caching for a subclass's collection in hibernate.cgf.xml

by Sebastien Blind (JIRA)

CLONE -Impossible to define caching for a subclass's collection in hibernate.cgf.xml ------------------------------------------------------------------------------------- Key: HHH-2808 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2808 Project: Hibernate3 Issue Type: Bug Components: caching (L2) Affects Versions: 3.2.5 Environment: Hibernate 3.2.5 Sybase Reporter: Sebastien Blind Basically, hibernate allows to define <cache usage="transactional"/> inside the subclass mapping, i.e. <subclass name="SubClass" extends="BaseClass" discriminator-value="xxx"> <bag name="subClassLinks" lazy="false" inverse="true" batch-size="100"> <cache usage="transactional" region="xxx"/> <key column="xxx" not-null="true"/> <one-to-many class="xxx"/> </bag> <join table="xxx"> </join> </subclass> but it's not allowed to do the same using <collection-cache collection="subClass.myCollection" region="xxx" usage="transactional"/>. It throws: Exception in thread "main" org.hibernate.MappingException: Cannot cache an unknown collection: subClass.myCollection at org.hibernate.cfg.Configuration.setCollectionCacheConcurrencyStrategy(Configuration.java:1984) at org.hibernate.cfg.Configuration.parseSessionFactory(Configuration.java:1568) at org.hibernate.cfg.Configuration.doConfigure(Configuration.java:1534) at org.hibernate.cfg.Configuration.doConfigure(Configuration.java:1508) at org.hibernate.cfg.Configuration.configure(Configuration.java:1428) -- 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

12 years, 5 months

6
10
0 / 0

[Hibernate-JIRA] Created: (OGM-21) Support EntityManager#createQuery(String)

by Emmanuel Bernard (JIRA)

Support EntityManager#createQuery(String) ----------------------------------------- Key: OGM-21 URL: http://opensource.atlassian.com/projects/hibernate/browse/OGM-21 Project: Hibernate OGM Issue Type: New Feature Components: query Reporter: Emmanuel Bernard -- 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

12 years, 5 months

2
1
0 / 0

[Hibernate-JIRA] Created: (OGM-20) Integrate the JP-QL to HSQuery / Lucene module

by Emmanuel Bernard (JIRA)

Integrate the JP-QL to HSQuery / Lucene module ---------------------------------------------- Key: OGM-20 URL: http://opensource.atlassian.com/projects/hibernate/browse/OGM-20 Project: Hibernate OGM Issue Type: Task Reporter: Emmanuel Bernard Assignee: Sanne Grinovero -- 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

12 years, 5 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-4959) Concurrent HQL parsing blocks on ReflectHelper.classForName()

by Jarl Totland (JIRA)

Concurrent HQL parsing blocks on ReflectHelper.classForName() ------------------------------------------------------------- Key: HHH-4959 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4959 Project: Hibernate Core Issue Type: Improvement Components: query-hql Affects Versions: 3.3.2 Environment: DB2 Reporter: Jarl Totland Priority: Minor Attachments: ReflectHelper.java For particularly HQL-heavy applications, concurrency is lost as ReflectHelper.classForName() blithely runs loadClass() for tokens again and again, many of which are not even classes. As loadClass() is synchronized it end up blocking while it generates stacktraces for its exceptions. This goes for both classic and AST parsers. Because of this blocking our regression tests took over 20 minutes, regardless of number of threads. Implementing a simple cache from String to Class in ReflectHelper.classForName() reduced this to 3 minutes for eight threads on a dual-core cpu; the bottleneck is now the database as it should be, not lock contention. The issue was reported earlier in HHH-1810, but dismissed as related to the classic parser only. We might use HQL in inappropriate ways, but still wouldn't hurt for Hibernate to support this. Attached is our modified ReflectHelper; modified code is in the classForName()-methods, classForNameInternal(), and the static HashMap<String, Object> classes. -- 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

12 years, 5 months

4
5
0 / 0

[Hibernate-JIRA] Created: (HHH-5274) HQL-Insert with Select and Sub-Select fails

by Björn Moritz (JIRA)

HQL-Insert with Select and Sub-Select fails ------------------------------------------- Key: HHH-5274 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5274 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.2 Environment: Hibernate 3.5.2, Oracle 10 (using org.hibernate.dialect.Oracle10gDialect) Reporter: Björn Moritz Attachments: Testcase.zip In Hibernate 3.5.2 a HQL-Insert statement doing a select using a subselect is failing. This is due to a wrong replacement of the table name in the generated SQL-Statement. The following statement will work: {code:sql}select a.id from A a where exists (select 1 from B b where b.id = a.id){code} but an insert statement embedding the same statement does not work: {code:sql}insert into C (id) select a.id from A a where exists (select 1 from B b where b.id = a.id){code} The latter statement will thrown an SqlSyntaxErrorException as the second 'a.id' will get replaced with 'AAA.id' (which is the real table name and not the alias used in the generated sql statement). In Hibernate 3.1.3 both statements worked fine. -- 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

12 years, 6 months

1
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2851) ParameterTranslationsImpl fails to correctly determine parameter type

by Alex Savitsky (JIRA)

ParameterTranslationsImpl fails to correctly determine parameter type --------------------------------------------------------------------- Key: HHH-2851 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2851 Project: Hibernate3 Issue Type: Bug Components: query-hql Affects Versions: 3.2.5 Reporter: Alex Savitsky Priority: Minor For the conditions in the form "(:param IS NULL OR alias.someField = :param)", the HQL parses would not correctly determine the type of param, unless the conditions are swapped like "(alias.someField = :param OR :param IS NULL)". The reason is that NamedParamTempHolder classes are created for all parameter entries, in the order they appear in the query. The first occurrence (:param IS NULL) would have its expectedType set to null, and the second occurrence would use the param holder created by the first occurrence, without checking whether it can improve it in any way (which it can - the expectedType for second occurrence is correctly determined to be Long). Proposed fix would be to check for this particular condition, enhancing paramHolder if possible, with new information: old code: if ( paramHolder == null ) { paramHolder = new NamedParamTempHolder(); paramHolder.name = namedSpec.getName(); paramHolder.type = namedSpec.getExpectedType(); namedParameterMap.put( namedSpec.getName(), paramHolder ); } new code: if ( paramHolder == null ) { paramHolder = new NamedParamTempHolder(); paramHolder.name = namedSpec.getName(); paramHolder.type = namedSpec.getExpectedType(); namedParameterMap.put( namedSpec.getName(), paramHolder ); + } else if (paramHolder.getExpectedType() == null && namedSpec.getExpectedType() != null) { + paramHolder.type = namedSpec.getExpectedType(); } -- 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

12 years, 6 months

6
10
0 / 0

[Hibernate-JIRA] Created: (HHH-2394) Support filter tag in subclass

by Welkin Hu (JIRA)

Support filter tag in subclass ------------------------------ Key: HHH-2394 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2394 Project: Hibernate3 Type: Improvement Components: core Versions: 3.0 beta 4 Reporter: Welkin Hu Assigned to: Steve Ebersole Fix For: 3.0 rc 1 According to a user: http://forum.hibernate.org/viewtopic.php?p=2229539#2229539 It's not possible to get a filter to apply to a subclass. This is Bad ;-) Steve, is that correct? -- 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

12 years, 6 months

7
9
0 / 0

[Hibernate-JIRA] Created: (HBX-1123) Reveng foreign-key map to non-primary key column produces incorrect mapping file

by Michael Sabin (JIRA)

Reveng foreign-key map to non-primary key column produces incorrect mapping file -------------------------------------------------------------------------------- Key: HBX-1123 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1123 Project: Hibernate Tools Issue Type: Bug Affects Versions: 3.2.4 Beta1 Environment: Eclipse Platform Version: 3.4.2 Build id: M20090211-1700 Hibernate Tools 3.2.4.GA-R200903141626-H5 Windows XP Pro SP3 JRE 6 Tested on Oracle 10g and Apache Derby Reporter: Michael Sabin Priority: Minor Attachments: CodeGenCfg1.png, CodeGenCfg2.png Creating a mapping from a column in one table to a non-primary key column in another table produces incorrect mapping file missing a property-ref to the non-primary key. How to reproduce using Apache Derby: Create a database and connect to the database. jdbc:derby://localhost:1527/myDB;create=true;user=me;password=mine Create these tables in the myDB database, in the ME schema. create table vehicles ( make_id integer, model_id integer, name varchar(50), PRIMARY KEY (make_id, model_id) ); create table owners ( owner_id integer PRIMARY KEY, favorite_make_id integer, name varchar(20) ); -- optional content insert into vehicles values (1, 10, 'Chevrolet Corvette'); insert into vehicles values (2, 11, 'Ford Focus'); insert into vehicles values (3, 12, 'Honda Accord'); insert into vehicles values (4, 13, 'Toyota Camry'); insert into owners values (50, 3, 'Jim'); insert into owners values (51, 1, 'Alex'); insert into owners values (52, 4, 'Sue'); insert into owners values (53, 1, 'Casey'); Create this Hibernate Configuration file. <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE hibernate-configuration PUBLIC "-//Hibernate/Hibernate Configuration DTD 3.0//EN" "http://hibernate.sourceforge.net/hibernate-configuration-3.0.dtd"> <hibernate-configuration> <session-factory> <property name="hibernate.connection.driver_class">org.apache.derby.jdbc.EmbeddedDriver</property> <property name="hibernate.connection.url">jdbc:derby://localhost:1527/myDB</property> <property name="hibernate.connection.username">me</property> <property name="hibernate.connection.password">mine</property> <property name="hibernate.dialect">org.hibernate.dialect.DerbyDialect</property> <property name="hibernate.current_session_context_class">thread</property> <property name="hibernate.default_schema">ME</property> <property name="hibernate.show_sql">true</property> </session-factory> </hibernate-configuration> Setup a Hibernate Console Configuration with the configuration above and connection to the Derby database. Create this Hibernate reverse engineering configuration <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE hibernate-reverse-engineering PUBLIC "-//Hibernate/Hibernate Reverse Engineering DTD 3.0//EN" "http://hibernate.sourceforge.net/hibernate-reverse-engineering-3.0.dtd" > <hibernate-reverse-engineering> <table-filter match-name="OWNERS"/> <table-filter match-name="VEHICLES"/> <table name="VEHICLES"> <foreign-key foreign-table="OWNERS"> <column-ref local-column="MAKE_ID" foreign-column="FAVORITE_MAKE_ID" /> </foreign-key> </table> </hibernate-reverse-engineering> Setup a Hibernate Code Generation configuration like in the attached images. Running the Code Generation configuration will produce this Vehicles.hbm.xml mapping file. <?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> <class name="reveng.Vehicles" table="VEHICLES"> <composite-id name="id" class="reveng.VehiclesId"> <key-property name="makeId" type="int"> <column name="MAKE_ID" /> </key-property> <key-property name="modelId" type="int"> <column name="MODEL_ID" /> </key-property> </composite-id> <many-to-one name="owners" class="reveng.Owners" update="false" insert="false" fetch="select"> <column name="MAKE_ID" not-null="true" /> </many-to-one> <property name="name" type="string"> <column name="NAME" length="50" /> </property> </class> </hibernate-mapping> The many-to-one tag should have this additional attribute: property-ref="favoriteMakeId" -- 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

12 years, 6 months

2
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues March 2011