Thanks for the pointer to the Generic Associations page, somehow I managed to miss that. I had the same qualms about referential integrity as the generic foreign description, but was hoping I was missing something.
Doing separate association tables isn't really a big problem, just a bit of a pain that I have a slightly weird setup. Each project shares a master database but has its own identical project database (which can relate to the master), so everything added to the project-side structure I have to arrange to create in a slowly expanding number of project databases. Someday I should look at arranging to collapse the project tables into single copies with project discriminators, but there's never time... :) -- 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.
