March 2011 - hibernate-issues - Jboss List Archives

[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

13 years, 6 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

13 years, 6 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

13 years, 6 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

13 years, 6 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

13 years, 6 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

13 years, 6 months

5
7
0 / 0

[Hibernate-JIRA] Created: (HHH-5771) PersistentBag.remove() and removeAll() load the whole collection

by Dobes Vandermeer (JIRA)

PersistentBag.remove() and removeAll() load the whole collection ---------------------------------------------------------------- Key: HHH-5771 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5771 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.5 Reporter: Dobes Vandermeer When removing an entity from the database, it is a requirement in hibernate that you remove the entity from any persistent collections it is in so that you don't get errors about transient objects being referenced by a collection. However, calling remove() on a persistent collection seems to load the whole collection into memory. The use of very large (too big to load all at once) lazy collections is apparently not well supported in hibernate because it is difficult to use them without loading the whole collection into memory rather than load it incrementally. Nevertheless, it is possible to request subsets of collections and having the ability to remove() without loading the lazy collection would be a bonus for those of us who do use large lazy collections that way. Here is the offending code: {code} public boolean remove(Object o) { initialize( true ); if ( bag.remove( o ) ) { dirty(); return true; } else { return false; } } {/code} -- 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

13 years, 6 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-6024) NPE in CastFunction when casting a field named "date" to type "date" in HQL

by Jon Mann (JIRA)

NPE in CastFunction when casting a field named "date" to type "date" in HQL --------------------------------------------------------------------------- Key: HHH-6024 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6024 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.6.2 Environment: Hibernate 3.6.0.Final and 3.6.2.Final MySQL 5.0 Reporter: Jon Mann Attachments: hibernate-cast-date.zip In Hibernate version "3.6.2.Final" when casting a field named "date" to type "date": SELECT entity FROM DateEntity AS entity WHERE CAST(entity.date AS date) = ? we encounter a NullPointerException in CastFunction: java.lang.NullPointerException at org.hibernate.dialect.function.CastFunction.render(CastFunction.java:56) at org.hibernate.hql.ast.SqlGenerator.endFunctionTemplate(SqlGenerator.java:214) at org.hibernate.hql.antlr.SqlGeneratorBase.methodCall(SqlGeneratorBase.java:2325) ... If we rename the field "date" to "creationDate", the problem dissapears. If we cast to "time" instead of "date", the problem dissapears. We encountered this problem while using Hibernate version "3.6.0.Final" against MySQL 5.0. Upgrading to Hibernate version "3.6.2.Final" did not resolve the problem. We guess this problem is a bug in the Hibernate HQL parsing code. It might be a problem with our usage of Hibernate, in which case it would be helpful for Hibernate to return a useful error message. Please find attached a minimal Maven test case (using HSQL memory DB) which demonstrates the problem. The following JIRA issue maybe related to this problem: HHH-3770 - NPE in o.h.dialect.function.CastFunction Credit to my colleague Sergey Shinkevich for creating the test case. Thanks to the Hibernate team for a great product. -- 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

13 years, 6 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-6012) HSQLDialect support for ROWNUM

by Ondrej Medek (JIRA)

HSQLDialect support for ROWNUM ------------------------------ Key: HHH-6012 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6012 Project: Hibernate Core Issue Type: Improvement Components: core Affects Versions: 3.6.0.CR2, 3.6.0.CR1, 3.5.6, 3.6.0.Beta4, 3.6.0.Beta3, 3.5.5, 3.6.0.Beta2, 3.6.0.Beta1, 3.5.4, 3.5.3, 3.5.2, 3.5.1, 3.5.0-Final, 3.5.0-CR-2, 3.5.0-CR-1, 3.5.0-Beta-4, 3.5.0-Beta-3, 3.5.0-Beta-2, 3.5.0.Beta-1, 3.3.2, 3.3.1 Reporter: Ondrej Medek New HSQLDB has a support for Oracel compatibility by: SET DATABASE SQL SYNTAX ORA TRUE So, the HSQLDB knows ROWNUM. However, I cannot use it in @Formula. Please, add ROWNUM into the HSQLDialect in the same way, as it is in the Oracle9iDialect. E.g. add: // Oracle compatibility mode support - SET DATABASE SQL SYNTAX ORA TRUE registerFunction( "rownum", new NoArgSQLFunction("rownum", Hibernate.LONG, false) ); -- 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

13 years, 6 months

2
1
0 / 0

[Hibernate-JIRA] Created: (OGM-19) Implement Referencable#getReference in OgmSessionFactory

by Emmanuel Bernard (JIRA)

Implement Referencable#getReference in OgmSessionFactory -------------------------------------------------------- Key: OGM-19 URL: http://opensource.atlassian.com/projects/hibernate/browse/OGM-19 Project: Hibernate OGM Issue Type: New Feature Components: core Reporter: Emmanuel Bernard Priority: Trivial low priority -- 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

13 years, 6 months

3
8
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