October 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (ANN-603) Using @CollectionOfEelements with FetchMode.JOIN and FetchType.EAGER to map a Map breaks Example criteria

by Philippe Laflamme (JIRA)

Using @CollectionOfEelements with FetchMode.JOIN and FetchType.EAGER to map a Map breaks Example criteria --------------------------------------------------------------------------------------------------------- Key: ANN-603 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-603 Project: Hibernate Annotations Issue Type: Bug Components: search Affects Versions: 3.3.0.ga Environment: hibernate-core-3.2.2.jar Reporter: Philippe Laflamme Attachments: ann-example_eager_join.patch I'm using CollectionOfElements to map a Map<String, @Embeddable>. I want it to eagerly join the associated table to fill the map. When I load the Entity using its PK, I obtain a single object with multiple entries in the Map, which is the expected behaviour. If I load the same Entity using an Example criteria (matching one of its property), I get one Entity per entry in the Map. If you use FetchMode.SELECT, the resulting Example query returns a single entity with multiple values in the Map (expected behaviour). Attached is a patch against annotations_3_3_0_GA that creates a test case in CollectionElementTest that reproduces 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

16 years, 11 months

4
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3548) "group by" does work when it contains function with named parameters

by Santtu Virolainen (JIRA)

"group by" does work when it contains function with named parameters -------------------------------------------------------------------- Key: HHH-3548 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3548 Project: Hibernate Core Issue Type: Bug Components: query-sql Affects Versions: 3.2.6 Environment: Hibernate 3.2.6.ga Oracle Database 10g Express Edition Reporter: Santtu Virolainen Following query throws SQLGrammarException: String sql = "select count(distinct foo.ID) c " + " , least(foo.AMOUNT, :amount) a " + " , :amount " + " from FOO foo " + "group by least(foo.AMOUNT, :amount) " + " , :amount "; SQLQuery query = getSession().createSQLQuery(sql); query.setParameter("amount", 1); query.list(); org.hibernate.exception.SQLGrammarException: could not execute query at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:67) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) at org.hibernate.loader.Loader.doList(Loader.java:2216) at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2104) at org.hibernate.loader.Loader.list(Loader.java:2099) at org.hibernate.loader.custom.CustomLoader.list(CustomLoader.java:289) at org.hibernate.impl.SessionImpl.listCustomQuery(SessionImpl.java:1695) at org.hibernate.impl.AbstractSessionImpl.list(AbstractSessionImpl.java:142) at org.hibernate.impl.SQLQueryImpl.list(SQLQueryImpl.java:152) ... Caused by: java.sql.SQLSyntaxErrorException: ORA-00979: not a GROUP BY expression at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:91) at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:112) at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:173) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:455) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:413) at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:1030) at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:194) at oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(T4CPreparedStatement.java:785) at oracle.jdbc.driver.T4CPreparedStatement.executeMaybeDescribe(T4CPreparedStatement.java:860) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1186) at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3381) at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3425) at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeQuery(OraclePreparedStatementWrapper.java:1490) at org.hibernate.jdbc.AbstractBatcher.getResultSet(AbstractBatcher.java:186) at org.hibernate.loader.Loader.getResultSet(Loader.java:1787) at org.hibernate.loader.Loader.doQuery(Loader.java:674) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:236) at org.hibernate.loader.Loader.doList(Loader.java:2213) ... 43 more -- 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

16 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3351) Dynamic entity model and inheritance - exception when trying to persist

by Adam Warski (JIRA)

