December 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-3648) Assign a @Version property using revision info for @Versioned entities

by Alexey Kaigorodov (JIRA)

Assign a @Version property using revision info for @Versioned entities ---------------------------------------------------------------------- Key: HHH-3648 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3648 Project: Hibernate Core Issue Type: New Feature Components: envers Reporter: Alexey Kaigorodov An integer @Version property may be assigned using revision number, a date @Version property using revision timestamp. I guess, this can be default behavior for versioned entities but it would be useful even as an optional feature. -- 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, 5 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3197) subquery is not valid SQL when select type is same as parent sql select type

by Nicolai Marck Ødum (JIRA)

subquery is not valid SQL when select type is same as parent sql select type ---------------------------------------------------------------------------- Key: HHH-3197 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3197 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.6 Environment: Java 1.5.0_14 JBoss 4.2.2.GA (Hibernate 3.2.1) - I have also tried with Hibernate 3.2.6.ga, hibernate-annotations-3.3.1.GA and hibernate-entitymanager-3.3.2.GA with same result. PostgreSQL 8.3.0 WindowsXP Reporter: Nicolai Marck Ødum The following ejb3 QL: "Delete FROM Notification noti WHERE noti NOT IN (SELECT subNoti.notifications FROM SubscriberNotification subNoti)" Result in the following sql "delete from Notification where id not in (select . from SubscriberNotification subscriber1_, SubscriberNotification_Notification notificati2_, Notification notificati3_ where subscriber1_.id=notificati2_.SubscriberNotification_id and notificati2_.notifications_id=notificati3_.id)" notice the "select . from" in the subquery if I alter the sql to be "delete from Notification where id not in (select notificati3_.id from SubscriberNotification subscriber1_, SubscriberNotification_Notification notificati2_, Notification notificati3_ where subscriber1_.id=notificati2_.SubscriberNotification_id and notificati2_.notifications_id=notificati3_.id)" I have not been able to create a workaround. -- 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, 5 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3645) Bug with list when rearranging - treat it as urgent

by leela (JIRA)

Bug with list when rearranging - treat it as urgent --------------------------------------------------- Key: HHH-3645 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3645 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1 Reporter: leela Class A has a child list specifying an association to another class B. Table A AId Table B BId Table C(Association Table with 3 columns) AId(Id of Table A) BId(Id of Table B) SeqNo OtherColumn1 OtherColumn2 When I rearrange the child list, obviously the index will be changing. Initially the table C was mapped like this before rearranging. A1 B1 0 XX YY A1 B2 1 YY ZZ A1 B3 2 ZZ XX After rearranging the java list contains : A1 B2 0 XX YY A1 B1 1 XX YY A2 B3 2 ZZ XX But when this list is getting persisted, hibernate is trying to do an update by seq no update tablec set table Bid = B2 where Aid = A1 and SeqNo = 0 It fails to persit because since we had set a unique composite index on AId and BId. That means hibernate was trying to persist like this, that caused the failures. A1 B2 0 A1 B2 1 A1 B3 2 Here is my hibernate mapping in classA mapping file. <list name="assocList" lazy="true" access="field" cascade="save-update" outer-join="false" table="tablec"> <key column="aid" not-null="true" unique="false"/> <list-index column="seqno"/> <composite-element class="ClassC"> <many-to-one name="ClassB" column="bid" lazy="proxy"/> <property ..../> <property ..../> </composite-element> </list> Should not hibernate supposed to delete and reinsert the child elements? Then what is the solution for this? Is not this a bug? -- 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, 5 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-2383) Generated SQL using setMaxResults/setFirstResult duplicate entities in the first page and subsequent pages in Oracle.

by Carlos Eugênio P. da Purificação (JIRA)

Generated SQL using setMaxResults/setFirstResult duplicate entities in the first page and subsequent pages in Oracle. --------------------------------------------------------------------------------------------------------------------- Key: HHH-2383 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2383 Project: Hibernate3 Type: Bug Components: query-hql Versions: 3.2.2 Environment: Hibernate 3.2.2 GA, Oracle 10 Reporter: Carlos Eugênio P. da Purificação Attachments: test.zip The generated SQL using setMaxResults/setFirstResult duplicate entities in the first page and subsequent pages. -- 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, 5 months

3
3
0 / 0

[Hibernate-JIRA] Commented: (HHH-912) Use of DetachedCriteria

by Chris Braun (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-912?page=co... ] Chris Braun commented on HHH-912: --------------------------------- I am also working with a DetachedCriteria and would like to find out how to use setMaxResults() and setFirstResult() but I don't see them available in the v3 API. Because of the lack of response to this over the last 3 years, I feel I must be missing something. Is there some other way to set these limits on a DetachedCriteria? > Use of DetachedCriteria > ----------------------- > > Key: HHH-912 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-912 > Project: Hibernate Core > Issue Type: Improvement > Components: core > Affects Versions: 3.0.5 > Environment: All > Reporter: Frank Verbruggen > Priority: Minor > > The class org.hibernate.criterion.DetachedCriteria should represent a criteria object on which all the operations available to a Criteria object that do NOT require a Session object are available. > Two such operations are setFirstResult() and setMaxResults(). > These are unfortunately enough not available. > There probably are more methods missing that need to be added but these two in particular are important to me. > See http://opensource2.atlassian.com/projects/spring/browse/SPR-1254. > Can they be added in the next release ? > Kind regards > Frank Verbruggen -- 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, 5 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3643) PersistentList shouldn't add a null element where a regular element exists

