June 2009 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-3256) OptimizerFactory$PooledOptimizer.generate doesn't set keep the in-memory hi_value in sync with the db next_val (after a JBoss restart)

by Tom Muldoon (JIRA)

OptimizerFactory$PooledOptimizer.generate doesn't set keep the in-memory hi_value in sync with the db next_val (after a JBoss restart) -------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-3256 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3256 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.6 Environment: Hibernate 3.2.6, MySQL 5 Reporter: Tom Muldoon After a JBoss restart, the in-memory hiValue is -1. As such, the callback.getNextValue( ) method is invoked twice. With an increment size of 50 and a current database next_val of 10000, the PooledOptimizer.generate method returns a value of 10000 (as expected) and sets the in memory hiValue to 10050 (also as expected), however, it sets the db next_val to 10100. Shouldn't the db next_val be kept in sync with the in-memory hiValue (i.e. 10050)? -- 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, 8 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-324) @DynamicBoost(BoostStrategy.class)

by Emmanuel Bernard (JIRA)

@DynamicBoost(BoostStrategy.class) ---------------------------------- Key: HSEARCH-324 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-324 Project: Hibernate Search Issue Type: New Feature Components: mapping Reporter: Emmanuel Bernard Fix For: 3.1.1, 3.2.0 This sounds like an interesting feature. We could do something very similar to the new AnalyzerDiscriminator approach. The use case is explained http://saloon.javaranch.com/cgi-bin/ubb/ultimatebb.cgi?ubb=get_topic&f=78... Need some analysis before the jump We can do that in 3.1.1, but no hard pressure. -- 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, 8 months

4
9
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-333) Remove or improve log warning in DocumentBuilderContainedEntity.checkDocumentId

by Hardy Ferentschik (JIRA)

Remove or improve log warning in DocumentBuilderContainedEntity.checkDocumentId ------------------------------------------------------------------------------- Key: HSEARCH-333 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-333 Project: Hibernate Search Issue Type: Bug Components: engine Affects Versions: 3.1.0.GA Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 3.1.1 http://forum.hibernate.org/viewtopic.php?t=993097 -- 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, 8 months

3
7
0 / 0

[Hibernate-JIRA] Created: (HHH-1992) Some cascade actions should not trigger a property access on lazy properties

by Emmanuel Bernard (JIRA)

Some cascade actions should not trigger a property access on lazy properties ---------------------------------------------------------------------------- Key: HHH-1992 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1992 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.cr3 Reporter: Emmanuel Bernard Assigned to: Emmanuel Bernard Priority: Critical Fix For: 3.2.0.ga -- 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, 8 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3107) Error with sql generated for set of subclass A in a peer subclass B.

by Austin Mayberry (JIRA)

Error with sql generated for set of subclass A in a peer subclass B. -------------------------------------------------------------------- Key: HHH-3107 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3107 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.6 Reporter: Austin Mayberry A mapping such as the following contrived examples does not yield the expected results and causes and error: <class name="com.foo.Foo1" table="FOO1"> <id name="id" type="java.lang.Integer" column="ID" > <generator class="sequence" > <param name="sequence">ID_SEQ</param> </generator> </id> <discriminator column="FOO_TYPE_ID" type="java.lang.Integer"/> <subclass name="com.foo.Foo2" discriminator-value="0"> <join table="FOO2"> <key column="ID"/> <property name="label" type="java.lang.String" column="LABEL" not-null="true" length="255" /> </join> <subclass name="com.foo.BarOne" discriminator-value="1"> <set name="barTwos" inverse="true" > <key> <column name="PARENT_ID" /> </key> <one-to-many class="com.foo.BarTwo" /> </set> </subclass> <subclass name="com.foo.BarTwo" discriminator-value="2"> <join table="BAR"> <key column="ID"/> <many-to-one name="parent" class="com.foo.BarOne" not-null="true" column="PARENT_ID" /> </join> </subclass> </subclass> </class> The sql created to populate the set "bartwos" looks like this looks like: select bartwos0_.PARENT_ID as PA3_1_, bartwos0_.ID as ID1_1_, bartwos0_.ID as ID1_52_0_, bartwos0_.FOO_TYPE_ID as FO2_52_0_, bartwos0_1_.LABEL as LABEL76_0_, bartwos0_2_.PARENT_ID as PA2_87_0_ from FOO1 bartwos0_, FOO2 bartwos0_1_, BAR2 bartwos0_2_ where bartwos0_.ID=bartwos0_1_.ID and bartwos0_.ID=bartwos0_2_.ID and bartwos0_.PARENT_ID=? And yields the following error message: java.sql.SQLException: ORA-00904: "BARTWOS0_"."PARENT_ID: invalid identifier The basic problem is that it should be looking for the property PARENT_ID on BAR2, but it is looking for it on FOO1. -- 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, 8 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3752) Error with sql generated for set of subclass A in a peer subclass B.

by Austin Mayberry (JIRA)

