Perhaps it would work if we made the restriction that extensions cannot modify existing tables, but may add tables, defining them in a separate model file?
cheers. -chris On May 30, 7:37 am, "Mark Ramm" <[EMAIL PROTECTED]> wrote: > > All of this boils down to the simplest approach: components requiring > > their own database tables/rows/etc should create their own separate > > database schema and database. This also frees the developer of said > > components to use whatever ORM or other database techniques they > > choose. This schema should be configurable, so should the developer > > choose to share the database with the general TG database he can do > > so. > > This is fine when you want super simple things. But take a look at > django contrib for a whole list of things that would be absolutely > impossible if "apps" couldn't change the model. (A simple example, a > comments app, which allows you to add comments to various content.) > > -- > Mark Ramm-Christensen > email: mark at compoundthinking dot com > blog:www.compoundthinking.com/blog --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
