> I am able to recreate the exception here. The value of Int64.MaxValue is
> 9223372036854775807. The UnixEpoch values are measured in seconds from
> the epoch 1970-01-01 00:00:00Z. Adding 9223372036854775807 seconds to the
> UnixEpoch would result in a DateTime far beyond the allowed maximum va
mailinglists.sqlite.org
[mailto:sqlite-users-boun...@mailinglists.sqlite.org] On Behalf Of Joe
Mistachkin
Sent: 28 April 2016 19:54
To: 'SQLite mailing list'
Subject: Re: [sqlite] [System.Data.SQLite] int overflow in date handling when
unixepoch is used
Jann Roder wrote:
>
> I jus
Jann Roder wrote:
>
> I just tested the new version that should have the fix for this and now
> I get an ArgumentOutOfRangeException exception when I actually have a
> value of Int64.MaxValue in a date column. Stack trace:
>
I am able to recreate the exception here. The value of Int64.MaxValue
To: 'SQLite mailing list'
Subject: Re: [sqlite] [System.Data.SQLite] int overflow in date handling when
unixepoch is used
Jann Roder wrote:
>
> When I set the dateformat to unixepoch the maximum date I can get back
> from a query is 2038-01-19. This appears to be a problem
Hi,
When I set the dateformat to unixepoch the maximum date I can get back from a
query is 2038-01-19. This appears to be a problem in the wrapper as SQLite
itself is using 64bit integers for dates.
You can reproduce the problem like this:
[Test]
public void ShouldDoSparseTimeSeriesTransform2()
Jann Roder wrote:
>
> When I set the dateformat to unixepoch the maximum date I can get back
> from a query is 2038-01-19. This appears to be a problem in the wrapper
> as SQLite itself is using 64bit integers for dates.
>
Thanks for the clear and concise report. This issue should now be fixed
6 matches
Mail list logo
