On Sun, 3 Mar 2019, Jonathan Vanasco wrote:
I generally write the SqlAlchemy models as a separate package, then import
that into my MVC/etc patterned app.
In terms of the SqlAlchemy logic, some of that I keep in the models
package, others are in the core app.
...
So my general advice is to approach things with two packages, one for [M]
and the other for [VC]
Jonathan,
I see three different approaches in the above: 1) a separate SA package; 2)
some SA in the model, some in the application class; and 3) a model module
and a combined view/controller module. Please help me distinguish among
them.
Regards,
Rich
--
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 sqlalchemy+unsubscr...@googlegroups.com.
To post to this group, send email to sqlalchemy@googlegroups.com.
Visit this group at https://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.
