[This KA was unapproved and obsolete when migrated.] Why do I get "invalid format" for the date field?
Article ID: KB0087714
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix BusinessWorks Plug-in for Database | - |
| Not Applicable | - |
Description
Resolution:
There is one known problem with the ActiveEnterprise dateTime type: it supports only datetimes in the range 00:00:00 1/1/1970 to 19:14:07 1/18/2038. This limitation is due to the fact that the Adapter SDK MDateTime
class, which implements the ActiveEnterprise dateTime type, relies on the time_t data type, which cannot handle dates outside the stated range. In a database, dates outside of this range are often stored, so we decided the best way to capture this is with a string. We had to pick an arbitrary date string format, so we chose: yyyy-mm-dd hh:mm:ss.xxx At the moment, ADB cannot recognize multiple date formats. In other words, if you need to send a date to ADB and have it put into the database, send the date in yyyy-mm-dd hh:mm:ss.xxx format.
There is one known problem with the ActiveEnterprise dateTime type: it supports only datetimes in the range 00:00:00 1/1/1970 to 19:14:07 1/18/2038. This limitation is due to the fact that the Adapter SDK MDateTime
class, which implements the ActiveEnterprise dateTime type, relies on the time_t data type, which cannot handle dates outside the stated range. In a database, dates outside of this range are often stored, so we decided the best way to capture this is with a string. We had to pick an arbitrary date string format, so we chose: yyyy-mm-dd hh:mm:ss.xxx At the moment, ADB cannot recognize multiple date formats. In other words, if you need to send a date to ADB and have it put into the database, send the date in yyyy-mm-dd hh:mm:ss.xxx format.
Issue/Introduction
[This KA was unapproved and obsolete when migrated.]
Why do I get "invalid format" for the date field?
Environment
Product: TIBCO Adapter for ActiveDatabase
Version:
OS:
--------------------
Feedback
Yes
No
Powered by
