On Mon, 4 Mar 2019, Jonathan Vanasco wrote:
We "define" the model in a separate package - all the classes and
relationships are in there. There are database support items as well, and
some of the advanced/business logic that manipulate the ORM objects. By
advanced-database-specific logic, an
We "define" the model in a separate package - all the classes and
relationships are in there. There are database support items as well, and
some of the advanced/business logic that manipulate the ORM objects. By
advanced-database-specific logic, an example might be: resetting a password
is a
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
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.
This allows other apps and utilities to be built off the SqlAlchemy models
