May 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-5213) Add native SQL Boolean type to Ingres10Dialect

by Ray Fan (JIRA)

Add native SQL Boolean type to Ingres10Dialect ---------------------------------------------- Key: HHH-5213 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5213 Project: Hibernate Core Issue Type: Patch Components: core Affects Versions: 3.5.1 Environment: Hibernate 3.5.1 trunk rev 19194, Ingres 10.0.0 (a64.lnx/123) Reporter: Ray Fan Attachments: Ingres10Dialect.java.svn.diff Ingres 10 now supports a native boolean column data type. This patch enables support within the dialect. An instance of the DBMS has been made available on the machine at 80.241.73.38 with a connection URL of jdbc:ingres://80.241.73.38:X07/hibernate. Contact me for credentials. -- 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, 5 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3579) Support for PostgreSQL UUID data type

by Olivier Van Acker (JIRA)

Support for PostgreSQL UUID data type ------------------------------------- Key: HHH-3579 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3579 Project: Hibernate Core Issue Type: New Feature Components: core Affects Versions: 3.3.1 Reporter: Olivier Van Acker PostgreSQL has since version 8.3 UUID as data type nativly supported in the database. The only way to get this to work in Hibernate is to add <column name="id" sql-type="uuid"/> to your mappings file (or @columnDefinition via annotations) and create your own custom usertype (e.g. public class UUIDUserType implements UserType, Serializable {..} ) and map this to java.util.UUID worth mentioning is that java.util.UUID is only introduced in java 1.5 so there might be a backwards compatibility 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

14 years, 5 months

5
22
0 / 0

[Hibernate-JIRA] Created: (HHH-5204) Introduce @RequiresDialectFeature annotation

by Hardy Ferentschik (JIRA)

Introduce @RequiresDialectFeature annotation -------------------------------------------- Key: HHH-5204 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5204 Project: Hibernate Core Issue Type: Bug Components: testsuite Affects Versions: 3.5.1 Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 3.5.2 This will allow us to: * get rid of {{HibernateTestCase.runForCurrentDialect}} * handle skipping of tests more consistently At the same time we have to fix an issue {{HibernateTestCase.determineSkipByDialect}}. The logic in the if statement should be inverted. Last but not least we can get rid of some unused member variables -- 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, 5 months

3
8
0 / 0

[Hibernate-JIRA] Created: (HHH-5231) Unit test failures lock up when they run on DB2 and PostgreSQL

by Gail Badner (JIRA)

Unit test failures lock up when they run on DB2 and PostgreSQL -------------------------------------------------------------- Key: HHH-5231 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5231 Project: Hibernate Core Issue Type: Bug Components: testsuite Reporter: Gail Badner Assignee: Gail Badner Fix For: 3.5.x, 3.6 Unit test failures lock up when they run on DB2 and PostgreSQL. -- 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, 5 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5251) NativeSQLQueryReturn impls pre-cache a final hashcode based on non-final fields

by Steve Ebersole (JIRA)

NativeSQLQueryReturn impls pre-cache a final hashcode based on non-final fields -------------------------------------------------------------------------------- Key: HHH-5251 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5251 Project: Hibernate Core Issue Type: Improvement Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.6, 3.5.x For example, code such as {code} public class NativeSQLQueryScalarReturn implements NativeSQLQueryReturn { private Type type; private String columnAlias; private final int hashCode; public NativeSQLQueryScalarReturn(String alias, Type type) { this.type = type; this.columnAlias = alias; this.hashCode = determineHashCode(); } ... private int determineHashCode() { int result = type != null ? type.hashCode() : 0; result = 31 * result + ( getClass().getName().hashCode() ); result = 31 * result + ( columnAlias != null ? columnAlias.hashCode() : 0 ); return result; } public int hashCode() { return hashCode; } } {code} should really read as such (for correctness): {code} public class NativeSQLQueryScalarReturn implements NativeSQLQueryReturn { private final Type type; private final String columnAlias; private final int hashCode; public NativeSQLQueryScalarReturn(String alias, Type type) { this.type = type; this.columnAlias = alias; this.hashCode = determineHashCode(); } ... private int determineHashCode() { int result = type != null ? type.hashCode() : 0; result = 31 * result + ( getClass().getName().hashCode() ); result = 31 * result + ( columnAlias != null ? columnAlias.hashCode() : 0 ); return result; } public int hashCode() { return hashCode; } } {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

14 years, 5 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-5220) Unit tests related to HHH-5063 and HHH-5135 fail on some dialects

