January 2007 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (ANN-411) @Generated(INSERT) properties does not update columns

by Emmanuel Bernard (JIRA)

@Generated(INSERT) properties does not update columns ----------------------------------------------------- Key: ANN-411 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-411 Project: Hibernate Annotations Type: Bug Components: binder Versions: 3.2.0.cr1 Reporter: Emmanuel Bernard Assigned to: Emmanuel Bernard Fix For: 3.2.0 -- 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, 2 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HBX-851) MySQL primary keys are not completely detected

by Zeljko Trogrlic (JIRA)

MySQL primary keys are not completely detected ---------------------------------------------- Key: HBX-851 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-851 Project: Hibernate Tools Type: Bug Components: reverse-engineer Versions: 3.2beta10 Environment: JBoss Seam 1.1.0.GA with MySQL 5 Reporter: Zeljko Trogrlic Attachments: MySqlMetaDataDialect.java Due to bug in MySQL JDBC driver, tools detects only int primary keys and not other types, like varchar. This can be fixed with MySQL specific MetaDataDialect - fix attached. -- 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, 2 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2343) SchemaUpdate and c3p0 connection pool too many connections

by Vlad Skarzhevskyy (JIRA)

SchemaUpdate and c3p0 connection pool too many connections ---------------------------------------------------------- Key: HHH-2343 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2343 Project: Hibernate3 Type: Bug Components: build Versions: 3.2.1 Environment: hibernate 3.2.1.ga, hibernate-annotations, oracle ojdbc14_g 10.2.0.2, c3p0 0.9.0 or 0.9.0.4, Sun Java 1.5.0.10, Win XP. Reporter: Vlad Skarzhevskyy - I have application, configured to use c3p0 as connection pool <property name="c3p0.max_size">2</property> - When SchemaUpdate is enabled <property name="hibernate.hbm2ddl.auto">update</property> Application (hibernate) creates ~100 connections to database and c3p0 pool initialized 42 times. (looks like number of entities in my domain) There are no problems like this in hibernate 3.2.0.ga I see this log statement 42 times in log INFO Initializing c3p0 pool... com.mchange.v2.c3p0.PoolBackedDataSource@15a4a77 [ ... initialPoolSize -> 2, ... maxPoolSize -> 2, ] INFO 2007-01-04 13:39:55,796 2031- [..] [C3P0Registry.banner:77] com.mchange.v2.c3p0.C3P0Registry.banner(C3P0Registry.java:77) [main] Initializing c3p0-0.9.0.4 [built 23-January-2006 22:20:29 -0500; debug? true; trace: 10] INFO 2007-01-04 13:39:56,093 2328- [..] [PoolBackedDataSource.getPoolManager:257] com.mchange.v2.c3p0.PoolBackedDataSource.getPoolManager(PoolBackedDataSource.java:257) [main] Initializing c3p0 pool... com.mchange.v2.c3p0.PoolBackedDataSource@bc312f [ connectionPoolDataSource -> com.mchange.v2.c3p0.WrapperConnectionPoolDataSource@5f1ba8 [ acquireIncrement -> 1, acquireRetryAttempts -> 30, acquireRetryDelay -> 1000, autoCommitOnClose -> false, automaticTestTable -> null, breakAfterAcquireFailure -> false, checkoutTimeout -> 0, connectionTesterClassName -> com.mchange.v2.c3p0.impl.DefaultConnectionTester, factoryClassLocation -> null, forceIgnoreUnresolvedTransactions -> false, identityToken -> 5f1ba8, idleConnectionTestPeriod -> 3000, initialPoolSize -> 2, maxIdleTime -> 5000, maxPoolSize -> 2, maxStatements -> 100, maxStatementsPerConnection -> 0, minPoolSize -> 2, nestedDataSource -> com.mchange.v2.c3p0.DriverManagerDataSource@13c4c09 [ description -> null, driverClass -> null, factoryClassLocation -> null, identityToken -> 13c4c09, jdbcUrl -> jdbc:oracle:thin:@torvspocapp:1522:ENT10, properties -> {user=******, password=******} ], preferredTestQuery -> null, propertyCycle -> 300, testConnectionOnCheckin -> false, testConnectionOnCheckout -> false, usesTraditionalReflectiveProxies -> false ], factoryClassLocation -> null, identityToken -> bc312f, numHelperThreads -> 3 ] ...... And so on 42 times. hibernate.cfg.xml ---- <property name="hibernate.connection.pool_size">0</property> <property name="c3p0.acquire_increment">1</property> <property name="c3p0.min_size">2</property> <property name="c3p0.max_size">2</property> <property name="c3p0.timeout">5000</property> <property name="c3p0.idle_test_period">3000</property> <property name="c3p0.max_statements">100</property> <property name="hibernate.hbm2ddl.auto">update</property> <property name="hibernate.bytecode.use_reflection_optimizer">false</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

