[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
14 years, 5 months
[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
14 years, 5 months
[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
14 years, 5 months
[Hibernate-JIRA] Created: (HHH-4736) Cannot pass ValidatorFactory into PersistenceProvider.createContainerEntityManagerFactory(PersistenceUnitInfo, Map)
by Mike Youngstrom (JIRA)
Cannot pass ValidatorFactory into PersistenceProvider.createContainerEntityManagerFactory(PersistenceUnitInfo, Map)
-------------------------------------------------------------------------------------------------------------------
Key: HHH-4736
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4736
Project: Hibernate Core
Issue Type: Bug
Components: entity-manager
Affects Versions: 3.5.0-Beta-2
Reporter: Mike Youngstrom
The javadocs for PersistenceProvider.createContainerEntityManagerFactory(PersistenceUnitInfo, Map) says:
If a Bean Validation provider is present in the classpath, the container must pass the ValidatorFactoryinstance in the map with the key "javax.persistence.validation.factory".
However, all non string values are stripped from the provided Map by Ejb3Configuration.configure(PersistenceUnitInfo, Map):463, ConfigurationHelper.overrideProperties() making it impossible to pass a ValidatorFactory using the "map". Passing a ValidatorFactory into PersistenceProvider.createEntityManagerFactory(String, Map) works fine since Ejb3Configuration.configure(String, Map) doesn't strip all non Strings from the map.
As a work around it appears a ValidatorFactory can be passed into the properties of the PersistenceUnitInfo.
Thanks,
Mike
--
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
14 years, 5 months