System.Data.SQLite

Login
This project makes use of Eagle, provided by Mistachkin Systems.
Eagle: Secure Software Automation
2013-01-01
19:32 Closed ticket [bb4b04d457]: Using DateTimeFormat=Ticks with TIMESTAMP column causes exception plus 3 other changes artifact: e3631f103c user: mistachkin
2012-12-29
21:37
In the test suite, avoid leaking memory used for data/temp_store_directory. Fix missing description in test [bb4b04d457]. check-in: 99a46a4feb user: mistachkin tags: trunk
2011-11-30
00:36 Fixed ticket [bb4b04d457]: Using DateTimeFormat=Ticks with TIMESTAMP column causes exception plus 3 other changes artifact: d7cdd753c4 user: mistachkin
00:34
Recognize the TIMESTAMP column data type as a DateTime object. Fix for ticket [bb4b04d457]. check-in: e96f0d17a5 user: mistachkin tags: trunk
2011-11-29
22:33 Ticket [bb4b04d457] Using DateTimeFormat=Ticks with TIMESTAMP column causes exception status still Open with 6 other changes artifact: 3524b6fee3 user: mistachkin
20:27 New ticket [bb4b04d457]. artifact: 5a49e7b276 user: anonymous

Ticket Hash: bb4b04d4578f017ea01ef094a2177687566f7bba
Title: Using DateTimeFormat=Ticks with TIMESTAMP column causes exception
Status: Closed Type: Feature_Request
Severity: Important Priority: Medium
Subsystem: Db_Type_Conversion Resolution: Fixed
Last Modified: 2013-01-01 19:32:26
Version Found In: 1.0.76,1.0.77
Description:
I have database with table like this CREATE TABLE Times (Time TIMESTAMP NOT NULL) In connection string I have the option datetimeformat=Ticks When reading field Times with SQLiteDataReader and trying to convert it in into DateTime type, exception "Invalid typecast" is thrown because returned value has "long" type. In version 1.0.74 and earlier the type was correct - DateTime. If I'll change declaration of field in database to DATETIME, then all go OK.

Example code http://pastebin.com/aQjUe1tV When linked to 1.0.74 it shows the correct date, but when linked to 1.0.76+, program closes with exception


mistachkin added on 2011-11-29 22:33:31 UTC:
For now, the best workaround is to use the DATETIME column type instead of TIMESTAMP?


mistachkin added on 2011-11-30 00:36:19 UTC:
Fixed by check-in [e96f0d17a5] on trunk.