This content has been marked as final. Show 4 replies
Thanks for the reply.
I'm using 3.6, so it's weird that there's a 3.5 patch, yet the problem persists in 3.6?
String is a nice idea, but I don't want to incur the performance penalty of turning the date into a string and back.
Is there a similar patch for 3.6?
P.S Sorry for the multiple posts, the web site kept saying there was an error each time I posted.
This issue was identified after 3.6.0 had shipped. While the fix has been made to both the Coherence 3.5 and 3.6 codelines, only the 3.5 version has been made publicly available as a patch. Based on the comments in the issue number, it looks like the 3.6 fix is slated to be part of the upcoming 3.6 SP1 (3.6.1). As for interim work arounds the only thing I can suggest is to encode the value as using the Coherence C++ Integer64 object (equivalent of java.lang.Long), this will allow you to both have a NULL value, as well as a way to encode any date you choose.