On Fri, Feb 10, 2012 at 6:19 AM, Daniel Holth <[email protected]> wrote: > I do not understand why I would want to share a declarative_base() between > packages.
One reason is so you can call Base.metadata.create_all() to create all tables, without having to go into each individual package or keep track of what tables they have. (Of course, you'd have to ensure the table names don't overlap, usually by the library defaulting to a prefix that others are unlikely to use.) But as I've said in a few places, I've gone back to 'meta' modules as in Pylons, and that's what I'm putting first in the Pyramid/Pylons guide. So the Sessions and Bases would not be coordinated unless the application writer does it. -- Mike Orr <[email protected]> -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
