> I am working on http://code.djangoproject.com/ticket/6148.
> This includes a new option "db_schema" that's been added to a models
> meta class.
> It involves using a custom schema for any model that has this
> attribute set.
> The problem comes when testing.
> In postgres a test database is created and inside that one this or
> these new schemas are created. Works fine when creating and dropping
> the test database.
> In mysql schemas are treated as ordinary databases. So a test database
> gets created. I can even create the "databases" that correspond to
> db_schema but these will be the same as when running "live". Not
> created INSIDE the test database but in parallel to the test database
> and with the same name as when running normally.

> What I want to do is to alter/patch the value in db_schema with
> something when create_test_db is used but not else.
> This db_schema attribute has to be set at the time contribute_to_class
> method of django.db.models.Options is called or before because it is
> used there.

> Any hints or ideas are most welcome...

> On Fri, Aug 22, 2008 at 12:39 AM, crippledcanary
> <crippledcan...@gmail.com> wrote:

>> I am working on http://code.djangoproject.com/ticket/6148.
>> This includes a new option "db_schema" that's been added to a models
>> meta class.
>> It involves using a custom schema for any model that has this
>> attribute set.
>> The problem comes when testing.
>> In postgres a test database is created and inside that one this or
>> these new schemas are created. Works fine when creating and dropping
>> the test database.
>> In mysql schemas are treated as ordinary databases. So a test database
>> gets created. I can even create the "databases" that correspond to
>> db_schema but these will be the same as when running "live". Not
>> created INSIDE the test database but in parallel to the test database
>> and with the same name as when running normally.

>> What I want to do is to alter/patch the value in db_schema with
>> something when create_test_db is used but not else.
>> This db_schema attribute has to be set at the time contribute_to_class
>> method of django.db.models.Options is called or before because it is
>> used there.

>> Any hints or ideas are most welcome...

> My hint would be wait. We are currently in the crunch right before our
> v1.0 release. Developer attention is currently focussed on  fixing
> existing bugs and getting v1.0 out the door; I can't speak for the
> other developers, but at the moment, I simply don't have the spare
> cycles to dedicate to guiding a new feature.

> This doesn't mean the feature isn't worthwhile - it just means we have
> slightly different priorities at the moment. If you wait about a month
> (2 weeks to the release, and a few extra weeks to let us recover from
> the hangover), you'll get a lot more attention for your design issues.

> Yours,
> Russ Magee %-)