by "plugin" does that mean, "its in the sqlalchemy.ext" package ? why is it important that it be there ? this is more of a distinct utility for a very narrow use case (i.e. when you can just ALTER TABLE and dont need any additional migrating SQL executed) and is not really an extension to SA itself.
On Feb 2, 2007, at 7:32 AM, Paul Johnston wrote: > Hi, > > Well, I just happened to say "model" in my original message. I > could have said "Tool to check whether a bunch of SA tables matches > the database tables". > > That is what model_update.py does (at least, it tries to!) - so is > it something you'd consider including as an SA plugin? > > Paul > > > On 2/1/07, Michael Bayer <[EMAIL PROTECTED]> wrote: > well, just making an app in such a way that all the "model" classes > are attached to a single-datamember called "model" is just one of > an infinite number of ways to do MVC. so your app is sort of part > of a larger framework (whether that framework explcitly exists or > not). > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" 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/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
