JoinTable
- Implemented Interfaces:
Annotation
A join table is typically used in the mapping of many-to-many and unidirectional one-to-many associations. It may also be used to map bidirectional many-to-one/one-to-many associations, unidirectional many-to-one relationships, and one-to-one associations (both bidirectional and unidirectional).
When a join table is used in mapping a relationship with an embeddable class on the owning side of the relationship, the containing entity rather than the embeddable class is considered the owner of the relationship.
If the JoinTable
annotation is missing, the default values of the annotation elements apply. The name of the join table is assumed to be the table names of the associated primary tables concatenated together (owning side first) using an underscore.
@JoinTable( name="CUST_PHONE", joinColumns= @JoinColumn(name="CUST_ID", referencedColumnName="ID"), inverseJoinColumns= @JoinColumn(name="PHONE_ID", referencedColumnName="ID") )
- See Also:
JoinColumn
JoinColumns
- Since:
- JPA 1.0
Public Annotation Attributes
Defaults to the default catalog.
- Since:
- JPA 1.0
foreignKey
element of any of the joinColumns
elements are specified, the behavior is undefined. If no foreign key annotation element is specified in either location, the persistence provider's default foreign key strategy will apply. - Since:
- JPA 2.1
foreignKey
element of any of the inverseJoinColumns
elements are specified, the behavior is undefined. If no foreign key annotation element is specified in either location, the persistence provider's default foreign key strategy will apply. - Since:
- JPA 2.1
Uses the same defaults as for JoinColumn.
- Since:
- JPA 1.0
Uses the same defaults as for JoinColumn.
- Since:
- JPA 1.0
Defaults to the concatenated names of the two associated primary entity tables, separated by an underscore.
- Since:
- JPA 1.0
Defaults to the default schema for user.
- Since:
- JPA 1.0
Defaults to no additional constraints.
- Since:
- JPA 1.0