July 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HBX-1000) Problem with PostgreSQL using uppercase letters in tables

by Ruediger Engelberger (JIRA)

Problem with PostgreSQL using uppercase letters in tables --------------------------------------------------------- Key: HBX-1000 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1000 Project: Hibernate Tools Issue Type: Bug Components: reverse-engineer Affects Versions: 3.2.beta11 Environment: Hibernate 3.2.5.ga, Hibernate Tools 3.2.0 beta9a, PostgreSql 8.2, postgresql-8.2-506.jdbc3.jar, Eclipse 3.3.0, all running on Windows XP at the moment (including PostgreSql) Reporter: Ruediger Engelberger I have problems using Hibernate tools when using upper case letters in a PostgreSQL database. I can configure Hibernate Tools for my local PostgreSql installation without any problems. I can access the table structure in the view Hibernate Configurations and do reverse engineering by creating XML mappings and beans. No problem. But when I'm using upper case characters in table names Hibernate Tools can't access the table structures any more. Hibernate Configuration shows the tables, but when I want to see the columns, it doesn't show anything. Reverse engineering also doesn't work any more. So, the following works: TABLE cms_clusterMessage pk_clustermessageid fk_clusternodeid messagetype messagedetail The following doesn't work: TABLE cms_clusterMessage PK_ClusterMessageId FK_ClusterNodeId MessageType MessageDetail I tried to use different JDBC drivers because I thought it could be a bug of the driver. But it wasn't. -- 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
10
0 / 0

[Hibernate-JIRA] Created: (HHH-5391) JUnit fails when we try to execute "Update queries via SQL"

by Dhaval Patel (JIRA)

JUnit fails when we try to execute "Update queries via SQL" ----------------------------------------------------------- Key: HHH-5391 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5391 Project: Hibernate Core Issue Type: Bug Components: query-sql Reporter: Dhaval Patel We are trying to run our test cases via JUnit We are using SQL queries in our DAO layer. It runs fine when we test the code from Web (UI) client. However when test the code from JUnit we get the following error: java.lang.UnsupportedOperationException: Update queries only supported through HQL Hibernate version: 3.2.0.ga Do we have a solution 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

14 years, 5 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-568) Unable to push stagged releases because hibernate-search-testing does not deploy the sources artifacts

by Emmanuel Bernard (JIRA)

Unable to push stagged releases because hibernate-search-testing does not deploy the sources artifacts ------------------------------------------------------------------------------------------------------ Key: HSEARCH-568 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-568 Project: Hibernate Search Issue Type: Bug Components: build Affects Versions: 3.2.1 Reporter: Emmanuel Bernard Assignee: Hardy Ferentschik -- 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
9
0 / 0

[Hibernate-JIRA] Created: (HHH-4904) result of 'join fetch' query is incorrectly cached

by Geoff Crain (JIRA)

result of 'join fetch' query is incorrectly cached -------------------------------------------------- Key: HHH-4904 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4904 Project: Hibernate Core Issue Type: Bug Components: caching (L2) Affects Versions: 3.3.2 Environment: hibernate 3.3.2, EhCache 1.2.3, postgresql, mysql and hsql Reporter: Geoff Crain Im not sure if this is either a bug, a missing option, or just an option that i can't find. Im using hibernate 3.3.2, and EhCache 1.2.3. I recently had an issue where objects in collections were getting dropped from the cache. After a long investigation, I found that it was because a "join fetch" query was being made on the parent object. http://docs.jboss.org/hibernate/core/3. ... ryhql.html This meant that only a subset of the child elements were selected. If the collection was not already in the cache, the "incomplete" result of this query is put into it. Every subsequent call to the parent element (wanting the "full" set of children) would only get this incomplete version. When the incomplete version drops out of the cache (after 24 hours) everything goes back to normal. So, is it a bug? Should hibernate (or ehcache) not be caching this "incomplete" collection? Or is there some way to tell hibernate that it is an incomplete collection _so_ that it doesnt get cached? * If you believe this to be a bug, I will provide a working example. * If you think this is actually an EhCache bug, tell me and Ill raise it there -- 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
1
0 / 0

[Hibernate-JIRA] Created: (HHH-5091) Unidirectional One-To-Many relationship with foreign key mapping doesn't work

by Juergen Zimmermann (JIRA)

