On 8 Feb 2020, at 3:10pm, Andy KU7T <k...@ku7t.org> wrote: > I'm looking for best practices on when and where to create/initialize your > tables when using SqlLite.Net as well as how to properly handle schema > changes from one version to another.
I urge you not to use CreateTable, but instead to use SQL commands to make and convert tables. That way anyone who knows SQL will understand what you're doing, and you can more easily transfer your code to something other than .net. In terms of version control, SQLite has space to store a version number which is ideal for that: <https://sqlite.org/pragma.html#pragma_user_version> You can store whatever integer you like in there and recall it whenever you want. Put a 1 in there for the first version of your program. If you ever need to make schema changes, start using it to keep track of your schema versions. If you would prefer not to use a SQLite-only facility, you might create a configuration table, with key and value rows, and have a row of that table indicate your schema version. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
