Ok my bad, after reading more I've realized that I don't need to specify remote for custom relationships between 2 distinct classes, using primaryjoin() should be enough...
Il giorno lunedì 28 agosto 2017 17:27:41 UTC+2, Martino Io ha scritto: > > I'm trying to add a simple relationship into 2 different ORM classes which > are not bound by DB foreign keys. > > The linked example > http://docs.sqlalchemy.org/en/latest/orm/join_conditions.html#creating-custom-foreign-conditions > > provides a self referential class which passes the column attribute to > remote() however in a more real-world scenario I think it's most likely > that you'll be referencing 2 distinct classes, and since the second class > isn't created yet i cannot pass a column reference to remote() and neither > use a string reference like "second_class.column"... any suggestions? > > -- > Marcin > > -- 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.
