4 Replies Latest reply on Oct 29, 2010 1:28 PM by Mfalco-Oracle

    POF Serializer, problems with large dates


      I seem to have run into a problem with POF serialization of dates. For some reason the C++ deserialization of dates checks the date to see if it's valid. This seems beyond the bounds of a serializer, however performance aside the POF rawDateTime thinks that the year 1/1/3000 is an invalid date. We have some fields with dates far in the future, I know the database, java, and our c++ can handle these dates.

      The second approach is to serialize the date to a long, however the date can be null. So how do I represent a null date? Maybe I could use 0 or -1, however this introduces a compare for every date we serialize, something which I want to avoid.

      Is there a way of telling the c++ coherence POF serializer that this date is not out of range?