SQL Server 2000 and 2005 do not have separate date and time data types.
When mapping the
The JADE
To save the exact millisecond value, map the time or timestamp property to an INTEGER data type.
Due to the values allowed in an SQL Server DATETIME field, if the value of a
SQL Server 2008 and higher has separate date and time data types. Valid dates are in the range 0001-01-01 through 9999-12-31.
In
In
The following is used to map values from JADE to the SQL Server 2000 and SQL Server 2005 DATETIME data type.
JADE Primitive Type | JADE Value | SQL Server 2000 and 2005 DATETIME Data Type |
---|---|---|
|
0 | Null column |
InvalidDate | Null column | |
Valid SQL Server date | ValidDate, 00:00:00 | |
Invalid SQL Server date | Null column with message to log | |
|
ValidTime (including 0) | TodaysDate if |
1/01/1900 if |
||
InvalidTime | Null column | |
|
SQLServerValidDate, ValidTime (including 0) | Date, Time |
Invalid SQL Server date, ValidTime | Null column with message to log | |
ValidDate, InvalidTime | ValidDate, 00:00:00 | |
InvalidDate, any Time | Null column | |
0, InvalidTime | Null column | |
0, ValidTime (including 0) | TodaysDate, ValidTime if |
|
1/01/1900, ValidTime if |
||
Null column if |
The following table defines the available mappings of JADE types to SQL Server 2008 and higher DATE and TIME data types that differ from the SQL Server 2000 and 2005 mappings listed in the previous table.
JADE Primitive Type | JADE Value | SQL Server 2008 and Higher DATE and TIME Data Types |
---|---|---|
|
Valid SQL Server Date | ValidDate |
Invalid SQL Server Date | Null column with message to log (SQL Server date limits) | |
|
ValidTime (including 0) | ValidTime |