November 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (EJB-403) QueryTest - Native Query for Update using alias causes failure

by Juraci Paixao Krohling (JIRA)

QueryTest - Native Query for Update using alias causes failure -------------------------------------------------------------- Key: EJB-403 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-403 Project: Hibernate Entity Manager Issue Type: Patch Components: EntityManager Environment: PostgreSQL 8.2.3 and Entity Manager Reporter: Juraci Paixao Krohling Assignee: Juraci Paixao Krohling Attachments: QueryTest.diff Even though it says in documentation that it supports table aliases in "update" clauses[1], the below test fails when using it. Removing the table alias is enough to make it successful. org.hibernate.ejb.test.QueryTest#testUpdateQuery [1] http://www.postgresql.org/docs/8.2/interactive/sql-update.html -- 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

15 years, 8 months

4
13
0 / 0

[Hibernate-JIRA] Created: (ANN-779) Test EmbeddedGenericsTest generates a table name "too long" for DB2

by Juraci Paixao Krohling (JIRA)

Test EmbeddedGenericsTest generates a table name "too long" for DB2 ------------------------------------------------------------------- Key: ANN-779 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-779 Project: Hibernate Annotations Issue Type: Bug Environment: Annotations Trunk / DB2 v9.1 Reporter: Juraci Paixao Krohling Annotations test EmbeddedGenericsTest#testWorksWithGenericCollectionOfElements generates the table name "EmbeddedGenericsTest$PopularBook_editions", but DB2 complains about its lengh: DB2 SQL error: SQLCODE: -107, SQLSTATE: 42622, SQLERRMC: EMBEDDEDGENERICSTEST$POPULARBOOK_ID;30 This error message says that the name exceeds the 30 characters limit. -- 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

15 years, 8 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-3554) Investigate how bulk updates can be supported

by Adam Warski (JIRA)

Investigate how bulk updates can be supported --------------------------------------------- Key: HHH-3554 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3554 Project: Hibernate Core Issue Type: Task Components: envers Reporter: Adam Warski -- 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

15 years, 8 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2317) CGLIB unable to lazy load classes in diff. classloader than hibernate jars

by Jason Novotny (JIRA)

CGLIB unable to lazy load classes in diff. classloader than hibernate jars --------------------------------------------------------------------------- Key: HHH-2317 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2317 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.1 Reporter: Jason Novotny Please see http://forum.hibernate.org/viewtopic.php?p=2334617#2334617 for more details and possible fix -- 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

15 years, 8 months

5
8
0 / 0

[Hibernate-JIRA] Created: (HHH-3229) Make cascade rules more transparent/explicit/deterministic

by Chris Bredesen (JIRA)

Make cascade rules more transparent/explicit/deterministic ---------------------------------------------------------- Key: HHH-3229 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3229 Project: Hibernate3 Issue Type: Improvement Components: core Affects Versions: 3.2.6, 3.2.5, 3.2.4.sp1 Reporter: Chris Bredesen Cascade rules are prone to different behavior based on the order in which properties appear in mapping XML. It is possible that an unexpected TransientObjectException may arise from certain operations when an object graph with circular references is merged (and possibly persisted/updated, etc). For example, if a transient instance is reachable through more than once path from a root entity, it is not clear whether operations will be cascaded to it. The order in which the properties are mapped plays a part in determining cascade paths, but the rules are not documented. Possible resolutions include: 1. Documenting the rules so that a programmer can make educated decisions about mapping. 2. Enhancing the algorithm such that order no longer matters and the rules are deterministic. 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

15 years, 8 months

6
12
0 / 0

[Hibernate-JIRA] Created: (HHH-3095) Invalid queries when using subclasses and one-to-many associations

by Sebastien Blind (JIRA)

Invalid queries when using subclasses and one-to-many associations ------------------------------------------------------------------ Key: HHH-3095 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3095 Project: Hibernate3 Issue Type: Bug Components: query-sql Affects Versions: 3.2.5 Environment: Hibernate 3.2.5, bug identified on sybase Reporter: Sebastien Blind Priority: Blocker Attachments: src-cat.zip This bug report builds on top of the topic found in the forum at http://forum.hibernate.org/viewtopic.php?t=977453 Basically, there seems to be an issue in the way hibernate treats a collections of objects that extend a base class. The attached example has: a Cat class a DomesticCat class (extends Cat) a Cage class (can contain multiple DomesticCat) The generated SQL is below - the filter cats0_.CAGE_ID=? should really be cats0_1_.CAGE_ID=? select cats0_.CAGE_ID as CAGE3_1_, cats0_.CAT_ID as CAT1_1_, cats0_.CAT_ID as CAT1_0_0_, cats0_1_.CAGE_ID as CAGE2_2_0_ from CAT cats0_ inner join DCAT cats0_1_ on cats0_.CAT_ID=cats0_1_.CAT_ID where cats0_.CAGE_ID=? As of now, I am not aware of any configuration that would work around this problem. Please let me know if you know otherwise. Thanks, Sebastien -- 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

