In relationship(), foreign_keys refers to the field in the source table,
not the destination.
--
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
Using or_ function
https://paste.ofcode.org/zd7aqqwR4V4rpYjfpmCHQg
On Friday, August 24, 2018 at 2:26:21 AM UTC+4:30, Mike Bayer wrote:
>
> is there a stack trace (just the beginning and then a bit of the
> repeating part, not the whole thing), there's no recursion inherent in
> the SQLAlchemy
It's riding me crazy
here is a MVCE
https://paste.ofcode.org/7evqFGabM3Ls8qXiNnTGSy
On Friday, August 24, 2018 at 2:26:21 AM UTC+4:30, Mike Bayer wrote:
>
> is there a stack trace (just the beginning and then a bit of the
> repeating part, not the whole thing), there's no recursion inherent in
Stacktrace with codes =>
https://paste.ofcode.org/N4L9vHq6KqiupFRxBDTedZ
Its riding me crazy
On Friday, August 24, 2018 at 2:26:21 AM UTC+4:30, Mike Bayer wrote:
>
> is there a stack trace (just the beginning and then a bit of the
> repeating part, not the whole thing), there's no recursion
> if you want individual migration sections for each schema, with or
> without "schema" written in, there's ways to do all that also but that
> doesn't seem necessary if you are sharing a single model with multiple
> identical schemas.
>
The problem is that some one might alter some tables
