Changes between Initial Version and Version 1 of Ticket #845


Ignore:
Timestamp:
Aug 10, 2012, 2:26:35 PM (12 years ago)
Author:
gregboone
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #845

    • Property Status newassigned
  • Ticket #845 – Description

    initial v1  
    331) a corrupted date (year == 0) may be returned from the expression engine
    44
    5 2) an exception may be thrown when reading an unmanged FdoDateTime value and converting it to a System.DateTime value
     52) an exception may be thrown when reading an unmanaged FdoDateTime value and converting it to a System.DateTime value
    66
    7 For the Expression Engine, exceptions are thrown for invalid months/days/etc... so an invalid year should also be handled in teh 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.
     7For 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.
    88
    9 For the FDO Managed API, the date conversion typically happens when reading date values using the FdoIReader interface. Throwing exceptions when reading invalid datstore dates can be fatal to an application and in retropsect does not need to be treated as a hard failure.
     9For 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.