by Christophe Boutter (JIRA)

PersistentList shouldn't add a null element where a regular element exists -------------------------------------------------------------------------- Key: HHH-3643 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3643 Project: Hibernate Core Issue Type: Improvement Components: core Environment: SVN Revision 15680, all plattforms. Reporter: Christophe Boutter Priority: Minor Attachments: patch.txt The readFrom() method of PersistentList does a null padding for the indexes where there are no elements in the database. The actual problem is that the method adds a null element at the index of the next element and then replacing it with the element instead of just adding the next element. Thus in a List without any padding you get 2n operations for a List of size n instead of just n operations. I added a patch with a solution to the problem. -- 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, 5 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3641) Add tableName argument to the NamingStrategy columnName method

by Paweł Kępka (JIRA)

Add tableName argument to the NamingStrategy columnName method -------------------------------------------------------------- Key: HHH-3641 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3641 Project: Hibernate Core Issue Type: New Feature Components: core Reporter: Paweł Kępka Priority: Minor I have a database where each table has its suffix (for instance ITEM_IT) and where columns in the tables are prefixed with this suffix (id column for ITEM_IT is ITID). I would like to use NamingStrategy to declare id property in entities super class with column name ID and not to have to override it in each subclass. The easiest solution which would work for me would be adding new argument for columnName method in the NamingStrategy interface: String columnName(String tableName, String columnName); I guess it could be useful in other cases too. -- 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, 5 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3638) Ability to use Criteria with Queries

by Adriano dos Santos Fernandes (JIRA)

Ability to use Criteria with Queries ------------------------------------ Key: HHH-3638 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3638 Project: Hibernate Core Issue Type: New Feature Components: core, query-criteria, query-hql, query-sql Reporter: Adriano dos Santos Fernandes I done it, for my needs, using internal classes. It would be very great to have this nativelly on Hibernate. Query createQueryByExample(Query query, Entidade entity) { SessionImpl session = (SessionImpl) entityManager.getDelegate(); Class<?> entityClass = entity.getClass(); CriteriaImpl criteria = (CriteriaImpl) session.createCriteria(entityClass); CriteriaQueryTranslator criteriaQuery = new CriteriaQueryTranslator( session.getFactory(), criteria, entityClass.getName(), "z"); Example example = Example.create(entity) .enableLike(MatchMode.START) .excludeZeroes(); criteria.add(example); String newSql = "select * from (" + ((HibernateQuery) query).getHibernateQuery().getQueryString() + ") z"; Object[] params = criteriaQuery.getQueryParameters().getPositionalParameterValues(); if (params.length > 0) { String newWhere = example.toSqlString(criteria, criteriaQuery); newSql += "\nwhere " + newWhere; query = entityManager.createNativeQuery(newSql, entityClass); int n = 0; for (Object param : params) query.setParameter(++n, param); } return query; } -- 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, 5 months

1
0
0 / 0

[Hibernate-JIRA] Created: (EJB-382) PersistenceException instead of EntityExistsException thrown when entity already exists

by Miro Bezjak (JIRA)

PersistenceException instead of EntityExistsException thrown when entity already exists --------------------------------------------------------------------------------------- Key: EJB-382 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-382 Project: Hibernate Entity Manager Issue Type: Bug Components: EntityManager Affects Versions: 3.4.0.GA Reporter: Miro Bezjak Priority: Minor Attachments: hibernate.zip By specification of EntityManager (http://java.sun.com/javaee/5/docs/api/javax/persistence/EntityManager.htm...) an EntityExistsException should be thrown when entity already exists but current implementation of AbstractEntityManagerImpl throws PersistenceException. I noticed the bug when upgrading from 3.3.2.GA (throws EntityExistsException properly) to 3.4.0.GA. It seems that problem is in throwPersistenceException method. 3.3.2.GA has following code: " else if ( e instanceof ConstraintViolationException ) { //FIXME this is bad cause ConstraintViolationException happens in other circumstances throwPersistenceException( new EntityExistsException( e ) ); } " but that was dropped in 3.4.0.GA (maybe because of http://opensource.atlassian.com/projects/hibernate/browse/EJB-349 ?). Anyway, stack trace for attached example: javax.persistence.PersistenceException: org.hibernate.exception.ConstraintViolationException: could not insert: [test.User] at org.hibernate.ejb.AbstractEntityManagerImpl.throwPersistenceException(AbstractEntityManagerImpl.java:614) at org.hibernate.ejb.AbstractEntityManagerImpl.persist(AbstractEntityManagerImpl.java:226) -- 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, 5 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3636) Attempt to read invalid column when loading collection of subclasses mapped with table-per-subclass with discriminator

by Chris Bredesen (JIRA)

Attempt to read invalid column when loading collection of subclasses mapped with table-per-subclass with discriminator ---------------------------------------------------------------------------------------------------------------------- Key: HHH-3636 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3636 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1, 3.2.6, 3.2.4.sp1 Reporter: Chris Bredesen Assignee: Chris Bredesen Priority: Minor This problem is described in this forum post: http://forum.hibernate.org/viewtopic.php?t=992703&highlight Hibernate attempts to read an invalid column from the collection result set when the following conditions are present: 1. Instances of a subclass are contained in a collection 2. The subclasses are single-table + a <join> (table-per-subclass with discriminator) 3. The <join> portion of the subclass contains at least 3 of its own columns -- 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, 5 months

1
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues December 2008