Invalid date in typed literal string causes exception

(In [2375]) re #370 reviewer: lee

Set native value to null if lexical value cannot be parsed.

Lee, is this reasonable? Would it be better to fall back to a default value instead of null?

Lee,

Would you review and close if this is okay?

Thanks

Not really sure what's best.

For some applications, early detection (and exception) is best ... for others, invalid typed literals is OK and the app. chooses to deal with it as it chooses. IIRC, Jena and Sesame provide a configuration option as to how early / whether or not typed literals are checked for validity.

[2375] looks fine, just not sure if it's the best design. I'll leave open for further discussion; if we don't have any other guiding direction for now, please feel free to close.

I believe that returning null is correct. It views the native value as a convenience for converting to Java types that only handles certain datatypes and only when they are well-formed.

The type conversion work done as part of #377 and documented at wiki:AnzoTypeConversions uses this approach which I believe is the correct one. If we change our minds and make it configurable in the future, then we can create an new ticket.