Hi Russ, thanks, that's what I'm using currently. Not optimal but I guess it'll have to do.
On Jun 26, 12:42 am, "Russell Keith-Magee" <[EMAIL PROTECTED]> wrote: > On Wed, Jun 25, 2008 at 11:54 PM, [EMAIL PROTECTED] > > <[EMAIL PROTECTED]> wrote: > > > Hi everyone, > > > I'm working on a project that has a very solid database design but > > many of the used features aren't supported by Django (for example, > > multiple column primary keys). > > > The project has a complete database creation script but I haven't > > found a way to use it to create the test database which I really want > > to, given the ability to use Django's testing framework. Is there a > > way to enable creation of the test database not by the declared models > > by with a SQL script? > > Not really. You can control the name of the test database that Django > uses, but Django creates and destroys the database on each test run, > so anything you put into a test database will be lost as soon as you > run the test suite. > > You might be able to mock something up using custom SQL statements > [1], but it will depend on exactly what you want to achieve. > > [1]http://www.djangoproject.com/documentation/model-api/#providing-initi... > > 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 -~----------~----~----~----~------~----~------~--~---
