November 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Commented: (HBX-524) Reverse of one-to-one relationships

by Max Rydahl Andersen (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-524?page=co... ] Max Rydahl Andersen commented on HBX-524: ----------------------------------------- Related jboss tools issue: https://jira.jboss.org/jira/browse/JBIDE-3270 > Reverse of one-to-one relationships > ----------------------------------- > > Key: HBX-524 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-524 > Project: Hibernate Tools > Issue Type: Bug > Components: reverse-engineer > Affects Versions: 3.1beta2 > Environment: HIbernate 3.1, Oracle 9i > Reporter: Andrea Cattani > Assignee: Anthony Patricio > Fix For: 3.2.4.CR1 > > Attachments: HBX-524.patch, HBX-524v2.patch, one-to-one-marcio.patch, patch.txt > > > Hi, > I've posted this issue to the forum and got this response from Max, Hibernate Team: > "the reveng tools does not detect this as a one-to-one. it probably could, so add a request/patch to jira." > The problem I've faced is the following: > I have two tables, let's say > - table A with column ID (PK) and other fields > - table B with column ID (PK) and other fields > table B has a foreign key constraint against table A, from column ID to column ID (one-to-one) > When I reverese the tables with the HibernateTools I have such a resultant mapping for table B: > <class name="B" table="B" schema="SCHEMA"> > <id name="id" type="string"> > <column name="ID" length="12" /> > <generator class="assigned" /> > </id> > <[b]many-to-one name[/b]="a" class="A" update="false" insert="false" fetch="select"> > <column name="ID" length="12" not-null="true" unique="true" /> > </many-to-one> > .... > And this one for table A: > <class name="A" table="A" schema="SCHEMA"> > <id name="id" type="string"> > <column name="ID" length="12" /> > <generator class="assigned"/> > </id> > <set name="b" inverse="true"> > <key> > <column name="ID" length="12" not-null="true" unique="true" /> > </key> > <[b]one-to-many[/b] class="B" /> > </set> > </class> > while I was expecting something like: > [i]<one-to-one name="a" class="A" constrained="true"/>[/i] > in table B, and the same (or nothing) in table A > Thank you > Andi -- 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, 7 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HBX-524) Reverse of one-to-one relationships

by Max Rydahl Andersen (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-524?page=co... ] Max Rydahl Andersen commented on HBX-524: ----------------------------------------- Because we didn't get the ui in place - i'm working on that. > Reverse of one-to-one relationships > ----------------------------------- > > Key: HBX-524 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-524 > Project: Hibernate Tools > Issue Type: Bug > Components: reverse-engineer > Affects Versions: 3.1beta2 > Environment: HIbernate 3.1, Oracle 9i > Reporter: Andrea Cattani > Assignee: Anthony Patricio > Fix For: 3.2.4.CR1 > > Attachments: HBX-524.patch, HBX-524v2.patch, one-to-one-marcio.patch, patch.txt > > > Hi, > I've posted this issue to the forum and got this response from Max, Hibernate Team: > "the reveng tools does not detect this as a one-to-one. it probably could, so add a request/patch to jira." > The problem I've faced is the following: > I have two tables, let's say > - table A with column ID (PK) and other fields > - table B with column ID (PK) and other fields > table B has a foreign key constraint against table A, from column ID to column ID (one-to-one) > When I reverese the tables with the HibernateTools I have such a resultant mapping for table B: > <class name="B" table="B" schema="SCHEMA"> > <id name="id" type="string"> > <column name="ID" length="12" /> > <generator class="assigned" /> > </id> > <[b]many-to-one name[/b]="a" class="A" update="false" insert="false" fetch="select"> > <column name="ID" length="12" not-null="true" unique="true" /> > </many-to-one> > .... > And this one for table A: > <class name="A" table="A" schema="SCHEMA"> > <id name="id" type="string"> > <column name="ID" length="12" /> > <generator class="assigned"/> > </id> > <set name="b" inverse="true"> > <key> > <column name="ID" length="12" not-null="true" unique="true" /> > </key> > <[b]one-to-many[/b] class="B" /> > </set> > </class> > while I was expecting something like: > [i]<one-to-one name="a" class="A" constrained="true"/>[/i] > in table B, and the same (or nothing) in table A > Thank you > Andi -- 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, 7 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-296) Expose managed entity class via a Projection constant

by Jesse McLaughlin (JIRA)

