Kind of a similar approach. In both cases I think there is merit in keeping the site-structure code separate from the data-access code. In my app, the sqlalchemy classes are also used by another application, so I don't want to load them up with stuff that is specific to the website. And composition over inheritance, right?
-- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-devel@googlegroups.com. To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en.
