I needed to resolve this issue *today* and decided that rather than creating special weird datetimes, it's better to have a date be a date, and have the JSON code deal in date() values rather than now() values, as the former are far more common in models. At least in our code. What are others' experiences?
I opened a pull request: https://github.com/ChicagoBoss/ChicagoBoss/pull/501 In theory, now() values should not be negative: Timestamp = timestamp() timestamp() = {MegaSecs :: integer() >= 0, Secs :: integer() >= 0, MicroSecs :: integer() >= 0} So they're a lot less flexible than dates and datetimes in any case. I'm happy to keep working on a solution that fits everyone's needs, but I needed to pull the trigger on this so that our site wasn't showing elderly people being born in 2033. -- David N. Welton http://www.welton.it/davidw/ http://www.dedasys.com/ -- You received this message because you are subscribed to the Google Groups "ChicagoBoss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at http://groups.google.com/group/chicagoboss. To view this discussion on the web visit https://groups.google.com/d/msgid/chicagoboss/CA%2Bb9R_ux1isNSQyDDrUMvG8vMTZiBVtfnvpPYLirD0vyTq6m5A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
