Decided to handle this via the controller because it seems to be the most straightforward method (check if the association exists; if it doesn't, create it; done).
I was thinking there might be a way to do it automatically via a listener in the schema, but the mechanics of such a solution are evading me. I suppose I could also work through it in the Mako templates, but if I eventually decide to use a form library I'll have to address the issue in the controller or schema anyway. So, unless anyone thinks that adding a listener to the schema is the way to go, I'll consider this problem solved. Thanks. On Thursday, January 9, 2014 2:10:32 AM UTC-5, Brian Findlay wrote: > > > How would you recommend tackling this? Should it be addressed in the > controller, the template, or perhaps in the schema (__init__ or a > listener?)? > > -- 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/groups/opt_out.