by Gail Badner (JIRA)

Unit tests related to HHH-5063 and HHH-5135 fail on some dialects ----------------------------------------------------------------- Key: HHH-5220 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5220 Project: Hibernate Core Issue Type: Bug Components: testsuite Affects Versions: 3.5.2 Reporter: Gail Badner Assignee: Gail Badner Fix For: 3.5.x, 3.6 The fixes for HHH-5063 and HHH-5135 are OK, but there are problems when using particular dialects. For example: http://hudson.qa.jboss.com/hudson/job/hibernate-core-branch35-testsuite/1... http://hudson.qa.jboss.com/hudson/job/hibernate-core-branch35-testsuite/1... There may be other dialects that are affected as well. -- 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, 5 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-2277) bidirectional <key-many-to-one> both lazy=false fetch=join lead to infinite loop

by Emmanuel Bernard (JIRA)

bidirectional <key-many-to-one> both lazy=false fetch=join lead to infinite loop -------------------------------------------------------------------------------- Key: HHH-2277 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2277 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.1 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, 5 months

2
14
0 / 0

[Hibernate-JIRA] Created: (HHH-2268) JDK Bug 5062759 Breaks Hibernate Introspection

by James Olsen (JIRA)

JDK Bug 5062759 Breaks Hibernate Introspection ---------------------------------------------- Key: HHH-2268 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2268 Project: Hibernate3 Type: Patch Components: core Versions: 3.2.0.ga Environment: n/a Reporter: James Olsen Priority: Blocker Attachments: patch.txt Class#getDeclaredMethods() returns inherited methods - see http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5062759 This can result in Hibernate failing to determine the correct return type for a method that overrides an inherited method and further constrains the return type. Behaviour is nondeterministic as it depends on the order of the returned array, e.g. public volatile java.lang.Object com.xxx.impl.CPMImpl.getId() // from interface implemented by superclass public volatile com.xxx.api.CPMId com.xxx.impl.CPMImpl.getId() // from superclass implementation public com.xxx.impl.CPMIdImpl com.xxx.impl.CPMImpl.getId() // local The patch checks if the method is 'volatile' and ignores it if it is. -- 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, 5 months

5
14
0 / 0

[Hibernate-JIRA] Created: (EJB-225) EntityManager.find infinite loop related to ANN-381

by John Schneider (JIRA)

