I'm working with a MySQL setup that has, say, a Studio database (or
schema), and multiple Production schemas (Production_1, Production_2, etc).
The Studio database has a seasons table, and the Production databases
have episodes tables. Currently, the episodes table doesn't have a
foreign key
On May 24, 2013, at 11:53 AM, YKdvd davidobe...@gmail.com wrote:
class Production(Base):
__table_args__ = {'schema':'Studio'}
id = Column('id', Integer, primary_key=True, nullable=False)
class Episode(Base):
...
# some sort of relationship() back to Production, even
On May 24, 2013, at 12:34 PM, YKdvd davidobe...@gmail.com wrote:
Yeah, I was afraid of that, but I thought there might be something going on
with the relationship layer that might do the knitting. It would be a
constant value (per schema/engine) I could have provided to the engine,
Yup, all episodes in a Production schema would belong to one specific
production row. I guess I was thinking about the relationship more in
terms of the automatic loading of the collection, and being able to
add/delete from it and have it reflected on flush. It looks like @property
Am 24.05.2013, 17:53 Uhr, schrieb YKdvd davidobe...@gmail.com:
but I can't seem to find anything that works. I can provide some sort of
instance method or property with the necessary id value for foreign(),
but
I'm not sure if this is acceptable, or even if the remote reference is
correct