Expose managed entity class via a Projection constant ----------------------------------------------------- Key: HSEARCH-296 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-296 Project: Hibernate Search Issue Type: New Feature Environment: all Reporter: Jesse McLaughlin Expose managed entity class via a projection constant. It's currently possible to get the entity class using: ProjectionConstants.DOCUMENT, and then: ((Document)tuple[0]).getField("_hibernate_class") But it would be nice to have the equivalent available as a first class projection constant. Looks like this is currently a TODO in the source code for org.hibernate.search.ProjectionConstants. But you can't vote on a TODO! :) -- 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, 7 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3619) Calling Query.iterator() executed queries and leaves preparedstatements open if not iterated to the end.

by Jari Timonen (JIRA)

Calling Query.iterator() executed queries and leaves preparedstatements open if not iterated to the end. -------------------------------------------------------------------------------------------------------- Key: HHH-3619 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3619 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.1.2 Environment: Hibernate 3.1.2, Oracle 9.0.2.8 Reporter: Jari Timonen I was wondering if this design point/flaw is still valid: QueryLoader http://kickjava.com/src/org/hibernate/loader/hql/QueryLoader.java.htm Makes Iterator: http://kickjava.com/src/org/hibernate/impl/IteratorImpl.java.htm QueryLoader gives ResultSet and PreparedStatement to iterator. Every time Qeury.iterator() is called, it executes queries. So, if you do not iterate code to the end it leaves PS, RS open. close()-method is only called if hasNext() is false. (postNext()) Commit does not close these since it does not have access to them (?). This code leaves preparedstatement open and finally after 100-200 open preparedstatements hibernate crashes: if(query.iterate().hasNext()) query.iterate().next(); I think this is a major design issue. Is this considered as bug or "it works like this, just iterate to the end and use proper SQL-queries"? Whole iterator-logic needs redesign -- 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, 7 months

1
0
0 / 0

[Hibernate-JIRA] Created: (ANN-688) Repeated columns created for single table inheritance

by Nick Heudecker (JIRA)

Repeated columns created for single table inheritance ----------------------------------------------------- Key: ANN-688 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-688 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.0.ga Environment: Hibernate 3.2.5ga, Postgresql Reporter: Nick Heudecker I have the following classes: @Entity @Inheritance(strategy= InheritanceType.SINGLE_TABLE) @DiscriminatorColumn(name="cltype", discriminatorType= DiscriminatorType.STRING, length=10) @DiscriminatorValue("device") public abstract class Device extends AbstractPersistent { private System system; @ManyToOne public System getSystem() { return system; } public void setSystem(System system) { this.system = system; } } @Entity @DiscriminatorValue("snmp") public class SnmpDevice extends Device { // .... additional properties defined } When I try to create the SessionFactory, I'm getting the following exception: Caused by: org.hibernate.MappingException: Repeated column in mapping for entity: model.SnmpDevice column: system_uuid (should be mapped with insert="false" update="false") at org.hibernate.mapping.PersistentClass.checkColumnDuplication(PersistentClass.java:652) at org.hibernate.mapping.PersistentClass.checkPropertyColumnDuplication(PersistentClass.java:674) at org.hibernate.mapping.PersistentClass.checkColumnDuplication(PersistentClass.java:696) at org.hibernate.mapping.PersistentClass.validate(PersistentClass.java:450) at org.hibernate.mapping.SingleTableSubclass.validate(SingleTableSubclass.java:43) at org.hibernate.cfg.Configuration.validate(Configuration.java:1102) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1287) -- 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, 7 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3618) Lack of documentation of the method Interceptor.onCollectionUpdate

by Ed Bras (JIRA)

Lack of documentation of the method Interceptor.onCollectionUpdate ------------------------------------------------------------------ Key: HHH-3618 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3618 Project: Hibernate Core Issue Type: Bug Components: documentation Affects Versions: 3.3.1 Environment: n.a. Reporter: Ed Bras A few verions ago the new method Interceptor.onCollectionUpdate was introduced, which could be very nice to do "something" just before value type objects are flushed. However, the usage is totaly unclear and till today no documentation is available. Also in the forum, nobody seems to really know how it should be used, and there is confusion about his usage in the forum. It would be very nice if somebody of the development team would take 5 minutes to right this down with a few examples. At least developers can then really make use of it. In my case I need to update a date of value type objects that are stored in a set that is cascaded updated due to an update call on his entity. For example: Entity: member that has a set of status history objects (value types). But I have no idea how to do this correctly without too much performance impact, even not after debugging the call to this method... -- 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, 7 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1615) GROUP BY entity does not work

