July 2012 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] (HHH-7442) rename org.hibernate.internal.util.Value

by Strong Liu (JIRA)

13 years, 4 months

1
2
0 / 0

[Hibernate-JIRA] (HHH-7380) bug when initialize MULTI_TENANT_IDENTIFIER_RESOLVER and CUSTOM_ENTITY_DIRTINESS_STRATEGY

by Strong Liu (JIRA)

13 years, 4 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-6707) One-to-One mapping with foreign key in target table and foreign key being the primary key fails with Oracle

by Florian Rampp (JIRA)

One-to-One mapping with foreign key in target table and foreign key being the primary key fails with Oracle ----------------------------------------------------------------------------------------------------------- Key: HHH-6707 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6707 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.6.6 Environment: Oracle 11g, Oracle JDBC 11.2.0.1.0 Reporter: Florian Rampp Attachments: bugreports-hibernate-oracleUniquePk-1.0-SNAPSHOT-src.zip When mapping a one-to-one parent/child relationship with the foreign key being in the child table and forming its primary key, in addition to the primary key definition, a unique constraint is generated (due to the one-to-one inverse mapping). A unique constraint and a primary key definition on the same column is not accepted by Oracle. The error is "ORA-02261: such unique or primary key already exists in the table" when creating the schema. The key entities: {code:java} @Entity public class Parent { @Id Long id; @OneToOne(cascade = CascadeType.ALL, orphanRemoval = true, mappedBy = "parent") Child child; } @Entity public class Child implements Serializable { @Id @OneToOne(optional = false) private Parent parent; } {code} The resulting DDL is: {code:sql} create table Child ( parent_id number(19,0) not null, primary key (parent_id), unique (parent_id) ) {code} This issue is similar to https://hibernate.onjira.com/browse/HBX-978. But I refiled it here since I consider it to be a bug in Hibernate core. Also, I provided a test case that can be used for regression tests. It needs to be executed with the arguments {{-Dhibernate.connection.username=<USERNAME> -Dhibernate.connection.password=<PASSWORD> -Dhibernate.connection.url=<JDBC_URL>}}. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-6304) Exception on consturctor query jpql

by Itis Me (JIRA)

Exception on consturctor query jpql ----------------------------------- Key: HHH-6304 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6304 Project: Hibernate Core Issue Type: Bug Components: entity-manager Affects Versions: 3.6.5, 3.6.4, 3.6.3, 3.6.2 Reporter: Itis Me Constructor queries (SELECT NEW xyz(a,b)...) with more than one parameter in the constructor are resulting in an java.lang.IllegalArgumentException: Cannot create TypedQuery for query with more than one return. Code snippet for testing: List<ListResult> resultList = em.createQuery("SELECT NEW domain.results.ListResult(p.name, p.adress) FROM Person p", ListResult.class).getResultList(); Moreover queries with one paramater in ctor result in an java.lang.IllegalArgumentException: Type specified for TypedQuery [com.evva.keyxs.backend.domain.results.ListResult] is incompatible with query return type [class java.lang.String] at org.hibernate.ejb.AbstractEntityManagerImpl.createQuery(AbstractEntityManagerImpl.java:286) More on this in HHH-5348. Its not fixed yet. http://opensource.atlassian.com/projects/hibernate/browse/HHH-5348 -- 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

13 years, 4 months

7
13
0 / 0

[Hibernate-JIRA] (HHH-7374) Support KEY, ENTRY and VALUE qualifiers in WHERE clause

by Strong Liu (JIRA)

13 years, 4 months

1
0
0 / 0

[Hibernate-JIRA] (HHH-7381) Refact: split CacheImpl from SessionFactoryImpl into a session factory scope service

by Strong Liu (JIRA)

13 years, 4 months

1
2
0 / 0

[Hibernate-JIRA] (HHH-7368) SQLServer2005Dialect: pagination query fails if terminating with a semicolon

by Strong Liu (JIRA)

13 years, 4 months

1
0
0 / 0

[Hibernate-JIRA] (HHH-7440) Redesign dialect-specific LIMIT clause appliance

by Lukasz Antoniak (JIRA)

13 years, 4 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2158) incorrect hql query on one-to-one with property-ref

by Sebastien Cesbron (JIRA)

incorrect hql query on one-to-one with property-ref ---------------------------------------------------- Key: HHH-2158 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2158 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.ga Environment: hibernate 3.2.0.ga with firebird 1.5.3 and jaybird 1.5.5 driver on windows XP Reporter: Sebastien Cesbron Attachments: testhib.zip I have a one-to-one relationship with property-ref between Master and Slave2. I want to find all Master instances that have a null Slave2 instance associated. To do so my query is select master from Master master where master.slave2 is null The sql generated is select master0_.oid as oid0_, master0_.libelle as libelle0_ from Master master0_ where master0_.oid is null which seems incorrect. It checks here Master instances with null id (config files are listed below). If I do my query like this select master from Master master where master.slave2.oid is null the generated sql is ok : select master0_.oid as oid0_, master0_.libelle as libelle0_ from Master master0_, Slave2 slave2x1_ where master0_.oid=slave2x1_.myMaster and (slave2x1_.oid is null) I have attached a small eclipse project that reproduces the problem This problem may-be related to the one I have submitted as issue HHH-1849 -- 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

13 years, 4 months

6
7
0 / 0

[Hibernate-JIRA] (OGM-213) Avoid storing reverse side association navigation info when no reverse side association is present

by Emmanuel Bernard (JIRA)

13 years, 4 months

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