EntityManager.find infinite loop related to ANN-381 --------------------------------------------------- Key: EJB-225 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-225 Project: Hibernate Entity Manager Type: Bug Environment: Hibernate Annotations 3.2.0.cr2 Hibernate EntityManager 3.2.0.cr2 Hibernate Core 3.2.0.cr4 Reporter: John Schneider Attachments: Test.zip I've tested the fix for ANN-381 and found that the improvement is not working correctly with the Entity Manager, specifically the find method. When calling the find method on a OneToMany collection mapped by a field in a primary key class, the Entity manager goes into an infinite loop of selecting records. Please note that a workaround is to replace the entity managers find method with a query, such as this: Query query = entityManager.createQuery("select c from Card c where c.id = :id"); query.setParameter("id", id); return (Card) query.getSingleResult(); However, this workaround doesn't work if you have other entities that relate to something like the Card entity, shown below. I'll expand on the example code from ANN-381 to show the problem of infinite looping when trying to load the related collection. @Entity public class Card implements Serializable { @Id private String id; @OneToMany(cascade = CascadeType.ALL, fetch = FetchType.EAGER, mappedBy = "primaryKey.card") private Set<CardField> fields; public Card(String id) { this(); this.id = id; } Card() { fields = new HashSet<CardField>(); } public String getId() { return id; } public void setId(String id) { this.id = id; } public void addField(Card card, Key key) { fields.add(new CardField(card, key)); } } @Entity public class CardField implements Serializable { @EmbeddedId private PrimaryKey primaryKey; CardField(Card card, Key key) { this.primaryKey = new PrimaryKey(card, key); } CardField() { } } @Embeddable public class PrimaryKey implements Serializable { @ManyToOne(optional = false) private Card card; @ManyToOne(optional = false) private Key key; public PrimaryKey(Card card, Key key) { this.card = card; this.key = key; } PrimaryKey() {} } @Entity public class Key implements Serializable { @Id private String id; public Key(String id) { this.id = id; } Key() { } } >From what I can tell, this maps fine with the correct Hibernate libs and JBoss EJB Embeddable Alpha 9. However, the Entity Manager must be creating bad query code or something with similar results to having bad queries. I've testing with the following DAO: @Stateless public class CardDAOBean implements CardDAOLocal { @PersistenceContext private EntityManager entityManager; public void createCard(Card card) { entityManager.persist(card); } public Card findCard(String id) { return entityManager.find(Card.class, id); } public void createKey(Key key) { entityManager.persist(key); } } The Test class: public class EJBTest { private Card card; private Key key; public static void main(String[] args) { TestRunner.run(suite()); } public static junit.framework.Test suite() { TestSuite suite = new TestSuite("Test for ANN-381"); suite.addTest(new JUnit4TestAdapter(EJBTest.class)); // setup test so that embedded JBoss is started/stopped once for all // tests here. TestSetup wrapper = new TestSetup(suite) { protected void setUp() { startupEmbeddedJboss(); } protected void tearDown() { shutdownEmbeddedJboss(); } }; return wrapper; } @Before public void setup() { card = new Card("cardId"); key = new Key("keyId"); card.addField(card, key); } @Test public void persist() throws Exception { InitialContext ctx = getInitialContext(); CardDAOLocal CardDAOLocal = (CardDAOLocal) ctx.lookup("CardDAOBean/local"); CardDAOLocal.createKey(key); CardDAOLocal.createCard(card); Card card = CardDAOLocal.findCard(this.card.getId()); assertNotNull(card); } private static void startupEmbeddedJboss() { EJB3StandaloneBootstrap.boot(null); EJB3StandaloneBootstrap.scanClasspath(); } private static void shutdownEmbeddedJboss() { EJB3StandaloneBootstrap.shutdown(); } public static InitialContext getInitialContext() throws Exception { Hashtable properties = getInitialContextProperties(); return new InitialContext(properties); } private static Hashtable getInitialContextProperties() { Hashtable<String, String> props = new Hashtable<String, String>(); props.put("java.naming.factory.initial", "org.jnp.interfaces.LocalOnlyContextFactory"); props.put("java.naming.factory.url.pkgs", "org.jboss.naming:org.jnp.interfaces"); return props; } } Here's some relevant debugging output: Row insert: update CardField set card_id=? where card_id=? and key_id=? Row delete: update CardField set card_id=null where card_id=? and card_id=? and key_id=? One-shot delete: update CardField set card_id=null where card_id=? Static select for entity entity.CardField: select cardfield0_.card_id as card2_1_0_, cardfield0_.key_id as key1_1_0_ from CardField cardfield0_ where cardfield0_.card_id=? and cardfield0_.key_id=? Static select for action ACTION_MERGE on entity entity.CardField: select cardfield0_.card_id as card2_1_0_, cardfield0_.key_id as key1_1_0_ from CardField cardfield0_ where cardfield0_.card_id=? and cardfield0_.key_id=? Static select for action ACTION_REFRESH on entity entity.CardField: select cardfield0_.card_id as card2_1_0_, cardfield0_.key_id as key1_1_0_ from CardField cardfield0_ where cardfield0_.card_id=? and cardfield0_.key_id=? Static select for entity entity.Card: select card0_.id as id0_1_, fields1_.card_id as card2_3_, fields1_.key_id as key1_3_, fields1_.card_id as card2_1_0_, fields1_.key_id as key1_1_0_ from Card card0_ left outer join CardField fields1_ on card0_.id=fields1_.card_id where card0_.id=? Static select for entity entity.Card: select card0_.id as id0_1_, fields1_.card_id as card2_3_, fields1_.key_id as key1_3_, fields1_.card_id as card2_1_0_, fields1_.key_id as key1_1_0_ from Card card0_ left outer join CardField fields1_ on card0_.id=fields1_.card_id where card0_.id=? Static select for entity entity.Card: select card0_.id as id0_0_ from Card card0_ where card0_.id=? Static select for entity entity.Card: select card0_.id as id0_0_ from Card card0_ where card0_.id=? Static select for entity entity.Card: select card0_.id as id0_0_ from Card card0_ where card0_.id=? Static select for action ACTION_MERGE on entity entity.Card: select card0_.id as id0_1_, fields1_.card_id as card2_3_, fields1_.key_id as key1_3_, fields1_.card_id as card2_1_0_, fields1_.key_id as key1_1_0_ from Card card0_ left outer join CardField fields1_ on card0_.id=fields1_.card_id where card0_.id=? Static select for action ACTION_REFRESH on entity entity.Card: select card0_.id as id0_1_, fields1_.card_id as card2_3_, fields1_.key_id as key1_3_, fields1_.card_id as card2_1_0_, fields1_.key_id as key1_1_0_ from Card card0_ left outer join CardField fields1_ on card0_.id=fields1_.card_id where card0_.id=? Static select for entity entity.Key: select key0_.id as id2_0_ from Key key0_ where key0_.id=? Static select for entity entity.Key: select key0_.id as id2_0_ from Key key0_ where key0_.id=? Static select for entity entity.Key: select key0_.id as id2_0_ from Key key0_ where key0_.id=? Static select for entity entity.Key: select key0_.id as id2_0_ from Key key0_ where key0_.id=? Static select for entity entity.Key: select key0_.id as id2_0_ from Key key0_ where key0_.id=? Static select for action ACTION_MERGE on entity entity.Key: select key0_.id as id2_0_ from Key key0_ where key0_.id=? Static select for action ACTION_REFRESH on entity entity.Key: select key0_.id as id2_0_ from Key key0_ where key0_.id=? Static select for one-to-many entity.Card.fields: select fields0_.card_id as card2_1_, fields0_.key_id as key1_1_, fields0_.card_id as card2_1_0_, fields0_.key_id as key1_1_0_ from CardField fields0_ where fields0_.card_id=? When I call the findCard method in my EJB, the entity manager keeps looping through the select process several hundred times, and then dies from a stack overflow. Here's a sample of looping: DEBUG 17-09 21:17:18,328 (Log4JLogger.java:debug:84) -select card0_.id as id0_1_, fields1_.card_id as card2_3_, fields1_.key_id as key1_3_, fields1_.card_id as card2_1_0_, fields1_.key_id as key1_1_0_ from Card card0_ left outer join CardField fields1_ on card0_.id=fields1_.card_id where card0_.id=? DEBUG 17-09 21:17:18,343 (Log4JLogger.java:debug:84) -about to open ResultSet (open ResultSets: 0, globally: 0) DEBUG 17-09 21:17:18,343 (Log4JLogger.java:debug:84) -loading entity: [entity.Card#cardId] DEBUG 17-09 21:17:18,359 (Log4JLogger.java:debug:84) -about to open PreparedStatement (open PreparedStatements: 1, globally: 1) DEBUG 17-09 21:17:18,359 (Log4JLogger.java:debug:84) -select card0_.id as id0_1_, fields1_.card_id as card2_3_, fields1_.key_id as key1_3_, fields1_.card_id as card2_1_0_, fields1_.key_id as key1_1_0_ from Card card0_ left outer join CardField fields1_ on card0_.id=fields1_.card_id where card0_.id=? DEBUG 17-09 21:17:18,359 (Log4JLogger.java:debug:84) -about to open ResultSet (open ResultSets: 1, globally: 1) DEBUG 17-09 21:17:18,359 (Log4JLogger.java:debug:84) -loading entity: [entity.Card#cardId] DEBUG 17-09 21:17:18,359 (Log4JLogger.java:debug:84) -about to open PreparedStatement (open PreparedStatements: 2, globally: 2) DEBUG 17-09 21:17:18,359 (Log4JLogger.java:debug:84) -select card0_.id as id0_1_, fields1_.card_id as card2_3_, fields1_.key_id as key1_3_, fields1_.card_id as card2_1_0_, fields1_.key_id as key1_1_0_ from Card card0_ left outer join CardField fields1_ on card0_.id=fields1_.card_id where card0_.id=? DEBUG 17-09 21:17:18,359 (Log4JLogger.java:debug:84) -about to open ResultSet (open ResultSets: 2, globally: 2) DEBUG 17-09 21:17:18,359 (Log4JLogger.java:debug:84) -loading entity: [entity.Card#cardId] DEBUG 17-09 21:17:18,359 (Log4JLogger.java:debug:84) -about to open PreparedStatement (open PreparedStatements: 3, globally: 3) DEBUG 17-09 21:17:18,375 (Log4JLogger.java:debug:84) -select card0_.id as id0_1_, fields1_.card_id as card2_3_, fields1_.key_id as key1_3_, fields1_.card_id as card2_1_0_, fields1_.key_id as key1_1_0_ from Card card0_ left outer join CardField fields1_ on card0_.id=fields1_.card_id where card0_.id=? DEBUG 17-09 21:17:18,375 (Log4JLogger.java:debug:84) -about to open ResultSet (open ResultSets: 3, globally: 3) DEBUG 17-09 21:17:18,375 (Log4JLogger.java:debug:84) -loading entity: [entity.Card#cardId] DEBUG 17-09 21:17:18,375 (Log4JLogger.java:debug:84) -about to open PreparedStatement (open PreparedStatements: 4, globally: 4) DEBUG 17-09 21:17:18,375 (Log4JLogger.java:debug:84) -select card0_.id as id0_1_, fields1_.card_id as card2_3_, fields1_.key_id as key1_3_, fields1_.card_id as card2_1_0_, fields1_.key_id as key1_1_0_ from Card card0_ left outer join CardField fields1_ on card0_.id=fields1_.card_id where card0_.id=? DEBUG 17-09 21:17:18,375 (Log4JLogger.java:debug:84) -about to open ResultSet (open ResultSets: 4, globally: 4) DEBUG 17-09 21:17:18,375 (Log4JLogger.java:debug:84) -loading entity: [entity.Card#cardId] -- 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, 5 months

8
23
0 / 0

[Hibernate-JIRA] Created: (HHH-5253) TableHiLoGenerator does not increment hi-value any more when lo-range es exhausted

by Martin Gubser (JIRA)

TableHiLoGenerator does not increment hi-value any more when lo-range es exhausted ---------------------------------------------------------------------------------- Key: HHH-5253 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5253 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.2, 3.5.1 Environment: Hibernate 3.5.2, DB2 v9.7 Reporter: Martin Gubser Attachments: A.java, HiLoTest.java The {{TableHiLoGenerator}} increments the lo value when it first gets a lo-range but not any more when it grabs further lo-ranges. The first run of the attached program leaves the hi-value=1. Consequently on the second run it uses an id that has already been assigned to. -- 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, 5 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues May 2010