15 years, 8 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HBX-779) jdbc reengineer sql-type problem with oracle 9i

by jacky hua (JIRA)

jdbc reengineer sql-type problem with oracle 9i ----------------------------------------------- Key: HBX-779 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-779 Project: Hibernate Tools Type: Bug Components: reverse-engineer Versions: 3.2beta8 Environment: windowsxp sp2, jdk 1.4.2, eclipse 3.1.2 Reporter: jacky hua I used the ant task hibernate-tools provided like the below to generate hbms xml <target name="default" description="generate hbm"> <delete dir="./generate"/> <mkdir dir="./generate"/> <hibernatetool destdir="./generate"> <jdbcconfiguration configurationfile="./metadata/hibernate.cfg.xml" revengfile="./metadata/hibernate.reveng.xml" packagename="net.ema.examples.sa" detectmanytomany="true" detectoptimisticlock="true"> </jdbcconfiguration> <hbm2hbmxml destdir="./generate" /> </hibernatetool> </target> the ./metadata/hibernate.cfg.xml like the below: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE hibernate-reverse-engineering SYSTEM "http://hibernate.sourceforge.net/hibernate-reverse-engineering-3.0.dtd" > <hibernate-reverse-engineering> <schema-selection match-catalog="TITAN" match-schema="TITAN" /> <type-mapping>   <sql-type jdbc-type="NUMERIC" precision="1" hibernate-type="boolean" />  <sql-type jdbc-type="NUMERIC" precision="19" hibernate-type="long" /> <sql-type jdbc-type="TIMESTAMP" hibernate-type="java.util.Date" /> </type-mapping>  <table-filter match-name="BIN$.*" exclude="true" /> </hibernate-reverse-engineering> But the <sql-type jdbc-type="NUMERIC" precision="19" hibernate-type="long" /> didn't work, also generate big_decimal type not long type, otherwise the others two sql-type rules worked. the not affected column:USER_ID was pk of my table. the generated hbm file is like the below: <class name="net.ema.examples.sa.UserModel" table="T_SA_USER" schema="TITAN"> <id name="userId" type="big_decimal"> <column name="USER_ID" scale="0" /> <generator class="assigned" /> </id> <property name="logonName" type="string"> <column name="LOGON_NAME" length="60" /> </property> <property name="password" type="string"> <column name="PASSWORD" length="80" /> </property> <property name="isOrgAdmin" type="java.lang.Boolean"> <column name="IS_ORG_ADMIN" precision="1" scale="0" /> </property> <property name="remark" type="string"> <column name="REMARK" length="400" /> </property> <property name="createDate" type="java.util.Date"> <column name="CREATE_DATE" length="11" /> </property> <property name="status" type="string"> <column name="STATUS" length="2" /> </property> </class> -- 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

15 years, 8 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3620) Oracle - testWithClause fails due to "Missing IN or OUT parameter at index:: 1"

by Juraci Paixao Krohling (JIRA)

Oracle - testWithClause fails due to "Missing IN or OUT parameter at index:: 1" ------------------------------------------------------------------------------- Key: HHH-3620 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3620 Project: Hibernate Core Issue Type: Bug Components: testsuite Affects Versions: 3.3.x Environment: Oracle 9i, Branch_3_3 Reporter: Juraci Paixao Krohling Test testWithClause (org.hibernate.test.hql.WithClauseTest) fails due to "Missing IN or OUT parameter at index:: 1" Stack trace: org.hibernate.exception.GenericJDBCException: could not execute query at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:126) at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:114) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66) at org.hibernate.loader.Loader.doList(Loader.java:2231) at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2125) at org.hibernate.loader.Loader.list(Loader.java:2120) at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:401) at org.hibernate.hql.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:364) at org.hibernate.engine.query.HQLQueryPlan.performList(HQLQueryPlan.java:196) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1149) at org.hibernate.impl.QueryImpl.list(QueryImpl.java:102) at org.hibernate.test.hql.WithClauseTest.testWithClause(WithClauseTest.java:112) 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:585) at junit.framework.TestCase.runTest(TestCase.java:168) at org.hibernate.junit.functional.FunctionalTestCase.runTest(FunctionalTestCase.java:125) at junit.framework.TestCase.runBare(TestCase.java:134) at org.hibernate.junit.UnitTestCase.runBare(UnitTestCase.java:63) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:232) at org.hibernate.junit.functional.FunctionalTestClassTestSuite.runTest(FunctionalTestClassTestSuite.java:115) at junit.framework.TestSuite.run(TestSuite.java:227) at org.hibernate.junit.functional.FunctionalTestClassTestSuite.run(FunctionalTestClassTestSuite.java:84) at org.junit.internal.runners.OldTestClassRunner.run(OldTestClassRunner.java:76) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:45) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) Caused by: java.sql.SQLException: Missing IN or OUT parameter at index:: 1 at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112) at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:146) at oracle.jdbc.driver.OraclePreparedStatement.processCompletedBindRow(OraclePreparedStatement.java:1711) at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3311) at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3361) at org.hibernate.jdbc.AbstractBatcher.getResultSet(AbstractBatcher.java:208) at org.hibernate.loader.Loader.getResultSet(Loader.java:1808) at org.hibernate.loader.Loader.doQuery(Loader.java:697) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:259) at org.hibernate.loader.Loader.doList(Loader.java:2228) ... 31 more -- 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

