I tried a test, and apparently, the ms are saved in a DATETIME-type property after setting the DATETIMEFORMAT as suggested. So I guess that means it's not Unix Epoch format. Maybe it's "ms since..." stored as a 64-bit integer?
On Friday, March 18, 2016 at 11:27:57 AM UTC-5, Eric24 wrote: > > Luca-- > After making this change, does OrientDB actually save the ms? I was under > the impression that datetimes were stored internally as LONGs using the > standard Unix Epoch format (seconds since...). > --Eric > > On Thursday, December 19, 2013 at 8:28:16 AM UTC-6, Lvc@ wrote: >> >> You can use also: >> >> alter database DATETIMEFORMAT yyyy-MM-dd HH:mm:ss:SSS >> >> And the same with DATEFORMAT. >> >> Lvc@ >> >> >> -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
