The tables don't exist yet. The Base.metadata.create_all(engine) is to
create them.
Thanks!
On May 30, 11:52 pm, Michael Bayer mike...@zzzcomputing.com wrote:
This might be because the tables you're trying to reference are themselves
not InnoDB. Try running DESCRIBE on the referenced tables
Perhaps it's relevant (though I suspect not) that the class Avalanche
actually contains:
class Avalanche(Base):
events = relationship(Event,
secondary=Avalanche_Event_Association)
This is what prevents us from writing the classes in the following
order in the database definition .py
create_all() only can determine the order of tables if you use ForeignKey and
ForeignKeyConstraint objects correctly on the source Table objects and/or
declarative classes.
See http://docs.sqlalchemy.org/en/rel_0_7/orm/relationships.html#many-to-many
and
Thanks! I don't quite follow the statement about fully mapped
association table being unusual. The first Many-to-Many example you
linked was the structure I copied when making my own tables here. Have
I deviated from it in some way? Or should the example on the site have
viewonly=True, if being
On May 31, 2012, at 3:49 PM, Jeff wrote:
Thanks! I don't quite follow the statement about fully mapped
association table being unusual.
your name Avalanche_Event_Association with CamelCase made me think it was
mapped class, but this is not the case as you have it as a Table.
the problem
Well, one of the worst things that can happen in programming has
happened: It now works, and I don't know why _ I didn't change
anything that I know of, and I definitely didn't change the
capitalization. Guess I'll just slowly back away from the machine and
hope everything stays that way.
Thanks
