December 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-4754) @AuditMappedBy broken with inheritence

by Chris Raschl (JIRA)

@AuditMappedBy broken with inheritence -------------------------------------- Key: HHH-4754 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4754 Project: Hibernate Core Issue Type: Bug Components: envers Environment: envers-hibernate-3.3 Branch Reporter: Chris Raschl Priority: Minor Attachments: auditMappedBy-fix.diff Consider following entities: - A (having a "fake" bidirectional Association annotated with @AuditMappedBy) - B extends A If B is persisted or updated with a change made to the collection annotated with @AuditMappedBy the AuditEventListener does not check "fake" many-to-one bidirectional relations correctly, because the super class is not considered (although that has already been implemented in EntitiesConfigurations). I've attached the fix (I was not sure which format to use, hope this is ok)... -- 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

12 years, 6 months

3
7
0 / 0

[Hibernate-JIRA] Created: (HHH-6303) Documentation for "hibernate.hbm2ddl.import_files" needs correction.

by Tim (JIRA)

Documentation for "hibernate.hbm2ddl.import_files" needs correction. -------------------------------------------------------------------- Key: HHH-6303 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6303 Project: Hibernate Core Issue Type: Task Components: documentation Affects Versions: 3.6.0 Reporter: Tim Priority: Trivial The below page states incorrectly the name of the "hibernate.hbm2ddl.import_files" property as "hibernate.hbm2ddl.import_file" (note the missing "s" from the end). This caused me some minor confusion for a brief while, so I'm sure other readers would appreciate a correction. The URL of the documention page: http://docs.jboss.org/hibernate/stable/core/reference/en-US/html/session-... The text in question can be found in "Table 3.7. Miscellaneous Properties". -- 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

12 years, 6 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-6353) DetachedCriteria: get sql alias used for sql projection or sql restriction

by Dave (JIRA)

DetachedCriteria: get sql alias used for sql projection or sql restriction -------------------------------------------------------------------------- Key: HHH-6353 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6353 Project: Hibernate Core Issue Type: Improvement Components: query-criteria Environment: Java 6, Jboss 5.1.0, Hibernate 3 Reporter: Dave A method to get sql alias is needed from DetachedCriteria in order to use non-root entity alias in sql restriction or sql projection. DetachedCriteria: String getSqlAlias(String alias) // alias has been created detachedCriteria.createAlias("group","g"); String sqlAlias = detachedCriteria.getSqlAlias("g"); detachedCriteria.add(Restrictions.sqlRestriction(sqlAlias + ".name='John'")); detachedCriteria.setProjection(Restrictions.sqlProjection(sqlAlias + ".name")); -- 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

12 years, 6 months

4
4
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-852) Locks to manage IndexWriter instances should not prevent a concurrent get and a commit operation

by Sanne Grinovero (JIRA)

Locks to manage IndexWriter instances should not prevent a concurrent get and a commit operation ------------------------------------------------------------------------------------------------ Key: HSEARCH-852 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-852 Project: Hibernate Search Issue Type: Improvement Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 4.0.0.Alpha2 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5396) JPQL KEY() and VALUE() not implemented

by Harald Wellmann (JIRA)

