Re: [sqlite] SQLite iOS timestamp type mapping settings must be set to float to get correct data

2018-11-27 Thread Scott Perry
On Nov 26, 2018, at 14:16, Simon Slavin wrote: > > On 26 Nov 2018, at 9:09pm, Scott Perry wrote: > >> For Bill's purposes—investigating a copied, non-corrupt database—it would >> probably be easiest to just convert from the Cocoa epoch to the Unix epoch >> by updating all the columns that

Re: [sqlite] SQLite iOS timestamp type mapping settings must be set to float to get correct data

2018-11-26 Thread Simon Slavin
On 26 Nov 2018, at 9:09pm, Scott Perry wrote: > For Bill's purposes—investigating a copied, non-corrupt database—it would > probably be easiest to just convert from the Cocoa epoch to the Unix epoch by > updating all the columns that currently store Cocoa timestamps. Something > like: > >

Re: [sqlite] SQLite iOS timestamp type mapping settings must be set to float to get correct data

2018-11-26 Thread Scott Perry
On Nov 20, 2018, at 12:41 PM, Jens Alfke wrote: > On Nov 20, 2018, at 11:44 AM, Bill Hashman > wrote: > >> The timestamp from iOS systems is not compliant with ISO 8601/Unix or other >> common timestamps. It appears apple has their start date offset 31 years. > > Yes, the ‘epoch’ in

Re: [sqlite] SQLite iOS timestamp type mapping settings must be set to float to get correct data

2018-11-20 Thread Guy Harris
On Nov 20, 2018, at 12:41 PM, Jens Alfke wrote: > On Nov 20, 2018, at 11:44 AM, Bill Hashman > wrote: > >> The timestamp from iOS systems is not compliant with ISO 8601/Unix or other >> common timestamps. It appears apple has their start date offset 31 years. > > Yes, the ‘epoch’ in

Re: [sqlite] SQLite iOS timestamp type mapping settings must be set to float to get correct data

2018-11-20 Thread Petite Abeille
> On Nov 20, 2018, at 21:49, Thomas Kurz wrote: > >> (Does SQL itself have a numeric timestamp type, or explicitly endorse the >> POSIX epoch for numeric timestamps?) > > SQL has an explicit TIMESTAMP type since SQL-92, one thing that I'm heavily > missing in SQlite ;-) DATE '1998-12-25’ &

Re: [sqlite] SQLite iOS timestamp type mapping settings must be set to float to get correct data

2018-11-20 Thread Thomas Kurz
> (Does SQL itself have a numeric timestamp type, or explicitly endorse the > POSIX epoch for numeric timestamps?) SQL has an explicit TIMESTAMP type since SQL-92, one thing that I'm heavily missing in SQlite ;-) ___ sqlite-users mailing list

Re: [sqlite] SQLite iOS timestamp type mapping settings must be set to float to get correct data

2018-11-20 Thread Jens Alfke
> On Nov 20, 2018, at 11:44 AM, Bill Hashman > wrote: > > The timestamp from iOS systems is not compliant with ISO 8601/Unix or other > common timestamps. It appears apple has their start date offset 31 years. Yes, the ‘epoch’ in Apple’s own APIs (CoreFoundation, Foundation) is 1/1/2001,

Re: [sqlite] SQLite iOS timestamp type mapping settings must be set to float to get correct data

2018-11-20 Thread David Raymond
Tuesday, November 20, 2018 2:45 PM To: sqlite-users@mailinglists.sqlite.org Subject: [sqlite] SQLite iOS timestamp type mapping settings must be set to float to get correct data Hello to all, I was delving into a SQLite db3 that is a backup from a iOS application when I came across a timestamp t

[sqlite] SQLite iOS timestamp type mapping settings must be set to float to get correct data

2018-11-20 Thread Bill Hashman
Hello to all, I was delving into a SQLite db3 that is a backup from a iOS application when I came across a timestamp translation challenge. The timestamp from iOS systems is not compliant with ISO 8601/Unix or other common timestamps. It appears apple has their start date offset 31 years.