Re: [sqlalchemy] Re: Relationship to child with 2 foreginKey from same Parent column
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 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.
Re: [sqlalchemy] Re: Relationship to child with 2 foreginKey from same Parent column
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 part of this so something must be up with your model.
> an MCVE (see the link below) is always the best way to show what's
> happening.
>
> On Thu, Aug 23, 2018 at 4:57 PM, Alireza Ayin Mehr
> > wrote:
> > Well, I tried "or_()" before
> > primaryjoin="or_(User.id == Conversation.user1, User.id ==
> > Conversation.user2)"
> > It returns RecursionError :(
> >
> > On Thursday, August 23, 2018 at 9:00:58 PM UTC+4:30, Jonathan Vanasco
> wrote:
> >>
> >> I believe something like this should work.
> >>
> >>
> >> conversations = sqlalchemy.orm.relationship("Conversation",
> >>
> >> primaryjoin="""or_(User.id==Conversation.user_id_1,
> >>
> >> User.id==Conversation.user_id_2,
> >>
> )""",
> >>
> >> order_by="Conversation.id.desc()",
> >> )
> >>
> >>
> >> i also think you'll need to make an explicit relationship for a user1
> and
> >> user2 relationship instead of using back_populates. i could be wrong.
> >> personally i would make separate relationships though, because having
> an
> >> undordered list for them makes little sense.
> >>
> > --
> > 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+...@googlegroups.com .
> > To post to this group, send email to sqlal...@googlegroups.com
> .
> > Visit this group at https://groups.google.com/group/sqlalchemy.
> > For more options, visit https://groups.google.com/d/optout.
>
--
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.
Re: [sqlalchemy] Re: Relationship to child with 2 foreginKey from same Parent column
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
> the SQLAlchemy part of this so something must be up with your model.
> an MCVE (see the link below) is always the best way to show what's
> happening.
>
> On Thu, Aug 23, 2018 at 4:57 PM, Alireza Ayin Mehr
> > wrote:
> > Well, I tried "or_()" before
> > primaryjoin="or_(User.id == Conversation.user1, User.id ==
> > Conversation.user2)"
> > It returns RecursionError :(
> >
> > On Thursday, August 23, 2018 at 9:00:58 PM UTC+4:30, Jonathan Vanasco
> wrote:
> >>
> >> I believe something like this should work.
> >>
> >>
> >> conversations = sqlalchemy.orm.relationship("Conversation",
> >>
> >> primaryjoin="""or_(User.id==Conversation.user_id_1,
> >>
> >> User.id==Conversation.user_id_2,
> >>
> )""",
> >>
> >> order_by="Conversation.id.desc()",
> >> )
> >>
> >>
> >> i also think you'll need to make an explicit relationship for a user1
> and
> >> user2 relationship instead of using back_populates. i could be wrong.
> >> personally i would make separate relationships though, because having
> an
> >> undordered list for them makes little sense.
> >>
> > --
> > 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+...@googlegroups.com .
> > To post to this group, send email to sqlal...@googlegroups.com
> .
> > Visit this group at https://groups.google.com/group/sqlalchemy.
> > For more options, visit https://groups.google.com/d/optout.
>
--
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.
Re: [sqlalchemy] Re: Relationship to child with 2 foreginKey from same Parent column
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 inherent in
> the SQLAlchemy part of this so something must be up with your model.
> an MCVE (see the link below) is always the best way to show what's
> happening.
>
> On Thu, Aug 23, 2018 at 4:57 PM, Alireza Ayin Mehr
> > wrote:
> > Well, I tried "or_()" before
> > primaryjoin="or_(User.id == Conversation.user1, User.id ==
> > Conversation.user2)"
> > It returns RecursionError :(
> >
> > On Thursday, August 23, 2018 at 9:00:58 PM UTC+4:30, Jonathan Vanasco
> wrote:
> >>
> >> I believe something like this should work.
> >>
> >>
> >> conversations = sqlalchemy.orm.relationship("Conversation",
> >>
> >> primaryjoin="""or_(User.id==Conversation.user_id_1,
> >>
> >> User.id==Conversation.user_id_2,
> >>
> )""",
> >>
> >> order_by="Conversation.id.desc()",
> >> )
> >>
> >>
> >> i also think you'll need to make an explicit relationship for a user1
> and
> >> user2 relationship instead of using back_populates. i could be wrong.
> >> personally i would make separate relationships though, because having
> an
> >> undordered list for them makes little sense.
> >>
> > --
> > 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+...@googlegroups.com .
> > To post to this group, send email to sqlal...@googlegroups.com
> .
> > Visit this group at https://groups.google.com/group/sqlalchemy.
> > For more options, visit https://groups.google.com/d/optout.
>
--
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.
Re: [sqlalchemy] Alembic and postgresql multiple schema question
> 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 at some schemas with plain sql in psql (( So it would be perfect to have individual migration sections for each schema, _with_ "schema" written in. Thank you -- 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.
