Changes between Initial Version and Version 1 of Ticket #845
- Timestamp:
- 08/10/12 14:26:35 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #845
- Property Status new → assigned
-
Ticket #845 – Description
initial v1 3 3 1) a corrupted date (year == 0) may be returned from the expression engine 4 4 5 2) an exception may be thrown when reading an unman ged FdoDateTime value and converting it to a System.DateTime value5 2) an exception may be thrown when reading an unmanaged FdoDateTime value and converting it to a System.DateTime value 6 6 7 For the Expression Engine, exceptions are thrown for invalid months/days/etc... so an invalid year should also be handled in t eh same manner. It is a long term goal that the EE become more forgiving whebn handling DateTime values, but that llarger change is not currently in scope for FDO 3.8.7 For the Expression Engine, exceptions are thrown for invalid months/days/etc... so an invalid year should also be handled in the same manner. It is a long term goal that the EE become more forgiving when handling DateTime values, but that larger change is not currently in scope for FDO 3.8. 8 8 9 For the FDO Managed API, the date conversion typically happens when reading date values using the FdoIReader interface. Throwing exceptions when reading invalid dat store dates can be fatal to an application and in retropsect does not need to be treated as a hard failure.9 For the FDO Managed API, the date conversion typically happens when reading date values using the FdoIReader interface. Throwing exceptions when reading invalid data store dates can be fatal to an application and in retrospect does not need to be treated as a hard failure.