March 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HSEARCH-141) Allow term position information to be stored in an index

by John Griffin (JIRA)

Allow term position information to be stored in an index -------------------------------------------------------- Key: HSEARCH-141 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-141 Project: Hibernate Search Issue Type: New Feature Components: engine Reporter: John Griffin Assignee: John Griffin The default behavior of indexing is to not store term position and offset information. Modify the @Field annotation to allow input of Field.TermVector values. This would facilitate proximity queries. -- 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

18 years

2
1
0 / 0

[Hibernate-JIRA] Created: (ANN-712) Maven pom.xml should (in time) depend on javax.persistence:persistence-api instead of org.hibernate:ejb3-persistence

by Geoffrey De Smet (JIRA)

Maven pom.xml should (in time) depend on javax.persistence:persistence-api instead of org.hibernate:ejb3-persistence -------------------------------------------------------------------------------------------------------------------- Key: ANN-712 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-712 Project: Hibernate Annotations Issue Type: Task Affects Versions: 3.3.1.GA Reporter: Geoffrey De Smet Priority: Minor Now it's possible to get the same classes (for example javax.persistence.Entity) twice in the classpath: - one from persistence-api-1.0.jar - and another from ejb3-persistence-1.0.1.GA.jar. Mix that with classloaders and you get bugs like A extends B but an A is not instance of B (because B.class is loaded twice from different jars). Otherwise you can get this too, but if the groupId:artifactId match, maven deals with it. In theory, replace: <dependency> <groupId>org.hibernate</groupId> <artifactId>ejb3-persistence</artifactId> <version>1.0.1.GA</version> </dependency> with: <dependency> <groupId>javax.persistence</groupId> <artifactId>persistence-api</artifactId> <version>1.0</version>  </dependency> It looks like org.hibernate:ejb3-persistence is just a copy of javax.persistence:persistence-api, but with a hot-fix applied to it: probably because javax.persistence:persistence-api:1.0.1 isn't deployed to the central repo yet. So the JCP might need to be poked to put javax.persistence:persistence-api:1.0.1 on the central repo :) Which is probably not an easy thing to do... -- 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

18 years

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3192) SchemaValidator nullability check

by Ioannis Cherouvim (JIRA)

SchemaValidator nullability check --------------------------------- Key: HHH-3192 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3192 Project: Hibernate3 Issue Type: Patch Affects Versions: 3.2.6 Environment: 3.2.6.ga, MySQL, SQL Sever 2000 Reporter: Ioannis Cherouvim Priority: Trivial Attachments: table-nullability.patch I validate my schema with org.hibernate.tool.hbm2ddl.SchemaValidator It works OK, but it does not check for column null/not-null constraint. org.hibernate.mapping.Table.validateColumns only checks for column type. Checking for null constraint would be helpful. Here is a patch which improves this method. -- 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

18 years

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-2878) LazyInitializationException - no session or session was closed

by Paul Andrews (JIRA)

LazyInitializationException - no session or session was closed -------------------------------------------------------------- Key: HHH-2878 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2878 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.5 Environment: Hibernate v 3.1.4-3.2.5, Oracle/HSQLDB/Whatever Reporter: Paul Andrews Attachments: testcase.zip A LazyInitializationException is thrown for a lazy set when the items in the set can be duplicates. This is manifested in a many-to-many implemented using join table; the session is still open but the session for the collection is set to null. The attached ZIP contains a test-case that demonstrates this. -- 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

18 years

2
2
0 / 0

[Hibernate-JIRA] Commented: (HHH-1787) Postgres dialect needs date_trunc

by Brett Elliott (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1787?page=c... ] Brett Elliott commented on HHH-1787: ------------------------------------ Diego Pires Plentz, The patch just specifies the return type, but I see your confusion, you are looking at the timestamp type specified in the patch as the parameter. I tested the patch and it works. It has been 2 years, let's please add this patch to the code base. Thank you. > Postgres dialect needs date_trunc > --------------------------------- > > Key: HHH-1787 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1787 > Project: Hibernate3 > Issue Type: Patch > Components: metamodel > Affects Versions: 3.1 > Environment: 3.1.3, postgres > Reporter: George Courter > Attachments: patch > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Postgres dialect needs the date_trunc function registered. Patch is included. -- 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

