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
On Feb 13, 2008 3:55 PM, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
>
> On Feb 13, 2008 1:5
On Feb 13, 2008 1:56 AM, David Cramer <[EMAIL PROTECTED]> 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 %-)
--~--~-~--~~--
On Feb 12, 2008 10:47 PM, Waldemar Kornewald <[EMAIL PROTECTED]> wrote:
> 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
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'
On Feb 12, 10:56 am, David Cramer <[EMAIL PROTECTED]> wrote:
> Why don't they provide settings for MySQL, PostgreSQL, Oracle, MSSQL,
> etc?
>
> On Fe
Why don't they provide settings for MySQL, PostgreSQL, Oracle, MSSQL,
etc?
On Feb 12, 5:47 am, "Waldemar Kornewald" <[EMAIL PROTECTED]>
wrote:
> 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
> tes
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
--~--~--
