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 SQLite tends to differ from the other common databases. You can handle any of those differences using dialect specific custom compilers in SqlAlchemy (http://docs.sqlalchemy.org/en/latest/core/compiler.html) There's no need to do anything now, but it's helpful to know what is likely to break when switching the model's datastore to postgresql. -- SQLAlchemy - The Python SQL Toolkit and Object Relational Mapper http://www.sqlalchemy.org/ To post example code, please provide an MCVE: Minimal, Complete, and Verifiable Example. See http://stackoverflow.com/help/mcve for a full description. --- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