15 years, 8 months

1
6
0 / 0

[Hibernate-JIRA] Created: (EJB-381) EntityManager doesn't care about INSERT trigger of Oracle XE

by Juergen Zimmermann (JIRA)

EntityManager doesn't care about INSERT trigger of Oracle XE ------------------------------------------------------------ Key: EJB-381 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-381 Project: Hibernate Entity Manager Issue Type: Bug Affects Versions: 3.4.0.GA Environment: Hibernate EM 3.4.0, Hibernate Annotations 3.4.0, Hibernate Commons Annotations 3.1.0, Hibernate 3.3.0.SP1, Hibernate Validator 3.1.0.CR2, JDK 1.6.0_07 Reporter: Juergen Zimmermann I have an abstract entity class with 2 derived concrete classes: @Entity @Table(name="kunde") @Inheritance @DiscriminatorColumn(name="art", length=1) @XmlRootElement @XmlSeeAlso({ Firmenkunde.class, Privatkunde.class }) @XmlAccessorType(XmlAccessType.FIELD) public abstract class Kunde implements java.io.Serializable { @Id @GeneratedValue(generator="kunde_sequence_name") @SequenceGenerator(name="kunde_sequence_name", sequenceName="kunde_k_id_seq", allocationSize=1) @Column(name="k_id", nullable=false) @XmlAttribute(name="id", required=true) protected Long id = KEINE_ID; @Version @XmlTransient protected int version = ERSTE_VERSION; @Column(length=32, nullable=false) @XmlElement(required=true) protected String nachname = ""; ... @Column(length=32, unique=true) protected String username = ""; ... } The table is created as follows: CREATE TABLE kunde( k_id NUMBER(16) NOT NULL PRIMARY KEY, version NUMBER(8) DEFAULT 0, nachname VARCHAR2(32) NOT NULL, ... art VARCHAR2(2) DEFAULT 'P', ... username VARCHAR2(32) NOT NULL UNIQUE, ... ); Additionally there is this sequence and insert trigger for column username. CREATE SEQUENCE kunde_k_id_seq START WITH 200 NOMAXVALUE / CREATE OR REPLACE TRIGGER kunde_trigger_insert BEFORE INSERT ON kunde FOR EACH ROW BEGIN :NEW.username := TO_CHAR(:NEW.k_id); END; / New objects are inserted into the database using this code which works fine with PostgreSQL. However, using Oracle XE the insert trigger isn't considered: public List<Kunde> insertKunden(List<Kunde> kunden) { if (kunden == null || kunden.isEmpty()) { return new ArrayList<Kunde>(0); } for (Kunde k: kunden) { em.persist(k); } return kunden; } The attribute "username" is null using Oracle XE, but using PostgreSQL it has the value produced by the INSERT trigger. -- 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

15 years, 8 months

2
1
0 / 0

[Hibernate-JIRA] Created: (EJB-404) QueryTest - PostgreSQL - "ERROR: operator does not exist: character varying = bytea"

by Juraci Paixao Krohling (JIRA)

QueryTest - PostgreSQL - "ERROR: operator does not exist: character varying = bytea" ------------------------------------------------------------------------------------ Key: EJB-404 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-404 Project: Hibernate Entity Manager Issue Type: Patch Components: EntityManager Environment: PostgreSQL and Entity Manager Reporter: Juraci Paixao Krohling Assignee: Juraci Paixao Krohling Attachments: QueryTest_2.diff Test org.hibernate.ejb.test.QueryTest#testIsNull fails due to this query: select i from Item i where (i.descr is null and :descr is null) or i.descr = :descr When changing the query to what it reads below, it works properly: select i from Item i where i.descr = :descr or (i.descr is null and :descr is null) As this happened only with PostgreSQL, I assume this is an issue with either the driver or with the database itself. Will dig into pgsql's site to find out more about this issue. -- 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

15 years, 8 months

2
8
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues November 2008