Chapter 2. Mapping Entities - 0 views
-
Composite identifier
-
You can define a composite primary key through several syntaxes:
-
@EmbeddedId
- ...66 more annotations...
-
map multiple properties as @Id properties
-
annotated the property as
-
map multiple properties as @Id properties and declare an external class to be the identifier type
-
declared on the entity via the @IdClass annotation
-
The identifier type must contain the same properties as the identifier properties of the entity: each property name must be the same, its type must be the same as well if the entity property is of a
-
basic type
-
last case is far from obvious
-
recommend you not to use it (for simplicity sake)
-
@EmbeddedId property
-
@EmbeddedId
-
@Embeddable
-
@EmbeddedId
-
@Embeddable
-
@Embeddable
-
@EmbeddedId
-
Multiple @Id properties
-
arguably more natural, approach
-
place @Id on multiple properties of my entity
-
only supported by Hibernate
-
does not require an extra embeddable component.
-
@IdClass
-
@IdClass on an entity points to the class (component) representing the identifier of the class
-
WarningThis approach is inherited from the EJB 2 days and we recommend against its use. But, after all it's your application and Hibernate supports it.
-
Mapping entity associations/relationships
-
One-to-one
-
three cases for one-to-one associations:
-
associated entities share the same primary keys values
-
foreign key is held by one of the entities (note that this FK column in the database should be constrained unique to simulate one-to-one multiplicity)
-
association table is used to store the link between the 2 entities (a unique constraint has to be defined on each fk to ensure the one to one multiplicity)
-
@PrimaryKeyJoinColumn
-
shared primary keys:
-
explicit foreign key column:
-
@JoinColumn(name="passport_fk")
-
foreign key column named passport_fk in the Customer table
-
may be bidirectional
-
owner is responsible for the association column(s) update
-
In a bidirectional relationship, one of the sides (and only one) has to be the owner
-
To declare a side as
-
not responsible for the relationship
-
the attribute
-
mappedBy
-
is used
-
mappedBy
-
Indexed collections (List, Map)
-
Lists can be mapped in two different ways:
-
as ordered lists
-
as indexed lists
-
@OrderBy("number")
-
List<Order>
-
List<Order>
-
List<Order>
-
To use one of the target entity property as a key of the map, use
-
@MapKey(name="myProperty")
-
@MapKey(name"number")
-
Map<String,Order>
-
String number
-
-
@MapKeyJoinColumn/@MapKeyJoinColumns
-
if the map key type is another entity
-
@ManyToAny
-
2.4.5.2. @Any
-
@Any annotation defines a polymorphic association to classes from multiple tables
-
this is most certainly not meant as the usual way of mapping (polymorphic) associations.
-
@ManyToAny allows polymorphic associations to classes from multiple tables
-
first column holds the type of the associated entity
-
remaining columns hold the identifier
-
not meant as the usual way of mapping (polymorphic) associations
