4 ms·
Java 8 isn't supported quite yet on App Engine :-( Support is in beta, and should hopefully be available "for real" within months, but until it is, we're stuck
by CydeWeys 10y ago
Java 8 isn't supported quite yet on App Engine :-( Support is in beta, and should hopefully be available "for real" within months, but until it is, we're stuck with the old stuff.
I also wonder what kind of data migration we'll be facing, since all of our persisted data is from Joda DateTimes, not Java 8 ones. Hopefully none.
- niftich 10y agoIf 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 agoIf 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.
- CydeWeys 10y agoLooks 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...
- shabbyrobe 10y agoCheck out the ThreeTen backport for a mostly API-compatible Java 6/7 version of the Java 8 date API: http://www.threeten.org/threetenbp/ http://www.threeten.org/threetenbp/
- jcrites 10y agoFYI: Java 9 is scheduled for release in July. http://openjdk.java.net/projects/jdk9/ http://openjdk.java.net/projects/jdk9/