JPQL KEY() and VALUE() not implemented -------------------------------------- Key: HHH-5396 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5396 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.5.3 Environment: Hibernate 3.5.3, PostgreSQL 8.4.3 Reporter: Harald Wellmann The KEY() and VALUE() operators for persistent maps do not seem to be implemented in Hibernate. E.g. consider the query {code} select m.text from MultilingualString s join s.map m where key(m) = 'de' {code} given the following classes and mappings. {code:java} @Embeddable public class LocalizedString { private String language; @Column(name = "_text") private String text; } @Entity @Table(schema = "jpa", name = "multilingual_string") public class MultilingualString { @Id @GeneratedValue(strategy = GenerationType.SEQUENCE) @Column(name = "string_id") private long id; @ElementCollection(fetch=FetchType.EAGER) @MapKeyColumn(name = "language_key", insertable = false, updatable = false) @CollectionTable(schema = "jpa", name = "multilingual_string_map", joinColumns = @JoinColumn(name = "string_id")) private Map<String, LocalizedString> map = new HashMap<String, LocalizedString>(); } {code} (Note that these mappings are similar to but slightly different from the ones I used in HHH-5393. This time the map key column has a different name, creating a redundant column I would have liked to avoid. That way, Hibernate is at least happy about the mapping.) Running the query, I get the following exception: java.lang.IllegalArgumentException: org.hibernate.hql.ast.QuerySyntaxException: unexpected AST node: [select m.text from de.myjourney.model.media.MultilingualString s join s.map m where key(m) = 'de'] at org.hibernate.ejb.AbstractEntityManagerImpl.convert(AbstractEntityManagerImpl.java:1222) at org.hibernate.ejb.AbstractEntityManagerImpl.convert(AbstractEntityManagerImpl.java:1168) at org.hibernate.ejb.AbstractEntityManagerImpl.createQuery(AbstractEntityManagerImpl.java:292) at de.myjourney.model.test.MultilingualStringTest.createGerman(MultilingualStringTest.java:35) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) at org.junit.runners.ParentRunner.run(ParentRunner.java:236) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:46) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) Caused by: org.hibernate.hql.ast.QuerySyntaxException: unexpected AST node: [select m.text from de.myjourney.model.media.MultilingualString s join s.map m where key(m) = 'de'] at org.hibernate.hql.ast.QuerySyntaxException.convert(QuerySyntaxException.java:54) at org.hibernate.hql.ast.QuerySyntaxException.convert(QuerySyntaxException.java:47) at org.hibernate.hql.ast.ErrorCounter.throwQueryException(ErrorCounter.java:82) at org.hibernate.hql.ast.QueryTranslatorImpl.analyze(QueryTranslatorImpl.java:261) at org.hibernate.hql.ast.QueryTranslatorImpl.doCompile(QueryTranslatorImpl.java:185) at org.hibernate.hql.ast.QueryTranslatorImpl.compile(QueryTranslatorImpl.java:136) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:101) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:80) at org.hibernate.engine.query.QueryPlanCache.getHQLQueryPlan(QueryPlanCache.java:98) at org.hibernate.impl.AbstractSessionImpl.getHQLQueryPlan(AbstractSessionImpl.java:156) at org.hibernate.impl.AbstractSessionImpl.createQuery(AbstractSessionImpl.java:135) at org.hibernate.impl.SessionImpl.createQuery(SessionImpl.java:1760) at org.hibernate.ejb.AbstractEntityManagerImpl.createQuery(AbstractEntityManagerImpl.java:277) ... 23 more Using upper-case 'KEY(m)', the exception is different: javax.persistence.PersistenceException: org.hibernate.exception.SQLGrammarException: could not execute query at org.hibernate.ejb.AbstractEntityManagerImpl.convert(AbstractEntityManagerImpl.java:1235) at org.hibernate.ejb.AbstractEntityManagerImpl.convert(AbstractEntityManagerImpl.java:1168) at org.hibernate.ejb.QueryImpl.getResultList(QueryImpl.java:250) at de.myjourney.model.test.MultilingualStringTest.createGerman(MultilingualStringTest.java:36) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) at org.junit.runners.ParentRunner.run(ParentRunner.java:236) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:46) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) Caused by: org.hibernate.exception.SQLGrammarException: could not execute query at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:92) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66) at org.hibernate.loader.Loader.doList(Loader.java:2297) at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2172) at org.hibernate.loader.Loader.list(Loader.java:2167) at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:448) at org.hibernate.hql.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:363) at org.hibernate.engine.query.HQLQueryPlan.performList(HQLQueryPlan.java:196) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1258) at org.hibernate.impl.QueryImpl.list(QueryImpl.java:102) at org.hibernate.ejb.QueryImpl.getResultList(QueryImpl.java:241) ... 23 more Caused by: org.postgresql.util.PSQLException: FEHLER: Funktion key(bigint) existiert nicht Hint: Keine Funktion stimmt mit dem angegebenen Namen und den Argumenttypen überein. Sie müssen möglicherweise ausdrückliche Typumwandlungen hinzufügen. Position: 161 at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2062) at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1795) at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:257) at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:479) at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:367) at org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc2Statement.java:271) at org.hibernate.jdbc.AbstractBatcher.getResultSet(AbstractBatcher.java:208) at org.hibernate.loader.Loader.getResultSet(Loader.java:1849) at org.hibernate.loader.Loader.doQuery(Loader.java:718) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:270) at org.hibernate.loader.Loader.doList(Loader.java:2294) ... 31 more (The message from PostgreSQL means "Function key(bigint) does not exist".) I had a look at the ANTLR grammar for the query parser a while ago (which may have been before 3.5.3), and as far as I could make out, key() and value() are only recognized as lower case keywords, and while the parser accepts the syntax, it fails to generate any appropriate actions. The stack traces are up-to-date though, I just ran my test cases on Hibernate 3.5.3. -- 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

12 years, 6 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2828) criteria search by class throws org.hibernate.QueryException: Unsupported discriminator type null when mapping exists for this class