17 years, 2 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HHH-2306) put() fails on lazy one-to-many Map

by Andreas Idl (JIRA)

put() fails on lazy one-to-many Map ----------------------------------- Key: HHH-2306 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2306 Project: Hibernate3 Type: Bug Versions: 3.2.0.ga, 3.2.1 Environment: HIbernate 3.2.1. with Mysql 4 Reporter: Andreas Idl Priority: Critical Attachments: MapTest.zip If I add n objects to a lazy-loaded one-to-many map, the first added object is not contained afterwards. The size of the map is (n-1). Document document = (Document) session.load(Document.class,documentId); DocumentHistory history = new DocumentHistory(); history.setVersion(1); history.setTitle(document.getTitle()); history.setContent(document.getContent()); history.setDocument(document); // Put the new history into the map. Map<Integer, DocumentHistory> histories = document.getHistories(); histories.put(history.getVersion(), history); //not equal because histories.size() is 0 assertEquals(1, histories.size()); -- 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, 2 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HBX-819) NullPointerException in simple case with one configuration file and two console configurations

by Francois Granade (JIRA)

NullPointerException in simple case with one configuration file and two console configurations ---------------------------------------------------------------------------------------------- Key: HBX-819 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-819 Project: Hibernate Tools Type: Bug Components: consoleconfiguration Versions: 3.2beta8 Environment: macos, hsqldb Reporter: Francois Granade Priority: Minor I'm having an NullPointerException (See the stack below), I'm not really able to understand what triggers it (it is not completely reproducible, it seems). My setup is very simple: just one Java project, one hibernate configuration file, two console configurations, nothing else. The only thing that's a little special, is that one of the console configuration is invalid (no driver jar file defined). I'll try to describe it as precisely as possible: - I have a very simple HSQLDB server, just out-of-the box. I have created only one table with: "create table x (a varchar(255), b int)". - I created an Hibernate configuration file for the HSQLDB database using "File > New > Others", "Hibernate > Hibernate configuration file"; I specified "create a console configuration", and I gave a name to the Console Configuration, but I didn't set any other property (in particular, I did not specify the .jar file for hsqldb: so it's not a correctly defined console configuration) - Then I created a second console configuration; That time, in the 'classpath' section at the bottom, I selected 'add external jar' and added my 'hsqldb.jar'. - I can now open the HSQL DB correctly in the Hibernate Configuration view, with this second console configuration (the first one is doing an error, which is normal). - now, time to time, when I right-click on the definition of my table ('X"), and select "HQL Editor", I sometimes get the NullPointerException (but not always). here's the stack trace: !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.ui.workbench". !STACK 0 java.lang.NullPointerException at java.util.TreeMap.compare(TreeMap.java:1093) at java.util.TreeMap.getEntry(TreeMap.java:347) at java.util.TreeMap.get(TreeMap.java:265) at org.hibernate.console.KnownConfigurations.find(KnownConfigurations.java:225) at org.hibernate.eclipse.console.AbstractQueryEditor.getConsoleConfiguration(AbstractQueryEditor.java:51) at org.hibernate.eclipse.console.views.DynamicSQLPreviewView.updateText(DynamicSQLPreviewView.java:137) at org.hibernate.eclipse.console.views.DynamicSQLPreviewView.setCurrentEditor(DynamicSQLPreviewView.java:130) at org.hibernate.eclipse.console.views.DynamicSQLPreviewView.hookIntoEditor(DynamicSQLPreviewView.java:114) at org.hibernate.eclipse.console.views.DynamicSQLPreviewView.access$2(DynamicSQLPreviewView.java:107) at org.hibernate.eclipse.console.views.DynamicSQLPreviewView$1.partBroughtToTop(DynamicSQLPreviewView.java:92) at org.eclipse.ui.internal.PartListenerList2$2.run(PartListenerList2.java:83) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.runtime.Platform.run(Platform.java:843) at org.eclipse.ui.internal.PartListenerList2.fireEvent(PartListenerList2.java:53) at org.eclipse.ui.internal.PartListenerList2.firePartBroughtToTop(PartListenerList2.java:81) at org.eclipse.ui.internal.PartService.firePartBroughtToTop(PartService.java:90) at org.eclipse.ui.internal.WWinPartService$1.partBroughtToTop(WWinPartService.java:40) at org.eclipse.ui.internal.PartListenerList2$2.run(PartListenerList2.java: -- 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, 3 months

2
1
0 / 0

[Hibernate-JIRA] Created: (ANN-510) @EAN

by Emmanuel Bernard (JIRA)

@EAN ---- Key: ANN-510 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-510 Project: Hibernate Annotations Type: New Feature Components: validator Reporter: Emmanuel Bernard Assigned to: Emmanuel Bernard Priority: Minor Fix For: 3.2.2 -- 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, 3 months

5
6
0 / 0

[Hibernate-JIRA] Created: (ANN-508) @CreditCardNumber for Hibernate Validator

by Gavin King (JIRA)

@CreditCardNumber for Hibernate Validator ----------------------------------------- Key: ANN-508 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-508 Project: Hibernate Annotations Type: New Feature Components: validator Reporter: Gavin King Assigned to: Emmanuel Bernard Fix For: 3.2.2 I just dicovered the existence of the Luhn algorithm ;-) Very cool. http://en.wikipedia.org/wiki/Luhn_algorithm Here is a Java impl: http://www.darkcanyongroup.com/code/luhn_algorithm.txt We should have a built-in validator for 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

