Subscribe

You can track all active APARs for this component.

APAR status

Closed as program error.

Error description

When inserting a datetime object into SQL Server 2005 using Cast
Iron there is some incorrect conversion going on if the DB
connector expects it to be 3 digits for milliseconds.
The following are some examples.
If we have a datetime xml object 2013-01-28T12:44:12.62 it
inserts into SQL server as 2013-01-28 12:44:12.063
If we have a datetime xml object 2013-01-28T12:43:04.87 it
inserts into SQL server as 2013-01-28 12:43:04.087

Local fix

Problem summary

When inserting a datetime object into a database using Cast
Iron, incorrect conversion was occurring on the date/time stamps
being inserted.
The following are some examples.
If we have a datetime xml object 2013-01-28T12:44:12.62 it
inserts into SQL server as 2013-01-28 12:44:12.063
If we have a datetime xml object 2013-01-28T12:43:04.87 it
inserts into SQL server as 2013-01-28 12:43:04.087
This was occurring because the Cast Iron database connector
was incorrectly handling the millisecond values.