Unidirectional One-To-Many relationship with foreign key mapping doesn't work ----------------------------------------------------------------------------- Key: HHH-5091 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5091 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.5.0-Final Reporter: Juergen Zimmermann I've the following 2 tables (in PostgreSQL) in a one-to-many relationship with foreign key mapping: CREATE TABLE bestellung( b_id BIGSERIAL NOT NULL PRIMARY KEY, version INTEGER DEFAULT 0, kunde_fk BIGINT NOT NULL REFERENCES kunde(k_id) ); CREATE TABLE bestellposition( bp_id BIGSERIAL NOT NULL PRIMARY KEY, version INTEGER DEFAULT 0, artikel_fk BIGINT NOT NULL REFERENCES artikel(a_id), anzahl SMALLINT NOT NULL, bestellung_fk BIGINT NOT NULL REFERENCES bestellung(b_id) ); Now the 2 JPA entity classes: // owner class @Entity @Table(name="bestellung") public class Bestellung implements java.io.Serializable { @Id @GeneratedValue(generator="bestellung_sequence_name") @SequenceGenerator(name="bestellung_sequence_name", sequenceName="bestellung_b_id_seq", allocationSize=1) @Column(name="b_id", nullable=false) private Long id = null; @Version private int version = 0; // bidirectional @ManyToOne(optional=false) @JoinColumn(name="kunde_fk") @NotNull(message="{bestellverwaltung.bestellung.kunde.notNull}") private Kunde kunde; // unidirectional and cascading persist @OneToMany(fetch=EAGER, cascade={PERSIST, REMOVE}, orphanRemoval=true) @JoinColumn(name="bestellung_fk") @OrderBy("id ASC") @NotEmpty(message="{bestellverwaltung.bestellung.bestellpositionen.notEmpty}") private List<Bestellposition> bestellpositionen; } // dependant class @Entity @Table(name="bestellposition") public class Bestellposition implements java.io.Serializable { @Id @GeneratedValue(generator="bestellposition_sequence_name") @SequenceGenerator(name="bestellposition_sequence_name", sequenceName="bestellposition_bp_id_seq", allocationSize=1) @Column(name="bp_id", nullable=false) private Long id = null; @Version private int version = 0; @Column(nullable=false) @Min(value=ANZAHL_MIN, message="{bestellverwaltung.bestellposition.anzahl.min}") private short anzahl = 1; @ManyToOne(optional=false) @JoinColumn(name="artikel_fk") @NotNull(message="{bestellverwaltung.bestellposition.artikel.notNull}") private Artikel artikel; } Inside the owner class the dependent class is declared with cascade=PERSIST (see above). When I try to create a persistent entity of class Bestellung (owner class) then the generated SQL statement is wrong because the foreign key ("bestellung_fk") for the owner record is missing. insert into bestellposition(anzahl, artikel_fk, version, bp_id) values(?, ?, ?, ?) -- 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

4
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3478) @NaturalId queries not flushed from cache using EntityManager.remove(); exception results from query

by Elias Ross (JIRA)

@NaturalId queries not flushed from cache using EntityManager.remove(); exception results from query ---------------------------------------------------------------------------------------------------- Key: HHH-3478 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3478 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.3.0.SP1 Environment: Java 1.5, Maven dependencies: [INFO] (root) [INFO] | \- org.hibernate:hibernate-validator:jar:3.1.0.GA:compile [INFO] +- commons-codec:commons-codec:jar:1.3:compile [INFO] +- javax.persistence:persistence-api:jar:1.0:compile [INFO] +- org.hibernate:hibernate-core:jar:3.3.0.SP1:compile [INFO] | +- antlr:antlr:jar:2.7.6:compile [INFO] | +- commons-collections:commons-collections:jar:3.1:compile [INFO] | \- dom4j:dom4j:jar:1.6.1:compile [INFO] | \- xml-apis:xml-apis:jar:1.0.b2:compile [INFO] +- org.hibernate:hibernate-annotations:jar:3.4.0.GA:compile [INFO] | \- org.hibernate:ejb3-persistence:jar:1.0.2.GA:compile [INFO] +- org.hibernate:hibernate-commons-annotations:jar:3.3.0.ga:compile [INFO] | \- org.hibernate:hibernate:jar:3.2.1.ga:compile [INFO] | +- net.sf.ehcache:ehcache:jar:1.2.3:compile [INFO] | +- asm:asm-attrs:jar:1.5.3:compile [INFO] | +- cglib:cglib:jar:2.1_3:compile [INFO] | \- asm:asm:jar:1.5.3:compile [INFO] +- org.hibernate:hibernate-entitymanager:jar:3.4.0.GA:compile [INFO] | \- javassist:javassist:jar:3.4.GA:compile [INFO] +- javax.transaction:jta:jar:1.0.1B:compile [INFO] +- org.slf4j:slf4j-api:jar:1.5.2:compile [INFO] +- org.slf4j:slf4j-log4j12:jar:1.5.2:compile [INFO] +- hsqldb:hsqldb:jar:1.8.0.10:test [INFO] \- junit:junit:jar:4.4:test Reporter: Elias Ross Attachments: Dummy.java, DummyTest.java, persistence.xml See attached test case and entity. Current Result: javax.persistence.EntityNotFoundException: Unable to find com.autodesk.lbs.cs.Dummy with id 1 at org.hibernate.ejb.Ejb3Configuration$Ejb3EntityNotFoundDelegate.handleEntityNotFound(Ejb3Configuration.java:113) at org.hibernate.event.def.DefaultLoadEventListener.load(DefaultLoadEventListener.java:171) at org.hibernate.event.def.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:223) at org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:126) at org.hibernate.impl.SessionImpl.fireLoad(SessionImpl.java:905) at org.hibernate.impl.SessionImpl.internalLoad(SessionImpl.java:873) at org.hibernate.type.EntityType.resolveIdentifier(EntityType.java:590) at org.hibernate.type.ManyToOneType.assemble(ManyToOneType.java:219) at org.hibernate.cache.StandardQueryCache.get(StandardQueryCache.java:155) at org.hibernate.loader.Loader.getResultFromQueryCache(Loader.java:2184) at org.hibernate.loader.Loader.listUsingQueryCache(Loader.java:2147) at org.hibernate.loader.Loader.list(Loader.java:2117) at org.hibernate.loader.criteria.CriteriaLoader.list(CriteriaLoader.java:118) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1596) at org.hibernate.impl.CriteriaImpl.list(CriteriaImpl.java:306) at org.hibernate.impl.CriteriaImpl.uniqueResult(CriteriaImpl.java:328) at com.autodesk.lbs.cs.DummyTest.naturalKeyCachedQuery(DummyTest.java:69) at com.autodesk.lbs.cs.DummyTest.naturalKeyCachedQuery(DummyTest.java:61) at com.autodesk.lbs.cs.DummyTest.testQuery(DummyTest.java:49) It's expected that a cache invalidation occurs with an entity's natural key when it is removed. I'll investigate a solution. -- 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

