SecondaryTable
Target: TYPE
- Implemented Interfaces:
Annotation
Specifies a secondary table for the annotated entity class. Specifying one or more secondary tables indicates that the data for the entity class is stored across multiple tables.
If no SecondaryTable
annotation is specified, it is assumed that all persistent fields or properties of the entity are mapped to the primary table. If no primary key join columns are specified, the join columns are assumed to reference the primary key columns of the primary table, and have the same names and types as the referenced primary key columns of the primary table.
Single secondary table with a single primary key column. @Entity @Table(name="CUSTOMER") @SecondaryTable(name="CUST_DETAIL", pkJoinColumns=@PrimaryKeyJoinColumn(name="CUST_ID")) public class Customer { ... }Example 2:
Single secondary table with multiple primary key columns. @Entity @Table(name="CUSTOMER") @SecondaryTable(name="CUST_DETAIL", pkJoinColumns={ @PrimaryKeyJoinColumn(name="CUST_ID"), @PrimaryKeyJoinColumn(name="CUST_TYPE")}) public class Customer { ... }
- Since:
- JPA 1.0
Public Annotation Attributes
String catalog default ""
Defaults to the default catalog.
- Since:
- JPA 1.0
If both this element and the
foreignKey
element of any of the pkJoinColumns
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
String name default null
- Since:
- JPA 1.0
Defaults to the column(s) of the same name(s) as the primary key column(s) in the primary table.
- Since:
- JPA 1.0
String schema default ""
Defaults to the default schema for user.
- Since:
- JPA 1.0
These are typically only used if table generation is in effect. These constraints apply in addition to any constraints specified by the
Column
and JoinColumn
annotations and constraints entailed by primary key mappings. Defaults to no additional constraints.
- Since:
- JPA 1.0