December 2012 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-6491) Support @javax.persistence.SqlResultSetMapping(s) including @javax.persitence.EntityResult and @javax.persistence.ColumnResult

by Hardy Ferentschik (JIRA)

Support @javax.persistence.SqlResultSetMapping(s) including @javax.persitence.EntityResult and @javax.persistence.ColumnResult ------------------------------------------------------------------------------------------------------------------------------ Key: HHH-6491 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6491 Project: Hibernate Core Issue Type: Sub-task Reporter: Hardy Ferentschik -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

3
6
0 / 0

[Hibernate-JIRA] Created: (HHH-6492) Support @javax.persistence.Enumerated

by Strong Liu (JIRA)

Support @javax.persistence.Enumerated ------------------------------------- Key: HHH-6492 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6492 Project: Hibernate Core Issue Type: Sub-task Components: metamodel Reporter: Strong Liu -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

2
4
0 / 0

[Hibernate-JIRA] (HHH-7896) bind column with logical name

by Strong Liu (JIRA)

13 years, 3 months

1
0
0 / 0

[Hibernate-JIRA] (HSEARCH-1168) Improve documentation on Spatial integrations

by Sanne Grinovero (JIRA)

13 years, 3 months

3
14
0 / 0

[Hibernate-JIRA] Created: (HHH-6580) Discriminator value used as ID when inserting entity to PosgtreSQL

by Paweł Stawicki (JIRA)

Discriminator value used as ID when inserting entity to PosgtreSQL ------------------------------------------------------------------ Key: HHH-6580 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6580 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.6.6, 3.6.5, 3.6.4, 3.6.3, 3.6.2, 3.6.1, 3.6.0 Environment: Tested on Hibernate 3.6.0, but I looked in the code of 3.6.6 and 4.0.0 Beta4 and it looks like it isn't fixed. PostgreSQL 8.4.8 Reporter: Paweł Stawicki When we have inheritance strategy SINGLE_TABLE, and we use discriminator column, this column is the first one in table. Now we want to insert some entity inheriting from this one, and we want PostgreSQL to automatically generate the ID for the new entity. Discriminator column is the first in the table. Hibernate runs IdentityGenerator.GetGeneratedKeysDelegate.executeAndExtract(), which gets ResultSet from PreparedStatement (in Hibernate 3.6.0 it's line 97 in IdentityGenerator). This ResultSet, in case of PostgreSQL, contains whole inserted row, not only ID. This is the problem if ID is not the first column, because then Hibernate get's value from the first column and uses it as ID. It's in IdentifierGeneratorHelper.getGeneratedIdentity() and IdentifierGeneratorHelper.get(). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

5
14
0 / 0

[Hibernate-JIRA] (HHH-7895) Dual JOIN FETCH doubles number of child records

by Uli Bubenheimer (JIRA)

13 years, 3 months

1
3
0 / 0

[Hibernate-JIRA] (HHH-7894) failing test due to EntityNotFoundDelegate is not set to the SFbuilder

by Strong Liu (JIRA)

13 years, 3 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-7099) Unable to build EntityManagerFactory with not-JTA Datasource

by Wilson Horstmeyer Bogado (JIRA)

Unable to build EntityManagerFactory with not-JTA Datasource ------------------------------------------------------------ Key: HHH-7099 URL: https://hibernate.onjira.com/browse/HHH-7099 Project: Hibernate ORM Issue Type: Bug Components: entity-manager Affects Versions: 4.1.0, 4.0.1 Environment: Tomcat 7, Java 7, Hibernate 4.x, Servlet 3.0 Reporter: Wilson Horstmeyer Bogado Attachments: HibernateTest.zip When upgrading from Hibernate 3.6.x to Hibernate 4.x it is not possible to create an entity manager factory using a non-JTA Datasource in persistence.xml. When looking up the datasource with JNDI a "javax.naming.NamingException: This context must be accessed through a java: URL" exception is thrown. Debugging the source code we can see that in 3.6.x the lookup is done with "javax.naming.lookup(String)" but in 4.x it is done with "javax.naming.lookup(Name)" which fails. The attached file is a test case. To reproduce, do the following: 1. Build the project with Maven 2. Deploy to Tomcat 3. Go to /hibernate-test/test Result: All database records are shown in browser Now, in pom.xml file, change hibernate.core.version property from 3.6.10.Final to 4.1.0.Final. Repeat above steps. Result: an exception stack trace is displayed which ends with: Caused by: javax.naming.NamingException: This context must be accessed through a java: URL at org.apache.naming.SelectorContext.parseName(SelectorContext.java:776) at org.apache.naming.SelectorContext.lookup(SelectorContext.java:135) at javax.naming.InitialContext.lookup(InitialContext.java:415) at org.hibernate.service.jndi.internal.JndiServiceImpl.locate(JndiServiceImpl.java:65) ... 42 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

2
4
0 / 0

[Hibernate-JIRA] (BVAL-341) Add @Nullable for explicit communication of nullability

by Matthew Adams (JIRA)

13 years, 3 months

2
2
0 / 0

[Hibernate-JIRA] (HHH-1523) Rebuild fetches from query-cache hits

by Andy flury (JIRA)

13 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues December 2012