4
14
0 / 0

[Hibernate-JIRA] Created: (HHH-4798) Add Envers manual to Hibernate core documentation

by Erik-Berndt Scheper (JIRA)

Add Envers manual to Hibernate core documentation ------------------------------------------------- Key: HHH-4798 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4798 Project: Hibernate Core Issue Type: Improvement Components: envers Affects Versions: 3.5.0-Beta-3 Reporter: Erik-Berndt Scheper Now that Envers has been added to hibernate core, the Envers manual should be integrated into the Hibernate reference documentation. The Table of Contents of the latest version (3.5.0 Beta 3) does not even mention the Envers module. -- 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
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5400) Blob persistence fails with Hibernate 3.6.0-SNAPSHOT, works with 3.5.3-Final

by Tom Waterhouse (JIRA)

Blob persistence fails with Hibernate 3.6.0-SNAPSHOT, works with 3.5.3-Final ---------------------------------------------------------------------------- Key: HHH-5400 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5400 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.6.x Environment: MySQL 5.1/Spring 3.0.2 Reporter: Tom Waterhouse Priority: Critical Blob fields of an object cause the following exception when persisted using Hibernate 3.6.0-SNAPSHOT: Caused by: java.lang.UnsupportedOperationException: Blob may not be manipulated from creating session at org.hibernate.engine.jdbc.BlobProxy.invoke(BlobProxy.java:116) at $Proxy27.getBytes(Unknown Source) at com.mysql.jdbc.PreparedStatement.setBlob(PreparedStatement.java:3165) at com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.setBlob(NewProxyPreparedStatement.java:495) ... 64 more This did not occur with Hibernate 3.5.3-Final -- 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
32
0 / 0

[Hibernate-JIRA] Created: (HHH-5420) introducing new dialect for ms sql server 2008 with jdbc 3.0 and above

by Strong Liu (JIRA)

introducing new dialect for ms sql server 2008 with jdbc 3.0 and above ---------------------------------------------------------------------- Key: HHH-5420 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5420 Project: Hibernate Core Issue Type: Improvement Components: core Environment: ms sql server 2008 with jdbc 3.0 Reporter: Strong Liu Assignee: Strong Liu Fix For: 3.6.0.Beta2, 3.5.5 with the new released jdbc 3.0 driver of ms sql server 2008, there are something in the date type changed. The Microsoft SQL Server JDBC Driver 3.0 now supports the following SQL Server data types: time date datetime2 datetimeoffset For more information about these SQL Server types, see [Date and Time Data Types and Functions (Transact-SQL) | http://go.microsoft.com/fwlink/?LinkId=183664]. and without this dialect, org.hibernate.test.hql.ASTParserLoadingTest and org.hibernate.test.stateless.StatelessSessionTest fail. -- 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-5259) Invalid reflection optimization configuration property name in Hibernate documentation.

by Kirill Klenski (JIRA)

Invalid reflection optimization configuration property name in Hibernate documentation. --------------------------------------------------------------------------------------- Key: HHH-5259 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5259 Project: Hibernate Core Issue Type: Task Components: documentation Reporter: Kirill Klenski Priority: Minor I think this was already pointed out, but Hibernate documentation still misguides people to use the no-longer supported hibernate.cglib.use_reflection_optimizer property in Table 3.7. Miscellaneous Properties (http://docs.jboss.org/hibernate/core/3.5/reference/en/html/session-config...). The real name for the property is: hibernate.bytecode.use_reflection_optimizer. -- 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

4
7
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues July 2010