public class CreationTimestampGeneration extends Object implements AnnotationValueGeneration<CreationTimestamp>
CreationTimestamp.| Constructor and Description |
|---|
CreationTimestampGeneration() |
| Modifier and Type | Method and Description |
|---|---|
String |
getDatabaseGeneratedReferencedColumnValue()
For values which are generated in the database (
ValueGeneration.getValueGenerator() == null), if the
column will be referenced in the SQL (ValueGeneration.referenceColumnInSql() == true), what value should be
used in the SQL as the column value. |
GenerationTiming |
getGenerationTiming()
When is this value generated : NEVER, INSERT, ALWAYS (INSERT+UPDATE)
|
ValueGenerator<?> |
getValueGenerator()
Obtain the in-VM value generator.
|
void |
initialize(CreationTimestamp annotation,
Class<?> propertyType)
Initializes this generation strategy for the given annotation instance.
|
boolean |
referenceColumnInSql()
For values which are generated in the database (
ValueGeneration.getValueGenerator() == null), should the
column be referenced in the INSERT / UPDATE SQL?
This will be false most often to have a DDL-defined DEFAULT value be applied on INSERT |
public void initialize(CreationTimestamp annotation, Class<?> propertyType)
AnnotationValueGenerationinitialize in interface AnnotationValueGeneration<CreationTimestamp>annotation - an instance of the strategy's annotation type. Typically implementations will retrieve the
annotation's attribute values and store them in fields.propertyType - the type of the property annotated with the generator annotation. Implementations may use
the type to determine the right ValueGenerator to be applied.public GenerationTiming getGenerationTiming()
ValueGenerationgetGenerationTiming in interface ValueGenerationpublic ValueGenerator<?> getValueGenerator()
ValueGenerationnull. In fact for values that are generated "in the database" via execution of the
INSERT/UPDATE statement, the expectation is that null be returned heregetValueGenerator in interface ValueGenerationpublic boolean referenceColumnInSql()
ValueGenerationValueGeneration.getValueGenerator() == null), should the
column be referenced in the INSERT / UPDATE SQL?
This will be false most often to have a DDL-defined DEFAULT value be applied on INSERTreferenceColumnInSql in interface ValueGenerationtrue indicates the column should be included in the SQL.public String getDatabaseGeneratedReferencedColumnValue()
ValueGenerationValueGeneration.getValueGenerator() == null), if the
column will be referenced in the SQL (ValueGeneration.referenceColumnInSql() == true), what value should be
used in the SQL as the column value.
Generally this will be a function call or a marker (DEFAULTS).
NOTE : for in-VM generation, this will not be called and the column value will implicitly be a JDBC parameter ('?')getDatabaseGeneratedReferencedColumnValue in interface ValueGenerationCopyright © 2017 JBoss by Red Hat. All rights reserved.