June 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-4630) Criteria join on composite identifier generates wrong alias, SQL error

by Chris Wilson (JIRA)

Criteria join on composite identifier generates wrong alias, SQL error ---------------------------------------------------------------------- Key: HHH-4630 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4630 Project: Hibernate Core Issue Type: Patch Components: core Affects Versions: 3.5 Environment: Hibernate trunk from 2009-11-30, Ubuntu 8.04, Sun Java 1.6.0-17, MySQL 5.0.51a-3ubuntu5.4 Reporter: Chris Wilson Attachments: hibernate-invalid-alias-generation.patch Hibernate generates the wrong alias on a Criteria query involving a join on a composite identifier. For example, in the test below without the fix to JoinWalker, it generates this SQL: select this_.role_code as role1_0_1_, this_.is_deleted as is2_0_1_, this_.record_version as record3_0_1_, complexjoi3_.code as code1_0_, complexjoi3_.is_deleted as is2_1_0_, complexjoi3_.record_version as record3_1_0_ from list_action_roles this_ left outer join roles complexjoi3_ on this_.role_code=complexjoi3_.code where this_.is_deleted=? and complexjoi1_.is_deleted=? Which results in this error from the SQL server: Unknown column 'complexjoi1_.is_deleted' in 'where clause' Analysis of the problem: The entity persister class with the composite identifier has a fake property for it, called "_identifierMapper" (see HbmBinder.bindCompositeId() and similarly in Annotations). This property name ends up in the path used by JoinWalker.walkEntityTree() when it calls walkComponentTree(). However that path is used by CriteriaJoinWalker.generateTableAlias() to look up the correct criteria (and hence the alias) from the translator, a CriteriaQueryTranslator. The alias was created in CriteriaQueryTranslator.createCriteriaSQLAliasMap for a Criteria without this extra _identifierMapper path component. So when CriteriaJoinWalker tries to use the path with _identifierMapper to look up the criteria to find the correct alias to use, in generateTableAlias(), it doesn't find one, so it generates a new alias. That new alias no longer matches the one that will be rendered out in the WHERE clause, so the WHERE clause will refer to table names using aliases that are not used anywhere else in the query, and the SQL server will fail to parse the statement. The solution appears to be to exclude "_identifierMapper" components in the alias path when building it. I don't know what other implications that might have, but it seems like an implementation nastiness that shouldn't be exposed. Patch attached. -- 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, 9 months

4
7
0 / 0

[Hibernate-JIRA] Created: (HHH-6073) Dialects cannot use the Thread Context ClassLoader with AS7, please change to use the

by Scott Marlow (JIRA)

Dialects cannot use the Thread Context ClassLoader with AS7, please change to use the -------------------------------------------------------------------------------------- Key: HHH-6073 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6073 Project: Hibernate Core Issue Type: Task Reporter: Scott Marlow Priority: Blocker Fix For: 4.0.0.Alpha2 We can no longer rely on TCCL because AS7 is following a modular class loading approach. The AS7 "org.hibernate" module isn't setup to access the JDBC classes. For creating dialects, could we instead use the classloader from the java.sql.Connection that is passed into the DialectFactory. The following warning shows what we currently see with Hibernate 3.6.1 and the DerbyDialect (TCCL is null). 08:45:27,597 INFO [org.hibernate.dialect.Dialect] (MSC service thread 1-6) Using dialect: org.hibernate.dialect.DerbyDialect 08:45:27,603 INFO [org.hibernate.dialect.Dialect] (MSC service thread 1-2) Using dialect: org.hibernate.dialect.DerbyDialect 08:45:27,614 WARN [org.hibernate.dialect.DerbyDialect] (MSC service thread 1-6) Unable to load/access derby driver class sysinfo to check versions : java.lang.ClassNotFoundException: org.apache.derby.tools.sysinfo from [Module "org.hibernate:main" from local module loader @fee4648 (roots: /work/as7-dev/jboss-as/build/target/jboss-7.0.0.Beta2/modules)] 08:45:27,616 WARN [org.hibernate.dialect.DerbyDialect] (MSC service thread 1-2) Unable to load/access derby driver class sysinfo to check versions : java.lang.ClassNotFoundException: org.apache.derby.tools.sysinfo from [Module "org.hibernate:main" from local module loader @fee4648 (roots: /work/as7-dev/jboss-as/build/target/jboss-7.0.0.Beta2/modules)] -- 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, 9 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-6079) Random order of generated columns for a class hierarchy using @Inheritance(strategy = InheritanceType.SINGLE_TABLE)

by Saša Obradović (JIRA)

