Re: Another database for unit tests

2008-01-20 Thread Russell Keith-Magee
On Jan 20, 2008 2:13 PM, Jim Crossley <[EMAIL PROTECTED]> wrote: > > "James Bennett" <[EMAIL PROTECTED]> writes: > > > On Jan 19, 2008 10:24 PM, Jim Crossley <[EMAIL PROTECTED]> wrote: > >> Yes, I knew I could override the NAME, but I'd like to override the > >> ENGINE,USER,PASSWORD,HOST, and PORT

Re: Another database for unit tests

2008-01-19 Thread Jim Crossley
"James Bennett" <[EMAIL PROTECTED]> writes: > On Jan 19, 2008 10:24 PM, Jim Crossley <[EMAIL PROTECTED]> wrote: >> Yes, I knew I could override the NAME, but I'd like to override the >> ENGINE,USER,PASSWORD,HOST, and PORT, too. Our settings are configured >> for mysql/innodb, to match our produc

Re: Another database for unit tests

2008-01-19 Thread James Bennett
On Jan 19, 2008 10:24 PM, Jim Crossley <[EMAIL PROTECTED]> wrote: > Yes, I knew I could override the NAME, but I'd like to override the > ENGINE,USER,PASSWORD,HOST, and PORT, too. Our settings are configured > for mysql/innodb, to match our production environment. But as our > test suite and ini

Re: Another database for unit tests

2008-01-19 Thread Jim Crossley
Thanks, but... "James Bennett" <[EMAIL PROTECTED]> writes: > On Jan 19, 2008 5:05 PM, Jim Crossley <[EMAIL PROTECTED]> wrote: >> What's the common way of making unit tests use a different database >> than what's in settings.DATABASE_{ENGINE,USER,PASSWORD,HOST,PORT}? > > http://www.djangoproject.

Re: Another database for unit tests

2008-01-19 Thread James Bennett
On Jan 19, 2008 5:05 PM, Jim Crossley <[EMAIL PROTECTED]> wrote: > What's the common way of making unit tests use a different database > than what's in settings.DATABASE_{ENGINE,USER,PASSWORD,HOST,PORT}? http://www.djangoproject.com/documentation/settings/#test-database-name -- "Bureaucrat Con