by jo desmet (JIRA)

criteria search by class throws org.hibernate.QueryException: Unsupported discriminator type null when mapping exists for this class ------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-2828 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2828 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.5 Environment: hibernate 3.2.5, oracle 10g Reporter: jo desmet Attachments: src.zip when making a criteria based on a property of type class the query succeeds if this class is not mapped, the query building fails when this class is mapped within hibernate and has no discriminator e.g. code : Criteria l = session.createCriteria(SearchClass.class); l.add(Restrictions.eq("type", ClassWithNoMapping.class)); // SUCCESS java.util.List result = l.list(); l = session.createCriteria(SearchClass.class); l.add(Restrictions.eq("type", ClassWithMapping.class)); // EXCEPTION result = l.list(); exception is Hibernate: select this_.ID as ID0_0_, this_.name as name0_0_, this_.type as type0_0_ from SEARCHCLASS this_ where this_.type=? org.hibernate.QueryException: Unsupported discriminator type null at org.hibernate.loader.criteria.CriteriaQueryTranslator.getTypedValue(CriteriaQueryTranslator.java:499) at org.hibernate.criterion.SimpleExpression.getTypedValues(SimpleExpression.java:71) at org.hibernate.loader.criteria.CriteriaQueryTranslator.getQueryParameters(CriteriaQueryTranslator.java:251) at org.hibernate.loader.criteria.CriteriaLoader.list(CriteriaLoader.java:95) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1569) at org.hibernate.impl.CriteriaImpl.list(CriteriaImpl.java:283) at Test.list(Test.java:40) at Test.main(Test.java:27) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:90) classes are attached, tables should exists but no data is required. Please also provide workaround on short term if possible -- 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

12 years, 7 months

4
4
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-188) Add an option to use JMS in a JTA tx (rather than the post TX work done right now)

by Emmanuel Bernard (JIRA)

Add an option to use JMS in a JTA tx (rather than the post TX work done right now) ---------------------------------------------------------------------------------- Key: HSEARCH-188 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-188 Project: Hibernate Search Issue Type: New Feature Components: engine Reporter: Emmanuel Bernard Priority: Minor I think the main problem is ordering the hibernate flush and the JMS process. But I think the current PostTransactionWorkQueueSynchronization.beforeCompletion() suffers from the problem already. -- 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

12 years, 7 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-5465) HQL left join fetch of an element collection following a left join fetch of a one-to-one relationship causes NullPointerException

by Andrew Tolopko (JIRA)

HQL left join fetch of an element collection following a left join fetch of a one-to-one relationship causes NullPointerException --------------------------------------------------------------------------------------------------------------------------------- Key: HHH-5465 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5465 Project: Hibernate Core Issue Type: Bug Components: query-hql Affects Versions: 3.5.4 Environment: Hibernate 3.5.4, Postgresql 8.4, Java 6 Reporter: Andrew Tolopko Attachments: hibernate-left-fetch-join-element-collection.zip, log.txt HQL queries of the form "from EntityA a left join fetch a.entityB b left join fetch b.items" fail with a NullPointerExeption when EntityA and EntityB have a one-to-one (@OneToOne) relationship and EntityB.items is an element collection (@ElementCollection, aka collection of values). For comparison, the following HQL queries are all admissible (which intends to demonstrate that no particular clause of the the above HQL is incorrect): "from EntityB b left join fetch b.items" "from EntityA a left join fetch a.entityB" "from EntityA a left join fetch a.entityB.items" "from EntityA a left join fetch a.entityCs c left join fetch c.items" (where EntityA and EntityC have a one-to-many (@OneToMany) relationship, and EntityC.items is an element collection) Test code is attached. The log output along with thrown exception is attached as log.txt. -- 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

12 years, 7 months

3
6
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-407) Standalone: support pure query and object rehydratation from Lucene storage

by Emmanuel Bernard (JIRA)

Standalone: support pure query and object rehydratation from Lucene storage --------------------------------------------------------------------------- Key: HSEARCH-407 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-407 Project: Hibernate Search Issue Type: New Feature Components: engine Reporter: Emmanuel Bernard Assignee: 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

12 years, 7 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-1001) Create a testcase using HornetQ on JBoss7 for the backend

by Sanne Grinovero (JIRA)

Create a testcase using HornetQ on JBoss7 for the backend --------------------------------------------------------- Key: HSEARCH-1001 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-1001 Project: Hibernate Search Issue Type: Task Reporter: Sanne Grinovero Fix For: 4.1 When solving HSEARCH-984 it wasn't possible to create a fully automated testcase the verify the JMS integration -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 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 December 2011