Russ - We had a few back and forths about this several weeks ago, if
you recall. I now am much better versed in Django and so maybe a bit
more capable of making intelligent comments.
It would seem to me that with the primitives that I am seeking (which
is basically a continuation of hiding the SQL specifics of each DMBS
using Python code) all kinds of migration capabilities can easily be
implemented. In fact, I can see several options, all valid, that each
developer can choose for their project. That way Django would not
have to decide in advance how to do migrations. Some may prefer
whole frameworks and specific methodologies, others will prefer to
roll their own. For all intents and purposes, many of these
primitives already exist, at least for the initial creation of tables
from model class definitions, why not extend it to the next level and
provide the same toosl for Django developers to create tables and
modify them? Seems like a natural to me. I would write it myself,
but I am too rusty with SQL and the different syntaxes across
databases to be able to really dive in at this point. But I would
enjoy collaborating on design and proposed implementation with anyone
who was willing and capable of tackling this task.
Jack
On May 5, 9:34 pm, "Russell Keith-Magee" <[EMAIL PROTECTED]>
wrote:
> On Tue, May 6, 2008 at 11:57 AM, jack <[EMAIL PROTECTED]> wrote:
>
> > Are there any Python/Django methods that represent generic database
> > commands such as creating a new table, renaming or dropping a column,
> > etc.? My thinking is that if these generic methods existed, so that
> > all I needed to do was specifiy the correct info abt my DBMS in the
> > Settings file, I could create my own migrations as custom Views. I
> > could invoke these via the web as well after having copied my latest
> > code to my production server.
>
> There isn't anything built into Python or Django, but there are a few
> projects running externally to Django that implement this sort of
> feature.
>
> Personally, I would recommend Django Evolution [1] - but then, I'm one
> of the developers of that project. If you search the django-users and
> django-developers archives for "schema evolution", you will find
> references to a few other projects.
>
> [1]http://code.google.com/p/django-evolution
>
> Yours,
> Russ Magee %-)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---
