-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tue, 19 May 2015, Mike Bayer wrote:
Examples: date and time functions are entirely different on both
platforms, schema migration operations e.g. ALTER are generally not
supported on SQLite, SQLite has very different behavior regarding foreign
key constraints (in that they do nothing unless special directives are
emitted per-connection), ...
Mike,
I wondered about this. It's a scientific application with many date and
time columns in tables and relies on foreign keys extensively to associate
rows in a details table with a specific row in a header table.
A good amount of starting detail is available in the documentation for both
backends:
http://docs.sqlalchemy.org/en/rel_1_0/dialects/sqlite.html
http://docs.sqlalchemy.org/en/rel_1_0/dialects/postgresql.html
Because I'm starting to learn sqlalchemy I'll begin with the sqlite3
version. I should be able to have sqlalchemy generate the tables from the
declarative base .py file so I don't need to create it in advance with
sqlite. The docs mentions that the sqlite version built into python is used.
I presume that I can specify a newer version that's available since the
resultin .db will be packaged with the rest of the application.
Thanks very much,
Rich
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iD8DBQFVW8ypugEIjC001L0RAuPFAJ9ZbhU6S7p5QLsDeQKnJ7mSWr61QACglHhB
XnZZ2otJI7RhxbDohcWPnyM=
=/nLQ
-----END PGP SIGNATURE-----
