April 2011 - hibernate-issues - Jboss List Archives

[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-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-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

[Hibernate-JIRA] Created: (HSEARCH-264) Make a Luke version that can reuse Hibernate Search analyzers (per entity or per name)

by Emmanuel Bernard (JIRA)

Make a Luke version that can reuse Hibernate Search analyzers (per entity or per name) -------------------------------------------------------------------------------------- Key: HSEARCH-264 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-264 Project: Hibernate Search Issue Type: New Feature Components: query Reporter: Emmanuel Bernard Probably more on Hibernate Tools. Would be nice to fix copy/paste bugs too. -- 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: (ANN-777) Map key column is included in the PK but is not forced not-null

by Emmanuel Bernard (JIRA)

Map key column is included in the PK but is not forced not-null --------------------------------------------------------------- Key: ANN-777 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-777 Project: Hibernate Annotations Issue Type: Bug Components: binder Reporter: Emmanuel Bernard Assignee: Hardy Ferentschik I think forcing not-null is the right approach. This needs some investigation though -- 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
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3031) Include "FOR READ ONLY" hint in non-locking DB2 statements

by Steve Finch (JIRA)

Include "FOR READ ONLY" hint in non-locking DB2 statements ---------------------------------------------------------- Key: HHH-3031 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3031 Project: Hibernate3 Issue Type: Improvement Components: core Affects Versions: 3.2.5 Environment: 3.2.5, DB2/UDB 8.1+ Reporter: Steve Finch As per the DB2 documentation: http://publib.boulder.ibm.com/infocenter/db2luw/v8/index.jsp?topic=/com.i... The FOR READ ONLY clause indicates that the result table is read-only and therefore the cursor cannot be referred to in Positioned UPDATE and DELETE statements. FOR FETCH ONLY has the same meaning. For result tables in which updates and deletes are allowed, specifying FOR READ ONLY (or FOR FETCH ONLY) can possibly improve the performance of FETCH operations by allowing the database manager to do blocking. For example, in programs that contain dynamic SQL statements without the FOR READ ONLY or ORDER BY clause, the database manager might open cursors as if the FOR UPDATE clause were specified. It is recommended, therefore, that the FOR READ ONLY clause be used to improve performance, except in cases where queries will be used in positioned UPDATE or DELETE statements. A read-only result table must not be referred to in a Positioned UPDATE or DELETE statement, whether it is read-only by nature or specified as FOR READ ONLY (FOR FETCH ONLY). The aforementioned improvement can be achieved by applying "FOR READ ONLY" when other locking hints are not specified. Patch to be uploaded soon. -- 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

5
7
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 April 2011