On 9 December 2010 23:03, Greg Keogh <[email protected]> wrote: > Does not work and creates some sort of numeric column that does not > increment and has 1 in all rows. You have to specify [INTEGER] as the column > type. [int] and [INTEGER] are not the same.
http://sqlite.org/lang_createtable.html#rowid > Now I’m having trouble with SQLite DATETIME columns. A LINQ Select is > crashing with DateTime parse error and I can’t find where. One datetime > column I can read okay, the other crashes when I access it. The latter is > nullable, but it has valid non-null data in all rows. So nullable datetime > fields are un-parseable?! As Davy said - everything in SQLite is stored as a string. Each column then has an affinity set to a type, TEXT NUMERIC INTEGER REAL NONE Maybe the nullable DateTime has a different affinity set, one that EF4/SQLite.NET isn't parsing properly? SQLite Browser should be able to tell you the affinity set to a particular field. http://sourceforge.net/projects/sqlitebrowser/