17 years, 3 months

7
7
0 / 0

[Hibernate-JIRA] Created: (HHH-2397) hilo generator can generate negative numbers because of arithmetic overflow

by Steve Ebersole (JIRA)

hilo generator can generate negative numbers because of arithmetic overflow --------------------------------------------------------------------------- Key: HHH-2397 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2397 Project: Hibernate3 Type: Bug Components: core Reporter: Steve Ebersole Assigned to: Steve Ebersole Fix For: 3.2.3 org.hibernate.id.TableHiLoGenerator#generate can potentially generate negative numbers because of the possibility of overflow due to the handling of the "clock over" multiplication using int multiplication. The solution is to force one of the operands to type long. -- 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, 3 months

2
3
0 / 0

[Hibernate-JIRA] Created: (EJB-261) merge fails to update join table

by Bryan Hunt (JIRA)

merge fails to update join table -------------------------------- Key: EJB-261 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-261 Project: Hibernate Entity Manager Type: Bug Components: EntityManager Versions: 3.2.1 Environment: Embedded entity manager 3.2.1 with DB2 or MySQL Reporter: Bryan Hunt Priority: Blocker Doing a merge on an entity with a one to many relationship does not update the join table. I have the following entities: @Entity public class Foo { ... @OneToMany(cascade = CascadeType.ALL) private Set<Bar> bars; } @Entity public class Bar { ... } The following works: Foo foo = new Foo(); Bar bar = new Bar(); foo.getBars().add(bar); em.getTransaction().begin(); em.persist(foo); // <<----------------- correctly updates the join table em.getTransaction().commit(); This also works: Foo foo = em.find(Foo.class, id); Bar bar = new Bar(); foo.getBars().add(bar); em.getTransaction().begin(); em.persist(bar); em.merge(foo); // <<----------------- correctly updates the join table em.getTransaction().commit(); When this code executes the new Foo and Bar are persisted to the database, an entry is made into the join table, and all is well. The following fails: Foo foo = em.find(Foo.class, id); Bar bar = new Bar(); foo.getBars().add(bar); em.getTransaction().begin(); em.merge(foo); // <<----------------- does not update the join table em.getTransaction().commit(); When this code executes, the new Bar is persisted to the database, but the join table is not updated. -- 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, 3 months

2
11
0 / 0

[Hibernate-JIRA] Created: (HHH-2373) Merging a persistent object leads to cascading failure in collections

by Emmanuel Bernard (JIRA)

Merging a persistent object leads to cascading failure in collections --------------------------------------------------------------------- Key: HHH-2373 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2373 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.1 Reporter: Emmanuel Bernard class Empire { ... @OneToMany(cascade.ALL) public Set<Colony> colonies; } Then roman = (Empire) em.get( Empire.class, roman.getId() ); Colony gaule = new Colony(); roman.getColonies().add(gaule); em.merge( roman ); //If commented, will work em.flush(); em.clear(); roman =(Empire) em.get(Empire.class, roman.getId() ); assertEquals( 1, roman.getColonies().size() ); I believe the issue is about having a persistent copy of gaule (according to the merge API), not part of roman.getColonies() (colonies containing the transient gaule object) -- 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, 3 months

1
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues January 2007