Dynamic entity model and inheritance - exception when trying to persist ----------------------------------------------------------------------- Key: HHH-3351 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3351 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.6 Reporter: Adam Warski I have two dynamic model entites mapped as follows: <?xml version="1.0"?> <!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD 3.0//EN" "http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd"> <hibernate-mapping> <class entity-name="Superclass" discriminator-value="A"> <id name="id" type="integer"><generator class="native"/></id> <discriminator column="DISC" type="string" /> <property name="dataA" type="string"/> <subclass entity-name="Subclass" discriminator-value="B"> <property name="dataB" type="string"/> </subclass> </class> </hibernate-mapping> When I try to persist one of them (just invoking session.persist("Superclass", new HashMap()); is enough) I get the following exception: Exception in thread "main" org.hibernate.HibernateException: instance not of expected entity type: java.util.HashMap is not a: Superclass at org.hibernate.persister.entity.AbstractEntityPersister.getSubclassEntityPersister(AbstractEntityPersister.java:3640) at org.jboss.envers.test.working.MyPersister.getSubclassEntityPersister(MyPersister.java:22) at org.hibernate.impl.SessionImpl.getEntityPersister(SessionImpl.java:1347) at org.hibernate.engine.ForeignKeys.isTransient(ForeignKeys.java:180) at org.hibernate.event.def.AbstractSaveEventListener.getEntityState(AbstractSaveEventListener.java:512) at org.hibernate.event.def.DefaultPersistEventListener.onPersist(DefaultPersistEventListener.java:70) at org.hibernate.event.def.DefaultPersistEventListener.onPersist(DefaultPersistEventListener.java:38) at org.hibernate.impl.SessionImpl.firePersist(SessionImpl.java:618) at org.hibernate.impl.SessionImpl.persist(SessionImpl.java:592) at org.jboss.envers.test.working.WorkingMain.main(WorkingMain.java:62) -- 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

16 years, 11 months

2
1
0 / 0

[Hibernate-JIRA] Created: (EJB-300) create-drop with c3p0 causes SQLException

by Chris Redekop (JIRA)

create-drop with c3p0 causes SQLException ----------------------------------------- Key: EJB-300 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-300 Project: Hibernate Entity Manager Issue Type: Bug Components: EntityManager Affects Versions: 3.2.1 Environment: hibernate-entitymanager 3.2.1.ga, c3p0 0.9.0, and postgreSQL 8.1.8 or hsqldb 1.8.7 Reporter: Chris Redekop Attachments: c3p0Test.tar.gz In the attached test application, an EntityManagerFactory is created and then closed. Closing the EMF causes line 801 of org.hibernate.impl.SessionFactoryImpl to call getConnectionProvider().close(), which eventually results in c3p0's PooledDataSource being closed. Line 808 of org.hibernate.impl.SessionFactoryImpl the calls schemaExport.drop(), which attempts to acquire a connection from the data source and causes the following SQLException. java.sql.SQLException: com.mchange.v2.c3p0.PoolBackedDataSource@fced4 [ connectionPoolDataSource -> com.mchange.v2.c3p0.WrapperConnectionPoolDataSource@9505f [ 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 -> 9505f, idleConnectionTestPeriod -> 100, initialPoolSize -> 10, maxIdleTime -> 100, maxPoolSize -> 100, maxStatements -> 0, maxStatementsPerConnection -> 0, minPoolSize -> 10, nestedDataSource -> com.mchange.v2.c3p0.DriverManagerDataSource@80cac9 [ description -> null, driverClass -> null, factoryClassLocation -> null, identityToken -> 80cac9, jdbcUrl -> jdbc:hsqldb:., properties -> {user=******, password=******, autocommit=true, release_mode=auto} ], preferredTestQuery -> null, propertyCycle -> 300, testConnectionOnCheckin -> false, testConnectionOnCheckout -> false, usesTraditionalReflectiveProxies -> false ], factoryClassLocation -> null, identityToken -> fced4, numHelperThreads -> 3 ] has been closed() -- you can no longer use it. This exception is swallowed so it does not cause a test error, but it does appear in the console output. -- 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

16 years, 11 months

7
13
0 / 0

[Hibernate-JIRA] Commented: (HBX-629) JSP fields out of order when using the Seam CRUD generator with annotated EJB3 entities

