November 2009 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-4529) Support for derived identity (including @MapsId)

by Emmanuel Bernard (JIRA)

Support for derived identity (including @MapsId) ------------------------------------------------ Key: HHH-4529 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4529 Project: Hibernate Core Issue Type: Sub-task Components: annotations Reporter: Emmanuel Bernard Fix For: 3.5 2.4.1.1 IdClass (derived side) "The names of the attributes of the id class and the Id attributes of the dependent entity class must correspond as follows: • The Id attribute in the entity class and the corresponding attribute in the id class must have the same name. • If an Id attribute in the entity class is of basic type, the corresponding attribute in the id class must have the same type. • If an Id attribute in the entity is a many-to-one or one-to-one relationship to a parent entity, the corresponding attribute in the id class must be of the same Java type as the id class or embedded id of the parent entity (if the parent entity has a composite pri- mary key) or the type of the Id attribute of the parent entity (if the parent entity has a simple primary key). " This basically mean that property names int he entity and idClass must match. Types should be identical unless a @Id @XToOne Parent parent; is present in the entity. In this case the corresponding IdClass property should be of the type of the Parent PK "Alternatively, If the dependent entity has a single primary key attribute (i.e., the relationship attribute), the id class specified by the dependent entity must be the same as the primary key class of the parent entity. The Id annotation is applied to the relationship to the parent entity." "If the dependent entity uses an embedded id to represent its primary key, the attribute in the embedded id corresponding to the relationship attribute must be of the same type as the primary key of the parent entity and must be designated by the MapsId annotation applied to the relationship attribute. The value element of the MapsId annotation must be used to specify the name of the attribute within the embedded id to which the relationship attribute corresponds. If the embedded id of the dependent entity is of the same Java type as the primary key of the parent entity, the relationship attribute maps both the relationship to the parent and the primary key of the dependent entity, and in this case the MapsId annotation is specified without the value element." class Person @Id PersonPK id; @MapsId("ssnId") @ManyToOne SSN ssn; static class PersonPK { String name; String ssnId; } } class SSN { @Id String id; } "If the dependent entity has a single primary key attribute (i.e, the relationship attribute or an attribute that corresponds to the relationship attribute) and the primary key of the parent entity is a simple pri- mary key, the primary key of the dependent entity is a simple primary key of the same type as that of the parent entity (and neither EmbeddedId nor IdClass is specified). In this case, either (1) the rela- tionship attribute is annotated Id, or (2) a separate Id attribute is specified and the relationship attribute is annotated MapsId (and the value element of the MapsId annotation is not specified)" "A primary key attribute that is derived from the identity of a parent entity is mapped by the correspond- ing relationship attribute. The default mapping for this relationship is as specified in section 2.10. In the case where a default mapping does not apply or where a default mapping is to be overridden, the JoinColumn or JoinColumns annotation is used on the relationship attribute. If the dependent entity uses an embedded id to represent its primary key, the AttributeOverride annotation may be used to override the default mapping of embedded id attributes that do not corre- spond to the relationship attributes mapping the derived identity. The embedded id attributes that cor- respond to the relationship are treated by the provider as "read only"—that is, any updates to them on the part of the application are not propagated to the database. If the dependent uses an id class, the Column annotation may be used to override the default mapping of Id attributes that are not relationship attributes. " Examples for all that on page 31 -- 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

16 years, 2 months

3
16
0 / 0

[Hibernate-JIRA] Created: (HHH-4610) Hibernate query logging should also display the name of the named query.

by Juraj Holtak (JIRA)

Hibernate query logging should also display the name of the named query. ------------------------------------------------------------------------ Key: HHH-4610 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4610 Project: Hibernate Core Issue Type: Improvement Components: core Environment: all Reporter: Juraj Holtak Priority: Trivial It would be extremely helpful when tuning applications to see the named query name in the log together with the executed SQL. -- 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

16 years, 2 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2501) Read-only state of an entity in a session to propagate into subsequently lazy-loaded entities.

by Gunther Schadow (JIRA)

