February 2007 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (ANN-530) introduce fetch_size for Hibernate Search scrollable resultsets.

by Emmanuel Bernard (JIRA)

introduce fetch_size for Hibernate Search scrollable resultsets. ---------------------------------------------------------------- Key: ANN-530 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-530 Project: Hibernate Annotations Type: New Feature Components: search 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

17 years, 5 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-2342) support <load-collection> for stored procedures (see 3.2 documentation section 16.2.2)

by Rick Bradshaw (JIRA)

support <load-collection> for stored procedures (see 3.2 documentation section 16.2.2) -------------------------------------------------------------------------------------- Key: HHH-2342 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2342 Project: Hibernate3 Type: New Feature Components: core Environment: Any new hibernate version/update - Oracle is my personal DBMS preference Reporter: Rick Bradshaw In the 3.2 documentation 16.2.2 "Using Stored Procedures for Querying" it specifies that "<load-collection>" is not supported. The ability to load collections from stored procedures is a powerful idea. I have done it manually within my own Java implementation and it is a big time / headache saver. Many of the DB models I work with (and don't have control of) are full of inconsistencies that can be re-modeled and disguised within a stored procedure that returns sys_refcursor. Adding the <load-collection> feature will make it really easy/fast to map into hibernate the result sets of stored procedures. -- 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

17 years, 5 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2152) Optimistic lock error although using LockMode.UPGRADE

by Per-Olov Wingren (JIRA)

Optimistic lock error although using LockMode.UPGRADE ----------------------------------------------------- Key: HHH-2152 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2152 Project: Hibernate3 Type: Bug Components: core Versions: 3.1.3 Environment: Oracle 10.2, Hibernate 3.1.3 Reporter: Per-Olov Wingren Priority: Critical Attachments: OptLockProblem.zip I have a situation where two threads tries to update the same entity object at the same time. I use the Hibernate managed versioning using a version number but also a pessimistic lock using LockMode.UPGRADE. One thread will lock the object in the database and the other will wait for the transaction of the first thread to commit (or rollback). The first thread updates the object, which also will make its version to be incremented. When the second tread get access to the object after the first is commited, it get an incorrect value of the version attribute. This leads to a StaleObjectStateException when the transaction is commited. The entity object conists of a parent class and a subclass mapped to the database into two tables using <joined-subclass>. If the testcase is modified to update an attribute in the subclass (numberB) instead of in the superclass it works without errors. Is the problem caused by the fact that Hibernate only locks the subclass in the database (for update of classb.oid) and not the superclass? I attache a zip file containing a simple but complete test case that shows the problem. -- 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

17 years, 5 months

3
2
0 / 0

[Hibernate-JIRA] Created: (ANN-451) Notion of Filtered Lucene queries

by Emmanuel Bernard (JIRA)

Notion of Filtered Lucene queries --------------------------------- Key: ANN-451 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-451 Project: Hibernate Annotations Type: New Feature Components: lucene 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

17 years, 5 months

2
6
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-6) Provide access to the Hit.getScore() and potentially the Document on a query

by Emmanuel Bernard (JIRA)

Provide access to the Hit.getScore() and potentially the Document on a query ---------------------------------------------------------------------------- Key: HSEARCH-6 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-6 Project: Hibernate Search 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

17 years, 5 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-2423) Restrictions.isEmpty ignores where clause defined in the one-to-many collection mapping

by Vladimir Strugatsky (JIRA)

Restrictions.isEmpty ignores where clause defined in the one-to-many collection mapping --------------------------------------------------------------------------------------- Key: HHH-2423 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2423 Project: Hibernate3 Type: Bug Components: query-criteria Versions: 3.1.2 Environment: 3.1.2 against MySQL 5.0 and Oracle 9i Reporter: Vladimir Strugatsky In hbm.xml file: <bag name="issueContextRelationships" lazy="true" inverse="true" cascade="all-delete-orphan" where="SOURCE_SCREEN_NAME='Issue'" > <key column="ID_XXX" > </key> <one-to-many class="com.complianceandrisks.c2p.model.compliancehierarchy.IssueContextRelationship" /> </bag> Using the criteria: criteria.add(Restrictions.isEmpty("issueContextRelationships")); Generates the query: where not exists (select 1 from CONTEXT_REFERENCE_RELS where this_.ID_XXX=ID_XXX) but the SOURCE_SCREEN_NAME='Issue' is not generated! -- 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

17 years, 5 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-1988) Repeated column chack fails with SingleTable inheritance, biut not with TablePerClass

by Sergey Vladimirov (JIRA)