18 years

1
0
0 / 0

[Hibernate-JIRA] Commented: (HBX-696) hbm2java does not generate equals/hashCode

by Max Rydahl Andersen (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-696?page=co... ] Max Rydahl Andersen commented on HBX-696: ----------------------------------------- please be more specific on what you do....are you actually specifying which properties there should be used in equals/hashcode via <meta> tags in hbm.xml or reveng.xml ? In anycase - put it in a new jira if you can show it failing > hbm2java does not generate equals/hashCode > ------------------------------------------ > > Key: HBX-696 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-696 > Project: Hibernate Tools > Issue Type: Bug > Components: hbm2java > Affects Versions: 3.1.beta5 > Reporter: Bertram Grillitsch > Fix For: 3.2beta9 > > > see forum entry: http://forum.hibernate.org/viewtopic.php?t=959889 for details: > but basically the hbm2java task does not generate the equals/hashCode functions -- 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

18 years

1
0
0 / 0

[Hibernate-JIRA] Commented: (HBX-696) hbm2java does not generate equals/hashCode

by Keith Garry Boyce (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-696?page=co... ] Keith Garry Boyce commented on HBX-696: --------------------------------------- I'm not seeing this working in eclipse. I'm using 3.2.0.GA > hbm2java does not generate equals/hashCode > ------------------------------------------ > > Key: HBX-696 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-696 > Project: Hibernate Tools > Issue Type: Bug > Components: hbm2java > Affects Versions: 3.1.beta5 > Reporter: Bertram Grillitsch > Fix For: 3.2beta9 > > > see forum entry: http://forum.hibernate.org/viewtopic.php?t=959889 for details: > but basically the hbm2java task does not generate the equals/hashCode functions -- 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

18 years

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-613) search by criteria with sub-class Example do not bind sub-class properties

by Paul Benedict (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-613?page=co... ] Paul Benedict commented on HHH-613: ----------------------------------- Ah. I see. If you create a criteria of the supertype and make an example of the subtype, it obviously will not work. As Gavin said, this is correct behavior. You need to actually create an example of the subtype. > search by criteria with sub-class Example do not bind sub-class properties > -------------------------------------------------------------------------- > > Key: HHH-613 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-613 > Project: Hibernate3 > Issue Type: Bug > Components: core > Affects Versions: 3.0.5 > Reporter: Foaloke > Priority: Blocker > > class Animal { > private Int age; > ... > } > class Pet extends Animal { > private String name; > ... > } > Pet pet = new Pet(); > pet.setName("Fritz"); > session.createCriteria(Animal.class).add(Example.create(pet)).list(); > This will simply return all 'Pets', no binding occurs with the "name" property of Pet. > This could, more probably, occurs if I have some Country which contains Animals & I want to look for some kind of Pets in that country : > session.createCriteria(Country.class).createCriteria("animal").add(Example.create(pet)).list(); -- 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

18 years

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-2884) Provide a sessionFactory close event or hook for the event listeners

by Emmanuel Bernard (JIRA)

Provide a sessionFactory close event or hook for the event listeners -------------------------------------------------------------------- Key: HHH-2884 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2884 Project: Hibernate3 Issue Type: New Feature Components: core Reporter: Emmanuel Bernard Fix For: 3.3 It can be done either: - as an event/eventListener - as a method that eventlisteners implement (symmetric of initialize()) The former being more flexible -- 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

18 years

3
2
0 / 0

[Hibernate-JIRA] Updated: (HHH-530) Allow application of filters on subqueries

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-530?page=co... ] Steve Ebersole updated HHH-530: ------------------------------- Fix Version/s: (was: 3.3.0.CR1) 3.3.0 > Allow application of filters on subqueries > ------------------------------------------ > > Key: HHH-530 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-530 > Project: Hibernate3 > Issue Type: Patch > Components: core > Reporter: Gavin King > Assignee: Steve Ebersole > Fix For: 3.3.0 > > Attachments: HHH-530.Additional.Subquery.patch, HHH-530.patch, hibernate_filter_fix-3.0.5.patch, hibernate_filter_fix-3.0.5_14.patch, SubqueriesWithFiltersTest.patch > > > Currently filter conditions are applied in subselects, they should not be. -- 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

18 years

1
0
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 March 2008