Random order of generated columns for a class hierarchy using @Inheritance(strategy = InheritanceType.SINGLE_TABLE) ------------------------------------------------------------------------------------------------------------------- Key: HHH-6079 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6079 Project: Hibernate Core Issue Type: Bug Components: annotations, core Affects Versions: 3.6.1 Environment: hibernate-tools-3.4.0.CR1, Oracle Database Reporter: Saša Obradović Attachments: bugreport.zip hbm2ddl (org.hibernate.tool.ant.HibernateToolTask) using JPA generates a common table with all columns needed by inherited classes correctly. Bug description: The columns are generated in a not predictable order. Each invocation could result in a completely new order. This makes ensuring consistency of the domain model after each iteration (for example using svn diff) virtually impossible. We have been experiencing this behaviour after upgrading Hibernate from version 3.3.2 to version 3.6.1. -- 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, 9 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-660) Remove DirtyStrategy when we start depending on Core 4.x

by Emmanuel Bernard (JIRA)

Remove DirtyStrategy when we start depending on Core 4.x -------------------------------------------------------- Key: HSEARCH-660 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-660 Project: Hibernate Search Issue Type: Task Components: engine Affects Versions: 3.4.0 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

14 years, 9 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-755) Upgrade to Hibernate 4

by Sanne Grinovero (JIRA)

Upgrade to Hibernate 4 ---------------------- Key: HSEARCH-755 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-755 Project: Hibernate Search Issue Type: Task Affects Versions: 3.4.0.Alpha1 Reporter: Sanne Grinovero Priority: Blocker And integrate with the new API, service registry, lifecycle. -- 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, 9 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-35) Look for log and exception strategy

by Emmanuel Bernard (JIRA)

Look for log and exception strategy ----------------------------------- Key: HSEARCH-35 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-35 Project: Hibernate Search Type: Task Components: mapping, query, engine, directory provider Reporter: Emmanuel Bernard Priority: Minor Fix For: 3.0.0.beta2 -- 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, 9 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-768) MassIndexer working with the standard backend

by Sanne Grinovero (JIRA)

MassIndexer working with the standard backend --------------------------------------------- Key: HSEARCH-768 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-768 Project: Hibernate Search Issue Type: New Feature Components: massindexer Reporter: Sanne Grinovero Fix For: 4.0.0.Alpha1 -- 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, 9 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-636) DateBridge substracts one day from date

by Marc Schipperheyn (JIRA)

DateBridge substracts one day from date --------------------------------------- Key: HSEARCH-636 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-636 Project: Hibernate Search Issue Type: Bug Affects Versions: 3.3.0.CR1 Environment: Lucene 3.0.2 Reporter: Marc Schipperheyn I find that the public String objectToString(Object object) in the DateBridge class consistently returns a date that's one day before the date being passed. A Date object with date 2011-12-12 will become a string representation of 2011-12-11. Since the Lucene core DateTools are used, I assume the problem lies there and you might want to consider moving to another date library. -- 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, 9 months

2
10
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-210) Support hbm xml mapping!

by Mark Stewart (JIRA)

Support hbm xml mapping! ------------------------ Key: HSEARCH-210 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-210 Project: Hibernate Search Issue Type: Bug Components: mapping Affects Versions: 3.0.1.GA Environment: All. Reporter: Mark Stewart I like annotations as much as the next guy but it's a complete non-starter for our business (and, I suspect, plenty of others) to add full text search to our existing apps via Hibernate Search if it means we must convert all our existing hbm.xml configurations into annotations. The regression testing alone would kill us. The Hibernate project has always been supremely pragmatic which is why I've filed this as a bug rather than a feature request. I don't think Hibernate would have been half as popular if it didn't support things like direct SQL and reverse engineering tools. I think Search would see a big boost if it could be easily added to existing applications. Please consider adding the needed syntax for xml mapping. At the very least an entry in the FAQ that explains the lacking is needed. -- 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, 9 months

6
11
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-373) @AnalyzerDiscriminator applied to _hibernate_class field

by Sanne Grinovero (JIRA)

@AnalyzerDiscriminator applied to _hibernate_class field -------------------------------------------------------- Key: HSEARCH-373 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-373 Project: Hibernate Search Issue Type: Bug Reporter: Sanne Grinovero It appears that implementations of org.hibernate.search.analyzer.Discriminator is also called to identify the Analyzer to be used to index the reserved "id" and "_hibernate_class". I'm not sure if it's a good idea on "id", it probably isn't at all on "_hibernate_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, 9 months

3
4
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues June 2011