May 2012 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HSEARCH-1096) @Transient Fields are never marked dirty

by Marc Schipperheyn (JIRA)

@Transient Fields are never marked dirty ---------------------------------------- Key: HSEARCH-1096 URL: https://hibernate.onjira.com/browse/HSEARCH-1096 Project: Hibernate Search Issue Type: Bug Components: engine Affects Versions: 4.1.0.Final Reporter: Marc Schipperheyn Transient @Fields that rely on underlying @Fields are never marked dirty. When an underlying @Field is marked dirty, the @Transient related @Field should also be marked dirty. I suppose that without additional metadata (see HSEARCH-1093), a @Transient @Field should be considered dirty by default, although this may lead to unnecessary database calls. {code} @Field @IndexedEmbedded public Photo getPhoto(){ return photo; } @Transient @Field public String getPhotoUrl(){ return photoDir + "/" + photo.getFilename(); } {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-6044) Compound ID with auto-generated part produces exception

by Alex Shubert (JIRA)

Compound ID with auto-generated part produces exception ------------------------------------------------------- Key: HHH-6044 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6044 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.6 Environment: java 6.23 64bit Hibernate 3.5.6 Reporter: Alex Shubert @Entity public class TestRow implements Serializable { @Id @GeneratedValue(strategy = GenerationType.IDENTITY) private Long id; @Id private Long version; setters and getters are ommited for it's triviality } 2. creating database and table by hand #mysql -u username ... create table F_TESTROW (ID bigint not null auto_increment, VERSION bigint not null, primary key (VERSION, ID)) TestRow testRow = new TestRow(); testRow.setVersion(2L); testRow.setAddr("somewhere"); sessionFactory.openSession().save(testRow); produces java.lang.IllegalArgumentException: Can not set java.lang.Long field ru.kctsoft.fenestro.domain.strategy.TestRow.id to org.hibernate.id.IdentifierGeneratorHelper$2 at org.hibernate.property.DirectPropertyAccessor$DirectSetter.set(DirectPropertyAccessor.java:139) This is kinda frustrating. http://docs.jboss.org/hibernate/stable/annotations/reference/en/html_single/ 2.2.3.2.4. Partial identifier generation Hibernate supports the automatic generation of some of the identifier properties. Simply use the @GeneratedValue annotation on one or several id 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

3
4
0 / 0

[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

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

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-7314) DELETE Query generating invalid SQL for PostgreSQL databases.

by Bryan Varner (JIRA)

DELETE Query generating invalid SQL for PostgreSQL databases. ------------------------------------------------------------- Key: HHH-7314 URL: https://hibernate.onjira.com/browse/HHH-7314 Project: Hibernate ORM Issue Type: Bug Components: core, entity-manager Affects Versions: 4.1.3, 4.1.2 Environment: Hibernate 4.1.2, 4.1.3, PostgreSQL 9.1 (should effect all releases from 8.1 ~ current) Reporter: Bryan Varner Using a JPA Delete query with conditions requiring a join through Hibernate entity-manager generates invalid SQL for PostgreSQL. PostgreSQL cannot use CROSS JOIN in the FROM clause of a DELETE query. For example: JPQL Query {code} DELETE FROM Foo f WHERE f.bar.key = :key AND f.anotherprop = :anotherval {code} Generates an (invalid) SQL query like: {code} delete from schema.Foo cross join schema.Bar bar1_ where key=$1 and anotherprop=$2 {code} For PostgreSQL I believe this needs to look like: {code} delete from schema.Foo using schema.Bar bar1_ where key=$1 and anotherprop=$2 {code} PostgreSQL documentation on the DELETE syntax: http://www.postgresql.org/docs/8.1/static/sql-delete.html http://www.postgresql.org/docs/9.1/static/sql-delete.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

2
3
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

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

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

2
2
0 / 0

[Hibernate-JIRA] Test Message From JIRA

by noreply＠atlassian.com

This is a test message from JIRA. Server: Default SMTP Server SMTP Port: 25 Description: From: noreply(a)atlassian.com Host User Name: null

12 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-7328) Binding a self-referencing many-to-one attribute results in NullPointerException

by Gail Badner (JIRA)

Binding a self-referencing many-to-one attribute results in NullPointerException -------------------------------------------------------------------------------- Key: HHH-7328 URL: https://hibernate.onjira.com/browse/HHH-7328 Project: Hibernate ORM Issue Type: Bug Components: metamodel Reporter: Gail Badner Assignee: John Verhaeg Fix For: 5.0.0 This can be reproduced by executing org.hibernate.test.onetomany.RecursiveBidirectionalOneToManyNoCacheTest with -Dhibernate.test.new_metadata_mappings=true. After this issue is fixed, the test may still fail for other reasons. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues May 2012