testing and documentation (plus two minor bug fixes) are checked into
the schema-evolution branch:
tests/modeltests/schema_evolution/models.py
docs/schema-evolution.txt
> because I suspect the existing test framework will require some
> modifications to enable models to be evolved during a test run.
yeah, i spent some time trying to figure out how i could load a model,
change it, then run the evolve introspection scripts. but in the end, i
just wrote sql to simulate what the model used to look like. i figured
low-impact==good. (but i'm open to different ideas)
derek
Russell Keith-Magee wrote:
> On 7/20/07, Derek Anderson <[EMAIL PROTECTED]> wrote:
>> but i use django
>> quite a bit now and am surprised some sort of this hasn't been merged
>> yet, so i figured i'd bring it up to date and re-release.
>
> By casting a quick eye over the patch, I caught at least two reasons
> that this hasn't been merged (or taken particularly seriously by the
> core developers):
>
> - No tests.
> - No documentation.
>
> I agree that schema evolution would be a valuable addition to Django.
> However, if you (or anyone else) is serious about getting this into
> trunk, adding a comprehensive test suite and draft documentation is a
> non-negotiable prerequisite for .
>
> The testing requirement is especially relevant for schema-evolution
> because I suspect the existing test framework will require some
> modifications to enable models to be evolved during a test run. If you
> want to prove to me that you are serious, show me the tests.
>
> 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 [email protected]
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
-~----------~----~----~----~------~----~------~--~---