by Steve Van Reeth (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1615?page=c... ] Steve Van Reeth commented on HHH-1615: -------------------------------------- Did you try this ? select new list(cat, count(*)) from Cat cat group by cat Something strange with the generated SQL of this solution: select p.productType, count(*) from Product p group by p.productType -> SELECT P.PRODUCT_TYPE_ID, COUNT(*) FROM PRODUCT p INNER JOIN PRODUCT_TYPE T ON (T.ID = P.PRODUCT_TYPE_ID) GROUP BY P.TYPE_ID The inner join is not useful. Why Hibernate do this ? > GROUP BY entity does not work > ----------------------------- > > Key: HHH-1615 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1615 > Project: Hibernate Core > Issue Type: Improvement > Components: query-hql > Affects Versions: 3.2.5 > Environment: PostgreSQL 8.1.3, Hibernate 3.1.3 > Reporter: Xavier Bugaud > Assignee: Anthony Patricio > Priority: Critical > Attachments: group-by-discriminator.patch, hibernate-group-by.diff > > > The query : "select cat, count(*) from Cat cat group by cat" does not work. > ERROR: column "xxxx" must appear in the GROUP BY clause or be used in an aggregate function > See : > - http://forum.hibernate.org/viewtopic.php?t=953716 > - http://jira.nhibernate.org/browse/NH-528 -- 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, 7 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3617) Using Query (Object) ocurr violates foreign key in transaction

by Clayton K. N. Passos (JIRA)

Using Query (Object) ocurr violates foreign key in transaction -------------------------------------------------------------- Key: HHH-3617 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3617 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1 Environment: "PostgreSQL 8.2.5 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 4.3.0 20080428 (Red Hat 4.3.0-8)" Hibernate core 3.3.1 and the only required library Reporter: Clayton K. N. Passos Attachments: Car.hbm.xml, MainTest.java, Travel.hbm.xml Using Query (Object) ocurr violates foreign key in transaction Look MainTest and Query object: Query query = session.createQuery(sb.toString()); int row = query.executeUpdate(); I expect that the behavior be the even though Session.delete(...), but it´s not true. The exception occurs below: Exception in thread "main" org.hibernate.exception.ConstraintViolationException: could not execute update query at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:94) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66) at org.hibernate.hql.ast.exec.BasicExecutor.execute(BasicExecutor.java:107) at org.hibernate.hql.ast.QueryTranslatorImpl.executeUpdate(QueryTranslatorImpl.java:419) at org.hibernate.engine.query.HQLQueryPlan.performExecuteUpdate(HQLQueryPlan.java:283) at org.hibernate.impl.SessionImpl.executeUpdate(SessionImpl.java:1168) at org.hibernate.impl.QueryImpl.executeUpdate(QueryImpl.java:117) at com.MainTest.main(MainTest.java:54) Caused by: org.postgresql.util.PSQLException: ERROR: update or delete on table "car" violates foreign key constraint "fk95cb6b3a78a8fea5" on table "travel" Detalhe: Key (idcar)=(1) is still referenced from table "travel". at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:1548) at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1316) at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:191) at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:452) at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:351) at org.postgresql.jdbc2.AbstractJdbc2Statement.executeUpdate(AbstractJdbc2Statement.java:305) at org.hibernate.hql.ast.exec.BasicExecutor.execute(BasicExecutor.java:98) -- 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, 7 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3616) Using Query (Object)ocurr violates foreign key

by Clayton K. N. Passos (JIRA)

Using Query (Object)ocurr violates foreign key ---------------------------------------------- Key: HHH-3616 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3616 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1 Environment: "PostgreSQL 8.2.5 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 4.3.0 20080428 (Red Hat 4.3.0-8)" Hibernate core 3.3.1 and only required library Reporter: Clayton K. N. Passos Attachments: Car.hbm.xml, MainTest.java, Travel.hbm.xml -- 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, 7 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3615) C3P0ConnectionProvider now is in a different jar

by Gerhard Langs (JIRA)

C3P0ConnectionProvider now is in a different jar ------------------------------------------------ Key: HHH-3615 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3615 Project: Hibernate Core Issue Type: Bug Components: documentation Affects Versions: 3.3.1 Reporter: Gerhard Langs Priority: Minor A few weeks ago, I upgraded to core 3.3 and replaced hibernate.jar by hibernate-core.jar in my maven configs. worked, fine. Today, it took me about 3 hours to find out, that with the C3P0ConnectionProvider is not in (the new) hibernate-core.jar, but in a separate one. (hibernate-c3p0) So, could you pls update http://www.hibernate.org/214.html ?. (Just found a note here, http://relation.to/Bloggers/HibernateCore330GoesGA) -- 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, 7 months

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 November 2008