Hi,

"Since version 1.2.x (when the page store is enabled), the database stores
date/time as "local time" (the number of milliseconds since 1970-01-01 in
the local timezone). That should make a database file portable to different
time zones."

This is about the internal storage format. It has nothing to do with the
ability to convert between bigint and timestamp.

Regards,
Thomas




On Tue, Dec 24, 2013 at 11:02 AM, bruce buchanan <[email protected]
> wrote:

> well there was this:
>
> Hi,
>
> Since version 1.2.x (when the page store is enabled), the database
>
> stores date/time as "local time" (the number of milliseconds since
>
> 1970-01-01 in the local timezone). That should make a database file
>
> portable to different time zones. In previous versions, date/time was
>
> stored as UTC, which was a problem because it would change dates when
>
> moving the database file to a system with a different time zone.
>
>
> See also Data.writeValue(), cases Value.TIME / DATE / TIMESTAMP.
>
>
> Regards,
>
> Thomas
>
> and this:
>
> select convert(parseDateTime(DOB,'yyyy/MM/dd hh:mm:ss'),timestamp)
>
>  as NEWNAME
>
> from CSVREAD
>
>
> fragments of related conversations, which, combined, inspired me to ask
> such a question. but, let's face it, I'm clueless, never mind how I got
> here.
>
> so, let me ask: what do I do when I have all my dates/times in unix millis
> and I want to treat/parse them as dates, datetimes, etc? ie I want to do
> date parts, date comparisons etc... btw I have no issues regarding time
> zones, I just want to turn my unix millis into something like a date object
>
> thanks
> //
>
>
> On Tuesday, December 24, 2013 1:07:57 AM UTC-8, Thomas Mueller wrote:
>
>> Hi,
>>
>> No. What makes you believe it should?
>>
>> Regards,
>> Thomas
>>
>>
>> On Mon, Dec 23, 2013 at 11:46 PM, bruce buchanan 
>> <[email protected]>wrote:
>>
>>> should this work? (big number is a valid unix millis value that cashes
>>> out to  Mon, 11 Nov 2013 13:35:29 GMT)
>>>
>>> SELECT  CONVERT(1384176929520, TIMESTAMP);
>>> SELECT CAST(1384176929520 AS TIMESTAMP);
>>>
>>> both give me
>>>
>>> Cannot parse "TIMESTAMP" constant "1384176929520";
>>>
>>> thanks
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "H2 Database" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to [email protected].
>>> To post to this group, send email to [email protected].
>>>
>>> Visit this group at http://groups.google.com/group/h2-database.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>
>>  --
> You received this message because you are subscribed to the Google Groups
> "H2 Database" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/h2-database.
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
You received this message because you are subscribed to the Google Groups "H2 
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to