Repeated column chack fails with SingleTable inheritance, biut not with TablePerClass ------------------------------------------------------------------------------------- Key: HHH-1988 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1988 Project: Hibernate3 Type: Bug Components: metamodel Versions: 3.2.0.cr3 Environment: HA last from SVN, HEM last from SVN, MySQL Reporter: Sergey Vladimirov Not sure about component. Parent class introduce field, which is also discriminator field. Hibernate reports error in child class if and only if strategy = InheritanceType.SINGLE_TABLE org.hibernate.MappingException: Repeated column in mapping for entity: ru.arptek.arpsite.data.discriminator.IntegerSingleChild column: type (should be mapped with insert="false" update="false") at org.hibernate.mapping.PersistentClass.checkColumnDuplication(PersistentClass.java:590) at org.hibernate.mapping.PersistentClass.checkPropertyColumnDuplication(PersistentClass.java:612) at org.hibernate.mapping.PersistentClass.checkColumnDuplication(PersistentClass.java:630) at org.hibernate.mapping.PersistentClass.validate(PersistentClass.java:405) at org.hibernate.mapping.SingleTableSubclass.validate(SingleTableSubclass.java:43) at org.hibernate.cfg.Configuration.validate(Configuration.java:1026) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1211) at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:631) at org.hibernate.ejb.Ejb3Configuration.createEntityManagerFactory(Ejb3Configuration.java:760) at org.hibernate.ejb.Ejb3Configuration.createEntityManagerFactory(Ejb3Configuration.java:627) at ru.arptek.arpsite.data.AbstractHibernateJUnitTest.setUp(AbstractHibernateJUnitTest.java:89) at junit.framework.TestCase.runBare(TestCase.java:125) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) Test cas works with strategy = InheritanceType.TABLE_PER_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

17 years, 6 months

3
4
0 / 0

[Hibernate-JIRA] Created: (ANN-538) Give @IndexColumn a default name

by Sven Meier (JIRA)

Give @IndexColumn a default name -------------------------------- Key: ANN-538 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-538 Project: Hibernate Annotations Type: Improvement Versions: 3.2.1 Reporter: Sven Meier Priority: Minor It would be great, if the @IndexColumn annotation had a default 'name'. This would support users (e.g. me ;) in their effort to keep persistence annotations clear of database specifics. Additionally @IndexColumn is a rather often used annotation and it's tedious to repeat the same information (i.e. the 'name') over and over again. I'd propose 'hibernate_index', similar to the defaults in net.sf.hibernate.id.TableGenerator. Preferably this default would come from NamingStrategy, but I'm not sure how stable this interface is supposed to 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

17 years, 6 months

4
6
0 / 0

[Hibernate-JIRA] Created: (HHH-2122) optimization patch based on pmd rules

by Xavier Le Vourch (JIRA)

optimization patch based on pmd rules ------------------------------------- Key: HHH-2122 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2122 Project: Hibernate3 Type: Patch Environment: latest svn source Reporter: Xavier Le Vourch Priority: Minor Attachments: Optimizations.patch I've run pmd with a custom ruleset and made a few optimization changes: Double.valueOf(x).doubleValue() -> Double.parseDouble(x) append("x") -> append('x') x != null && x instanceof X -> x instanceof X list.toArray uses correctly sized array as argument new String(str) -> str if (expr == false) -> if (!expr) append(s1 + s2) -> append(s1).append(s2) loop over array to add to list -> list.addAll(Arrays.asList(<array>)) extra ; removed name.toLowerCase().equals("rowid") -> name.equalsIgnoreCase("rowid") use of System.arraycopy instead of loop I could break the patch in several parts if that makes it easier to analyze. Xavier -- 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

17 years, 6 months

3
3
0 / 0

[Hibernate-JIRA] Created: (ANN-526) Property xyz has an unbound type - is that so?

by Sebastian Kirsch (JIRA)

Property xyz has an unbound type - is that so? ---------------------------------------------- Key: ANN-526 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-526 Project: Hibernate Annotations Type: Bug Versions: 3.2.1 Reporter: Sebastian Kirsch Priority: Minor Attachments: Hibernate ANN-526.zip I get this "Property reference has an unbound type and no explictit target entity" exception and I think this is not exactly true. I'm not sure if this is a bug or a feature requests though. Have a look at the attached files and read on. I guess the model ist pretty easy to understand. The AbstractGeneric allows my to have concrete entities referring to specifc other subclasses - as seen in ConcreteOther and ConcreteSelf. The test case "workingClasses" shows us that Hibernate may work with this model - note that the class AbstractGeneric itslef was NOT added to the configuration. Now for the problem: The class OtherEntity is a completly different entity, but it refers to instances of AbstractGeneric - to any subclass of it actually, as AbstractGeneric is obviously abstract. If you run the test case "otherClass" the first part states that Hibernate doesn't know AbstractGeneric - which is fine, so I add that class to the configuration and try to build a session factory again. Now we receive the beforementioned exception. That's the situation. So is AbstractGeneric really an unbound type? I'd say it is not - T has an upper bound which should be good enough to work with - we know the table and the PK... -- 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

17 years, 6 months

4
14
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues February 2007