I use Convert.ToInt32 (or whatever else is appropriate) instead of direct casts when reading from System.Data.SQLite... I use a very similar schema in an SQLServer and SQLite database, and Convert seems to handle many of the differences without requiring different code for each database engine.
On Mon, 28 Jan 2019 at 03:31, Joe Mistachkin <sql...@mistachkin.com> wrote: > > JP wrote: > > > > The answers don't explain why there is a bitness difference at run-time > > between the types retrieved from INT and INTEGER columns, and that's my > > question. From reading https://sqlite.org/datatype3.html I understand > > there should be no difference whatsoever between defining a column INT > > or INTEGER (other than whether a primary key may become a rowid alias). > > > > System.Data.SQLite maps type names to their associated types. Mappings > can be overridden on a per-connection basis. By default, INT maps to a > 32-bit integer and INTEGER maps to a 64-bit integer, mostly for reasons > of backward compatibility. > > In order to customize the mappings, the flag UseConnectionTypes should > be used when opening the connection -AND- the AddTypeMapping method is > used to override a built-in mapping of the same name (e.g. "INT"). > > -- > Joe Mistachkin > > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
