On 9/16/06, James Bennett <[EMAIL PROTECTED]> wrote: > > On 9/15/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > > In general, initial SQL data is a real pain to manage and if anybody has > > a good idea on a better approach. I would like to avoid building a full > > SQL parser in Python for obvious reasons. > > Other people already *have* built SQL parsers in Python, with all the > quirks of specific databases, so... why not either > ...
Here's a third option: Introduce the use of fixtures, which allow other ways to put initial data into the database. The test system requires the ability to install (and remove) data into the database to act as test fixtures. Obviously, SQL isn't the ideal format for this, beacuse of differences between databases. However, we now have a deserialization framework which provides for JSON, XML and Python deserializers. My intention is to provide for an 'install fixture' api, with an entry point in django-admin, where the initial data can come from any of these deserializable formats. The 'initial SQL' feature is needed to support DB specific initialization that Django doesn't handle (minor table alterations, for example), so I would expect that this will continue to be available, just cease to be an attractive mechanism for initial data. I'm still working on some of the details, but I should have some specific proposals soon (or at least, as soon as I get a few moments to scratch myself). Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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-developers -~----------~----~----~----~------~----~------~--~---
