oh, right, concrete! abstract concrete can also do the trick?
On 04/15/2015 03:10 PM, Mike Bayer wrote:
On 4/15/15 1:59 PM, Richard Gerd Kuesters wrote:
oops, i forgot to comment out the fk to the parent table and now it
doesn't work: "sqlalchemy.exc.NoForeignKeysError: Can't find any
foreign key relationships between 'container_instance' and
'container_aggregation'."
well, it doesn't need it if it's inherited (both db and software
level), right?
correct, you'd use a "concrete" setup here from a SQLA perspective.
--
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 http://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.