Read-only state of an entity in a session to propagate into subsequently lazy-loaded entities. ---------------------------------------------------------------------------------------------- Key: HHH-2501 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2501 Project: Hibernate3 Type: Improvement Components: core Environment: any Reporter: Gunther Schadow ISSUE: Given an Entity entity and after Session.setReadOnly(entity), if the entity has lazy collections, lazy properties etc., other Entities are loaded into the Session upon navigating the object graph in the default read-writable state. However, it seems more reasonable to maintain the read-only state of the owning object. REQUEST: Ability to propagate read-only state of an entity in a session into other lazy-loaded entities. BACKGROUND: We have a system which permits users to make concurrent transactions which involve many of the same objects. Usually no changes happen on these shared objects, but instead connections (links) are made between these objects and new objects. For example, say you have an online meeting system, and every Meeting held has a link to a number of User object. The User objects are never changed in a Meeting, but there is a Relation called Participation (of User in Meeting) to which new relationships are added. When a new meeting is saved, it wants to save the User objects simply because a new Participation link entry was added to the collection. To an extent we can prevent this from happening by setting the Users explicitly to read-only. However, now suppose we added a function "Invite your Friends" to a Meeting, in which we would simply go: for(User friend : currentUser.getFriends()) meeting.addInvitation(friend); Now an Invitation is like a Participation, and would be added into the User but now it wants to save these users just for a version upgrade only because they have received an Invitation. -- 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

16 years, 2 months

5
13
0 / 0

[Hibernate-JIRA] Created: (HHH-4552) Support generated value for composite keys

by Ståle W. Pedersen (JIRA)

Support generated value for composite keys ------------------------------------------ Key: HHH-4552 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4552 Project: Hibernate Core Issue Type: Improvement Affects Versions: 3.5.0-Beta-2 Reporter: Ståle W. Pedersen Attachments: annotations.diff, core.diff, test_idclassgeneratedvalue.tar.gz To ensure compatibility/portability with other jpa implementations hibernate need support for generated value for composite keys. The SpecjEnterprise2010 application require this. -- 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

16 years, 2 months

3
17
0 / 0

[Hibernate-JIRA] Created: (METAGEN-5) Make the looging output configurable

by Hardy Ferentschik (JIRA)

Make the looging output configurable ------------------------------------ Key: METAGEN-5 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-5 Project: Hibernate StaticMetamodel Generator Issue Type: Task Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Pass additional attribute to the processor to turn on/off the printing of debug statements via processingEnv.getMessager() -- 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

16 years, 2 months

2
7
0 / 0

[Hibernate-JIRA] Created: (HBX-1074) DelegatingReverseEngineeringStratey.columnToHibernateTypeName reports invalid values

by Joel Schuster (JIRA)

DelegatingReverseEngineeringStratey.columnToHibernateTypeName reports invalid values ------------------------------------------------------------------------------------ Key: HBX-1074 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1074 Project: Hibernate Tools Issue Type: Improvement Components: reverse-engineer Affects Versions: 3.2.1 Environment: MyEclipse w/ Hibernate rev engineering against Oracle 10g Reporter: Joel Schuster When implementing an extention to the [u]DelegatingReverseEngineeringStrategy [/u]the [u]columnToHibernateTypeName [/u]does not report the true value of the [b]precision [/b]and [b]scale [/b]column of the table description/definition. The method signature: [code]@Override public String columnToHibernateTypeName( TableIdentifier table, String columnName, int sqlType, int length, int precision, int scale, boolean nullable, boolean generatedIdentifier) {[/code] The precision and scale parameters are [b]int[/b]. If the values in the definition are [b]null[/b] the values reported here come out as DATA_LENGTH and 0. Not null. These parameters should be [b]Integer[/b] and be set to [b]null [/b]when applicable. -- 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

16 years, 2 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-4616) Configure global/cache level JMX statistics from Hibernate configuration file

by Galder Zamarreno (JIRA)

Configure global/cache level JMX statistics from Hibernate configuration file ----------------------------------------------------------------------------- Key: HHH-4616 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4616 Project: Hibernate Core Issue Type: New Feature Components: caching (L2) Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 3.5 Provide a way in Infinispan cache provider to enable both global and cache level JMX statistics via hibernate.cfg.xml or persistence.xml <globalJmxStatistics enabled="true" jmxDomain="infinispan"/> <jmxStatistics enabled="false"/> These properties will often be enabled by the cache provider users. -- 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

16 years, 2 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-4068) Hibernate's ReadWriteCache synchronization slow down ehcache

by shaoxian yang (JIRA)

