public class SFieldTimestamp extends SFieldScalar
sqlDataTypeOverride, theGeneratorquoteName| Constructor and Description |
|---|
SFieldTimestamp(SRecordMeta meta,
java.lang.String columnName,
SFieldFlags... pvals) |
| Modifier and Type | Method and Description |
|---|---|
protected java.lang.Object |
convertToDataSetFieldType(java.lang.Object raw)
Converts the parameter from the raw type parameter to the correct internal Object
type that is stored in the data set.
|
java.lang.String |
defaultSqlDataType()
Time & date is a mess in SQL.
|
boolean |
isFKeyCompatible(SFieldScalar field)
Check if two fields can be used on both sides of a foreign key
relation (same type, length, ...)
|
int |
javaSqlType() |
java.lang.Object |
queryFieldValue(java.sql.ResultSet rs,
int sqlIndex)
Issues a JDBC get*() on the result set for the field and converts the
database type to the appropriate internal type, eg, Double for a double
field.
|
getColumnName, getGeneratorMode, getGeneratorParameter, getMaxSize, getReferences, getTheGenerator, isForeignKey, isGenerated, isMandatory, isNotOptimisticLocked, isPrimary, overrideSqlDataType, setGeneratorMode, setMaxSize, setTheGenerator, toLongerStringaddFlag, addValidator, doValidate, equals, getFieldName, getFlags, getRecordMeta, getUserProperties, getUserProperty, getValidators, hashCode, isDescriptive, isUnqueried, nextGeneratedValue, putUserProperty, readResolve, setQuoted, toString, writeFieldValue, writeFieldValuepublic SFieldTimestamp(SRecordMeta meta, java.lang.String columnName, SFieldFlags... pvals)
public java.lang.Object queryFieldValue(java.sql.ResultSet rs,
int sqlIndex)
throws java.lang.Exception
SFieldMetaqueryFieldValue in class SFieldMetajava.lang.Exceptionprotected java.lang.Object convertToDataSetFieldType(java.lang.Object raw)
throws java.lang.Exception
SFieldMetaSRecordInstance.setObject etc., Not getObject.convertToDataSetFieldType in class SFieldMetajava.lang.Exceptionpublic java.lang.String defaultSqlDataType()
ISO-92: seems to only support TIMESTAMP. Maybe WITH TIME ZONE. HSQL: Seems to support both TIMESTAMP and DATETIME. No WITH TIME ZONE. MSSQL: TIMESTAMP is not a time, but a transaction id like thing. DATETIME is a date time. POSTGRESQL: Appears to support both TIMESTAMP and DATETIME. Suports? WITH TIME ZONE. MySQL: DATETIME and TIMESTAMP are different data types with different precission.
TIMESTAMP is ISO, seems to be lowest common denominator.
defaultSqlDataType in class SFieldScalarpublic boolean isFKeyCompatible(SFieldScalar field)
SFieldScalarpublic int javaSqlType()
javaSqlType in class SFieldScalar