by Max Rydahl Andersen (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-629?page=co... ] Max Rydahl Andersen commented on HBX-629: ----------------------------------------- it affects native queries + it will give non-reproducable queries across clusters. > JSP fields out of order when using the Seam CRUD generator with annotated EJB3 entities > --------------------------------------------------------------------------------------- > > Key: HBX-629 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-629 > Project: Hibernate Tools > Issue Type: Bug > Environment: The version of Hibernate and Hibernate Tools that is packaged with JBoss Seam 1.0 Beta 2 > Reporter: Bruce Raggett > Priority: Minor > Fix For: 3.1.beta5 > > > If you use annotated EJB3 entities to generate a Seam CRUD application, then the generated JSPs are not really usable as the order of the fields in the generated JSPs is different from the order of the fields in the annotated EJB3 entities. This means that you have to manually edit the generated JSPs to get the fields into the correct order. > This issue seems to exist whether the process used to generate the CRUD application is > (a) generate a database schema from the annotated entities and then generate the CRUD application from the generated schema, or > (b) generate the CRUD application directly from the annotated entities. -- 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

16 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1100) Invalidate cache on StaleObjectStateException

by Nico De Groote (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1100?page=c... ] Nico De Groote commented on HHH-1100: ------------------------------------- Been upgrading to Hibernate 3.3.1.GA and had to fix this one again...... Now I did the following update in the execute method of my EntityUpdateAction class. try{ persister.update(id, state, dirtyFields, hasDirtyCollection, previousState, previousVersion, instance, rowId, session); } catch (StaleObjectStateException ex){ if (hasCache){ ((Session)session).evict(instance); } throw ex; } > Invalidate cache on StaleObjectStateException > ---------------------------------------------- > > Key: HHH-1100 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1100 > Project: Hibernate Core > Issue Type: Improvement > Components: core > Reporter: Gavin King > Assignee: Gavin King > Priority: Critical > > We should probably invalidate the second-level cache when a StaleObjectStateException occurs. Need to think this through. -- 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

16 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-292) Document the new Filter caching approach

by Emmanuel Bernard (JIRA)

Document the new Filter caching approach ---------------------------------------- Key: HSEARCH-292 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-292 Project: Hibernate Search Issue Type: Task Components: documentation Reporter: Emmanuel Bernard Fix For: 3.1.0.Beta2 -- 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

16 years, 11 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2820) Can not set HOLD_CURSORS_OVER_COMMIT when creating ScrollableResults

by steven (JIRA)

Can not set HOLD_CURSORS_OVER_COMMIT when creating ScrollableResults -------------------------------------------------------------------- Key: HHH-2820 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2820 Project: Hibernate3 Issue Type: Improvement Components: core Affects Versions: 3.2.5 Environment: N/A Reporter: steven Currently, I can not set HOLD_CURSORS_OVER_COMMIT when creating ScrollableResults. It seams that the method in Query: public ScrollableResults scroll(ScrollMode scrollMode) throws HibernateException; should be added with the second argument: ResultSet holdability. -- 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

16 years, 11 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-287) master.xml is mistakenly copied to the distribution

by Emmanuel Bernard (JIRA)

master.xml is mistakenly copied to the distribution --------------------------------------------------- Key: HSEARCH-287 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-287 Project: Hibernate Search Issue Type: Bug Components: documentation Affects Versions: 3.0.0.cr1 Reporter: Emmanuel Bernard Priority: Minor -- 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

16 years, 11 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-290) Use IndexReader = readonly on Reader strategies (see Lucene 2.4)

by Emmanuel Bernard (JIRA)

Use IndexReader = readonly on Reader strategies (see Lucene 2.4) ---------------------------------------------------------------- Key: HSEARCH-290 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-290 Project: Hibernate Search Issue Type: New Feature Components: engine Reporter: Emmanuel Bernard Fix For: 3.1.0.CR1 -- 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

16 years, 11 months

1
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues October 2008