|Re: [eclipselink-users] question about date/timestamp|
There is no best practice that I am aware of. You should carefully read the assumptions that come with the java date-types and the database date-types (e.g. http://download.oracle.com/docs/cd/E11882_01/server.112/e17118.pdf, 3-17++). This topic can get really troublesome if you start to consider leap seconds ;-). The most profound discussion about date/time-values that I know of is in the XSD-specification: http://www.w3.org/TR/xmlschema-2/#dateTime -- Frank Scott Lewis-2 wrote: > > Hi Folks, > > Apologies in advance if this is a faq, but I don't track this mailing > list constantly. > > Is there an appropriate/approved/conventional way of handling > timezone/date/time values within jpa? That is, I would like to persist > date and time (down to milliseconds), and expect to have these date and > time values coming from processes that are not expected to have > perfectly synchronized clocks. > > It it typical to persist timezone info...or simply to persist the > consistent GMT value...and not timezone...or do something else? > > If there are docs/tutorials about the general and/or jpa-specific > issues, please just point me to them. > > Thanks, > > Scott > _______________________________________________ > eclipselink-users mailing list > eclipselink-users@xxxxxxxxxxx > https://dev.eclipse.org/mailman/listinfo/eclipselink-users > > -- View this message in context: http://old.nabble.com/question-about-date-timestamp-tp30192925p30213325.html Sent from the EclipseLink - Users mailing list archive at Nabble.com.
Back to the top