On Jan 3, 2012, at 2:32 PM, Mike Orr wrote: > > Reflection is more difficult because you can't map classes to tables > until they've been reflected, and I'm not sure how it affects > declarative syntax.
I've recently worked out a way to do this: http://www.sqlalchemy.org/trac/wiki/UsageRecipes/DeclarativeReflectedBase and in 0.7.5 or #2356, it will be slightly easier still: http://www.sqlalchemy.org/trac/ticket/2356 > So some of the global code you have to put in an > init function, at minimum the table definitions and mapper calls, and > at maximum the entire declarative classes. Again the Akhet manual > discusses this. but yes the reflected approach still needs some point at which you say, "reflect and map !" even if declarative is used. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to pylons-discuss@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
