Annotation Interface Column
If no Column
annotation is explicitly specified, the
default values apply.
Example 1:
Example 2:
Example 3:
Portable applications which make use of schema generation should
explicitly specify the precision()
and scale()
of
columns of type numeric
or decimal
.
- Since:
- 1.0
-
Optional Element Summary
Modifier and TypeOptional ElementDescription(Optional) Check constraints to be applied to the column.(Optional) The SQL fragment that is used when generating the DDL for the column.(Optional) A comment to be applied to the column.boolean
(Optional) Whether the column is included in SQL INSERT statements generated by the persistence provider.int
(Optional) The column length.(Optional) The name of the column.boolean
(Optional) Whether the database column is nullable.(Optional) A SQL fragment appended to the generated DDL which declares this column.int
(Optional) The precision for a column of SQL typedecimal
ornumeric
, or of similar database-native type.int
(Optional) The scale for a column of SQL typedecimal
ornumeric
, or of similar database-native type.int
(Optional) The number of decimal digits to use for storing fractional seconds in a SQLtime
ortimestamp
column.(Optional) The name of the table that contains the column.boolean
(Optional) Whether the column is a unique key.boolean
(Optional) Whether the column is included in SQL UPDATE statements generated by the persistence provider.
-
Element Details
-
name
String name(Optional) The name of the column. Defaults to the property or field name.- Default:
- ""
-
unique
boolean unique(Optional) Whether the column is a unique key. This is a shortcut for theUniqueConstraint
annotation at the table level and is useful for when the unique key constraint corresponds to only a single column. This constraint applies in addition to any constraint entailed by the primary key mapping and to constraints specified at the table level.- Default:
- false
-
nullable
boolean nullable(Optional) Whether the database column is nullable.- Default:
- true
-
insertable
boolean insertable(Optional) Whether the column is included in SQL INSERT statements generated by the persistence provider.- Default:
- true
-
updatable
boolean updatable(Optional) Whether the column is included in SQL UPDATE statements generated by the persistence provider.- Default:
- true
-
columnDefinition
String columnDefinition(Optional) The SQL fragment that is used when generating the DDL for the column.Defaults to the generated SQL to create a column of the inferred type.
The specified DDL must be written in the native SQL dialect of the target database, and is not portable across databases.
- Default:
- ""
-
options
String options(Optional) A SQL fragment appended to the generated DDL which declares this column. May not be used in conjunction withcolumnDefinition()
.The specified DDL must be written in the native SQL dialect of the target database, and is not portable across databases.
- Since:
- 3.2
- Default:
- ""
-
table
String table(Optional) The name of the table that contains the column. If absent the column is assumed to be in the primary table.- Default:
- ""
-
length
int length(Optional) The column length.Applies only to columns whose type is parameterized by length, for example,
varchar
orvarbinary
types.- Default:
- 255
-
precision
int precision(Optional) The precision for a column of SQL typedecimal
ornumeric
, or of similar database-native type.Applies only to columns of exact numeric type.
The default value
0
indicates that a provider-determined precision should be inferred.- Default:
- 0
-
scale
int scale(Optional) The scale for a column of SQL typedecimal
ornumeric
, or of similar database-native type.Applies only to columns of exact numeric type.
The default value
0
indicates that a provider-determined scale should be inferred.- Default:
- 0
-
secondPrecision
int secondPrecision(Optional) The number of decimal digits to use for storing fractional seconds in a SQLtime
ortimestamp
column.Applies only to columns of time or timestamp type.
The default value
-1
indicates that fractional seconds should not be stored in atime
column, or that the maximum number of digits supported by the database and JDBC driver should be stored in atimestamp
column.- Since:
- 3.2
- Default:
- -1
-
check
CheckConstraint[] check(Optional) Check constraints to be applied to the column. These are only used if table generation is in effect.- Since:
- 3.2
- Default:
- {}
-
comment
String comment(Optional) A comment to be applied to the column. This is only used if table generation is in effect.- Since:
- 3.2
- Default:
- ""
-