May 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-6049) Improve error message about incompatible JDBC driver

by Sanne Grinovero (JIRA)

Improve error message about incompatible JDBC driver ---------------------------------------------------- Key: HHH-6049 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6049 Project: Hibernate Core Issue Type: Task Components: core Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 3.6.3 We should revert the workaround committed as part of (HHH-5642) Error configuring Hibernate with PostgreSQL JDBC3 8.2.511 driver and fail fast instead, with a good errormessage like "this jdbc driver compiled against jdk 1.3 or earlier..." -- 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, 1 month

3
9
0 / 0

[Hibernate-JIRA] Created: (HSHARDS-57) For a better "virtual shards" support!

by Colbert Philippe (JIRA)

For a better "virtual shards" support! -------------------------------------- Key: HSHARDS-57 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSHARDS-57 Project: Hibernate Shards Issue Type: Improvement Affects Versions: 3.0.0.Beta2 Environment: Windows XP Reporter: Colbert Philippe Assignee: Max Ross The current implementation of virtual shards leaves a lot to be desired when used in big corporate applications. A better way to model shards, is to identify a virtual shard by a pairing of "some name" + "an index" (example: Clients, 11). The name plays a role similar to namespaces. The index is always zero based and valid only within the namespace. There can be many shard namespaces with unique names. A configuration file (possibly XML) will map each virtual shard to a single physical shard. It's a simple mapping strategy. The mapping can allow overlaps of virtual shards into a single physical shard. This type of naming can make things more clear and easier to manage on the long-run. The big advantage to virtual shards over physical shards is that virtual shards can be easily persisted to file or database and retrieved again and still remain valid. Any change to the shard structure is fully controlled by the shard configuration file, without modifications to the persisted representation of the shard. This way the code can evolve separately from the physical shard architecture. With this kind of virtual shard, top-of-tree classes will map to a single shard namespace. The object will reside in any of the virtual shard indexes associated with the shard namespace. The resolution strategy becomes very simple because the set of shard indexes will be returned. -- 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, 1 month

2
1
0 / 0

[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, 1 month

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, 1 month

2
3
0 / 0

[Hibernate-JIRA] Created: (JPA-15) Criteria API based on MapKeyColumn is not working

by Edwin Dalorzo (JIRA)

Criteria API based on MapKeyColumn is not working ------------------------------------------------- Key: JPA-15 URL: http://opensource.atlassian.com/projects/hibernate/browse/JPA-15 Project: Java Persistence API Issue Type: Bug Environment: Hibernate 3.6.1 MySQL 5.0 Reporter: Edwin Dalorzo Attachments: log.txt, src.zip I defined an Employee entity having a map of phone numbers, where the key is the type of phone (home, office, mobile) and the value is the phone number as a String. @ElementCollection(fetch=FetchType.LAZY) @CollectionTable(name="emp_phone") @MapKeyColumn(name="phone_type") @Column(name="phone_num") private Map<String, String> phoneNumbers; Then I tried to write a Criteria API query using a map join, like this: CriteriaBuilder builder = entityManager.getCriteriaBuilder(); CriteriaQuery<Employee> criteria = builder.createQuery(Employee.class); Root<Employee> employeeRoot = criteria.from(Employee.class); criteria.select(employeeRoot); MapJoin<Employee, String, String> phoneRoot = employeeRoot.joinMap("phoneNumbers"); criteria.where(builder.equal(phoneRoot.key(), "HOME")); System.out.println(entityManager.createQuery(criteria).getResultList()); You get an NullPointerException java.lang.NullPointerException at org.hibernate.ejb.criteria.path.AbstractPathImpl.prepareAlias(AbstractPathImpl.java:246) at org.hibernate.ejb.criteria.path.AbstractPathImpl.render(AbstractPathImpl.java:253) at org.hibernate.ejb.criteria.predicate.ComparisonPredicate.render(ComparisonPredicate.java:173) at org.hibernate.ejb.criteria.QueryStructure.render(QueryStructure.java:258) at org.hibernate.ejb.criteria.CriteriaQueryImpl.render(CriteriaQueryImpl.java:340) at org.hibernate.ejb.criteria.CriteriaQueryCompiler.compile(CriteriaQueryCompiler.java:223) at org.hibernate.ejb.AbstractEntityManagerImpl.createQuery(AbstractEntityManagerImpl.java:441) at com.dalorzo.Main.main(Main.java:57) Exception in thread "main" java.lang.RuntimeException: java.lang.NullPointerException at com.dalorzo.Main.main(Main.java:64) Caused by: java.lang.NullPointerException at org.hibernate.ejb.criteria.path.AbstractPathImpl.prepareAlias(AbstractPathImpl.java:246) at org.hibernate.ejb.criteria.path.AbstractPathImpl.render(AbstractPathImpl.java:253) at org.hibernate.ejb.criteria.predicate.ComparisonPredicate.render(ComparisonPredicate.java:173) at org.hibernate.ejb.criteria.QueryStructure.render(QueryStructure.java:258) at org.hibernate.ejb.criteria.CriteriaQueryImpl.render(CriteriaQueryImpl.java:340) at org.hibernate.ejb.criteria.CriteriaQueryCompiler.compile(CriteriaQueryCompiler.java:223) at org.hibernate.ejb.AbstractEntityManagerImpl.createQuery(AbstractEntityManagerImpl.java:441) at com.dalorzo.Main.main(Main.java:57) If you change the query to filter on value instead of key, it works just fine criteria.where(builder.equal(phoneRoot.value(), "88750372")); I have attached a log with exceptions as well as the Employee entity and the Main class containing a main method. Also, the code in question runs perfectly fine in EclipseLink. -- 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, 1 month

6
8
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, 1 month

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, 1 month

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, 1 month

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, 1 month

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, 1 month

1
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues May 2011