On Mon, 26 Mar 2018, Jonathan Vanasco wrote:
Pay close attention to which database functions you use, and how you use
datetime fields. Those are two things were SQLite tends to differ from the
other common databases.
You can handle any of those differences using dialect specific custom
On Monday, March 26, 2018 at 9:41:00 AM UTC-4, Rich wrote:
>
>
>I'm working now on the single-user, SQLite3 version and will return to
> this issue when that's functioning.
Pay close attention to which database functions you use, and how you use
datetime fields. Those are two things were
On Mon, 26 Mar 2018, Mike Bayer wrote:
this is a very open-ended question that can't be answered with a single
document. SQLAlchemy will allow for standard SQL and DDL to work across
both platforms transparently as well as differences in INSERT mechanics,
and additionally transactional
this is a very open-ended question that can't be answered with a
single document. SQLAlchemy will allow for standard SQL and DDL to
work across both platforms transparently as well as differences in
INSERT mechanics, and additionally transactional semantics will work.
But beyond that you would
I'm starting to write an application which will have two versions. One is
single-user with sqlite3 as the backend, the other is multi-user with
postgres as the backend. The single-user version will be written first.
Both will be placed on github as F/OSS applications.
Please point me to
