Re: [sqlalchemy] is ForeignKey() the only ORM feature (outside of table setup) that requires table knowledge

On Oct 23, 2013, at 4:33 PM, Jonathan Vanasco jonat...@findmeon.com wrote: this has just confused me for a while , and constantly trips me up... class FirstTable() __tablename__ = 'first_table' id = Column(Integer, primary_key=True) class SecondTable()

Re: [sqlalchemy] is ForeignKey() the only ORM feature (outside of table setup) that requires table knowledge

Thanks for the history lesson! A large part of me things that both strings or objects should be accepted , this way there would be parity across the board. Because yes, it is confusing! But a larger part of me worries about backwards compatibility and collisions. ForeignKey(mytable.id)

[sqlalchemy] is ForeignKey() the only ORM feature (outside of table setup) that requires table knowledge

this has just confused me for a while , and constantly trips me up... class FirstTable() __tablename__ = 'first_table' id = Column(Integer, primary_key=True) class SecondTable() __tablename__ = 'second_table' id = Column(sa.Integer, primary_key=True)