Hibernate's ReadWriteCache synchronization slow down ehcache ------------------------------------------------------------- Key: HHH-4068 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4068 Project: Hibernate Core Issue Type: Bug Reporter: shaoxian yang Hi, I am setting up hibernate to work with ehcache. Hibernate has a wrapper to call underlying ehcache. Their wrappers are ReadWriteCache.java, which internally will call Ehcache. The two major methods in ReadWriteCache are synchronized: public synchronized Object get(Object key, long txTimestamp) throws CacheException { public synchronized boolean put( Object key, Object value, long txTimestamp, Object version, Comparator versionComparator, boolean minimalPut) I understand this is to ensure "read/write" strategy to read committed (when write and read thread get in at the same time, read does not get intermediate result and only get the latest committed result). However, isn't this also make concurrent read impossible when there is no write? ). It looks like we need some more advanced read/write lock at ReadWriteCache level. However, the class also have other synchronized methods which make me hesitate: public synchronized SoftLock lock(Object key, Object version) throws CacheException public synchronized void release(Object key, SoftLock clientLock) throws CacheException public synchronized boolean afterUpdate(Object key, Object value, Object version, SoftLock clientLock) throws CacheException public synchronized boolean afterInsert(Object key, Object value, Object version) throws CacheException public synchronized SoftLock lock(Object key, Object version) throws CacheException Basically I want to get the most out of ehcache performance gain. Currently, if I keep issuing the same query which read item from query cache, there is still overhead. Can you advise me why we have to use read lock for every read when there is no write? And is it necessary to acquire lock for any other operation than put/get in ReadWriteCache class? Thanks in advance. -- 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

16 years, 2 months

2
2
0 / 0

[Hibernate-JIRA] Created: (METAGEN-6) Moce xml parsing code in JPAMetaModelEntityProcessor into a separate class

by Hardy Ferentschik (JIRA)

Moce xml parsing code in JPAMetaModelEntityProcessor into a separate class -------------------------------------------------------------------------- Key: METAGEN-6 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-6 Project: Hibernate StaticMetamodel Generator Issue Type: Task Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik -- 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

16 years, 2 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-4455) Changes are not properly rollbacked after a bulk operation involving classes that use joined-subclass mapping

by dilbert (JIRA)

Changes are not properly rollbacked after a bulk operation involving classes that use joined-subclass mapping ------------------------------------------------------------------------------------------------------------- Key: HHH-4455 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4455 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.3.0.SP1, 3.2.5 Environment: Hibernate 3.2.5.ga and 3.3.0.SP1 MySql database version 5.1.36 Driver : mysql-connector-java-5.1.6 Reporter: dilbert Attachments: TransactionTest.zip I have a Location class on which two other classes "depend" (Contact and LocationTransaction). When I want to delete a Location Object I use bulk update operations. First I delete the LocationTransactions connected to the Location object and then I delete the contact objects connected to the location object. Finally I delete the Location object itself. At the end I simulate that something went wrong and trigger a Rollback. After the rollback I would expect that none of the objects that I tried to delete was actually deleted. However, all the LocationTransaction objects are missing from the database after the rollback. Since the other objects are rollbacked properly I figure that the problem is connected to the fact that LocationTransactions is inherited from Transaction and uses joined-subclass mapping which is included in the test project in the attachment. private static void doTest() { final Session s = sf.openSession(); final Transaction tx = s.beginTransaction(); try { Location l = (Location) s.createQuery("from Location l where l.name = 'l1'").uniqueResult(); final Query deleteTransactionQuery = s.createQuery( "delete from LocationTransaction lt " + "where lt.location = (:location)"); deleteTransactionQuery.setParameter("location", l); deleteTransactionQuery.executeUpdate(); final Query deleteContactQuery = s.createQuery( "delete from Contact c " + "where c.location = (:location)"); deleteContactQuery.setParameter("location", l); deleteContactQuery.executeUpdate(); final Query deleteQuery = s.createQuery( "delete from Location l where l = (:location)"); deleteQuery.setParameter("location", l); deleteQuery.executeUpdate(); //s.delete(l); throw new RuntimeException("test"); //tx.commit(); } catch (Exception e) { tx.rollback(); System.out.println(e); } finally { s.close(); } } Please contact me with any further questions. Thanks for the help. -- 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

16 years, 2 months

1
1
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 November 2009