Error with sql generated for set of subclass A in a peer subclass B. -------------------------------------------------------------------- Key: HHH-3752 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3752 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1, 3.3.0.SP1, 3.3.0.GA, 3.3.0.CR2, 3.3.0.CR1, 3.2.6, 3.2.5, 3.2.4.sp1, 3.2.4, 3.2.x, 3.3.x Reporter: Austin Mayberry A mapping such as the following contrived examples does not yield the expected results and causes and error: <class name="com.foo.Foo1" table="FOO1"> <id name="id" type="java.lang.Integer" column="ID" > <generator class="sequence" > <param name="sequence">ID_SEQ</param> </generator> </id> <discriminator column="FOO_TYPE_ID" type="java.lang.Integer"/> <subclass name="com.foo.Foo2" discriminator-value="0"> <join table="FOO2"> <key column="ID"/> <property name="label" type="java.lang.String" column="LABEL" not-null="true" length="255" /> </join> <subclass name="com.foo.BarOne" discriminator-value="1"> <set name="barTwos" inverse="true" > <key> <column name="PARENT_ID" /> </key> <one-to-many class="com.foo.BarTwo" /> </set> </subclass> <subclass name="com.foo.BarTwo" discriminator-value="2"> <join table="BAR"> <key column="ID"/> <many-to-one name="parent" class="com.foo.BarOne" not-null="true" column="PARENT_ID" /> </join> </subclass> </subclass> </class> The sql created to populate the set "bartwos" looks like this looks like: select bartwos0_.PARENT_ID as PA3_1_, bartwos0_.ID as ID1_1_, bartwos0_.ID as ID1_52_0_, bartwos0_.FOO_TYPE_ID as FO2_52_0_, bartwos0_1_.LABEL as LABEL76_0_, bartwos0_2_.PARENT_ID as PA2_87_0_ from FOO1 bartwos0_, FOO2 bartwos0_1_, BAR2 bartwos0_2_ where bartwos0_.ID=bartwos0_1_.ID and bartwos0_.ID=bartwos0_2_.ID and bartwos0_.PARENT_ID=? And yields the following error message: java.sql.SQLException: ORA-00904: "BARTWOS0_"."PARENT_ID: invalid identifier The basic problem is that it should be looking for the property PARENT_ID on BAR2, but it is looking for it on FOO1. I am refiling this bug because I originally only filed agains 3.2.4. It has been a year with no comments on it so I a resubmitting for all affected versions I have tried. -- 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, 8 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3748) foreign key attributed to wrong table when table for subclass with inheritance model is used

by Paul Pogonyshev (JIRA)

foreign key attributed to wrong table when table for subclass with inheritance model is used -------------------------------------------------------------------------------------------- Key: HHH-3748 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3748 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1, 3.4 Environment: Tested with 3.3.1.GA + Oracle and 3.4 (trunk) + hsqldb. Reporter: Paul Pogonyshev Attachments: test.diff When a collection of inherited objects (using table per subclass with discriminator model) is mapped, foreign key is always attributed to the base class table, not inherited class table. This means fields in inherited class tables are _unusable_ as keys for collections, or at least I don't see any way to use them. This is a workaroundable issue for new databases (you could move the field to the base table, even if this is suboptimal), but a blocker for interfacing already existing database schemas. I tried to create a testcase for this, attached is a diff against trunk. The test doesn't visibly fail, because I do not know how to check which table it references. However, you can see in ASTParserLoadingTest-output.txt: create table DIBase ( id bigint generated by default as identity (start with 1), type varchar(255) not null, container bigint, primary key (id) ) create table DISubclass1 ( id bigint not null, container bigint, primary key (id) ) I.e. field 'container' ends up in both base and derived class tables. Second is because of the 'many-to-one'. First is because foreign key from 'children' bag is attributed to a wrong table: instead, Hibernate should reuse the column in DISubclass1 table. Might be related to issue 3500. -- 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, 8 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3005) DTD: map-key should allow nested type rather than attribute.

by Mattias Jiderhamn (JIRA)

DTD: map-key should allow nested type rather than attribute. ------------------------------------------------------------ Key: HHH-3005 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3005 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.5 Reporter: Mattias Jiderhamn Priority: Minor The metamodel allows for user typed 'map-key's via nested <type> tags but the DTD requires a type, attribute. See HHH-822 for a similar problem with key-property. -- 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, 8 months

4
6
0 / 0

[Hibernate-JIRA] Created: (HHH-2584) PersistentMap.remove() incorrect on uninitialized, non-extra-lazy map

by Daniel Wellman (JIRA)

PersistentMap.remove() incorrect on uninitialized, non-extra-lazy map --------------------------------------------------------------------- Key: HHH-2584 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2584 Project: Hibernate3 Issue Type: Patch Components: core Affects Versions: 3.2.3, 3.2.2, 3.2.1 Environment: Hibernate 3.2.3 ga, MySQL 5.0.24a, for Win32 Reporter: Daniel Wellman Attachments: persistentmap_remove.patch This problem is nearly identical to HHH-2476: PersistentMap.put() incorrect on uninitialized, non-extra-lazy map. remove() has the same problem. See also issue HHH-2142. The write up for HHH-2476 was so concise that I will transform it here, substituting remove() for put(). --- Essentially, an uninitialized PersistentMap loses the first remove() into it if defined as non-extra-lazy. The underlying cause is the code in PersistentMap#remove() which attempts to readElementByIndex(). In the case of non-extra-lazy, readElementByIndex() returns the UNKNOWN marker object which is supposed to be used to signal that the delegate map is now initialized and to remove the element directly from the map. Long story short, PersistentMap#remove() does not properly check the return value from readElementByIndex() and react accordingly. -- 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, 8 months

8
12
0 / 0

[Hibernate-JIRA] Created: (HV-156) Exploring properties and cascade is unnecessary if TraversableResolver returns false

by Emmanuel Bernard (JIRA)

Exploring properties and cascade is unnecessary if TraversableResolver returns false ------------------------------------------------------------------------------------ Key: HV-156 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-156 Project: Hibernate Validator Issue Type: Improvement Reporter: Emmanuel Bernard This will likely optimize the engine. not at urgent though since HV-155 -- 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, 8 months

2
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues June 2009