3 ms·

If your datetime is persisted ISO 8601 form, RFC 3339 form, some other unambiguously parseable string form, in epoch form, or as some database-native reliable d

by niftich 10y ago

If your datetime is persisted ISO 8601 form, RFC 3339 form, some other unambiguously parseable string form, in epoch form, or as some database-native reliable datetime type, you'll be fine. But if by any chance it's Java-serialized Joda-Time objects, you're going to want to get them out of that form, as the Java-serialized forms are not compatible.

koolba 10y ago
If you're data is persisted in Java-serialized form you should be fired. That's not just for just dates or timestamps either. That's for data period.
- Twirrim 10y ago
  I've horrible memories of WordPress and their obsession with storing PHP serialised objects in the database. It makes a whole lot of things that ought to be simple a lot harder.
  - h1d 10y ago
    It was saving different blog data on different tables prefixed by index numbers. It's a mess.
CydeWeys 10y ago
Looks like our native representation in Datastore is java.util.Date, so we should be in the clear. Relevant code here: https://github.com/google/nomulus/blob/master/java/google/registry/model/translators/ReadableInstantUtcTranslatorFactory.java https://github.com/google/nomulus/blob/master/java/google/re...