[PATCH]: default settings for unit tests

[Waldemar Kornewald]

Hi,
when I tried to run Django's unit tests I faced a little problem: it
wanted me to create a settings file. Why don't you provide a fallback
test configuration with sqlite3 (if that exists)? That would make
testing patches a lot easier. My patch is attached.

Regards,
Waldemar Kornewald

[David Cramer]

Why don't they provide settings for MySQL, PostgreSQL, Oracle, MSSQL,
etc?

On Feb 12, 5:47 am, "Waldemar Kornewald" <wkornew...@freenet.de>
wrote:

> tests.diff
> 1KDownload

[alex....@gmail.com]

Well the reason to use SQLite is that python includes bindings for it,
and you don't have to pick a user with appropriate permissions. Just
sayin'

[Russell Keith-Magee]

This has been proposed and rejected previously, for a very specific
reason: SQLite is only one of the databases that Django supports.
Setting up the test configuration files is not difficult, and is a
documented process. Requiring developers to manually set up a
configuration file for a specific database is one way to reinforce the
fact that ensuring cross-database compatibility is an important part
of the patch development process, and that there isn't a 'default
database'.

Yours,
Russ Magee %-)

[Russell Keith-Magee]

On Feb 13, 2008 1:56 AM, David Cramer <dcr...@gmail.com> wrote:
>
> Why don't they provide settings for MySQL, PostgreSQL, Oracle, MSSQL,
> etc?

If you think about what goes in a MySQL/PostgreSQL/Oracle settings
file, the answer will be obvious.

Yours,
Russ Magee %-)

[Mike Scott]

Further to this I'd like to point out that SQL lite is a very limited database in respect to the other offerings.

Encouraging such a practice, in my opinion, is a really bad idea.

Just my 2c.



Mike