On 04/09/06, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
>
>
> On 9/4/06, Ned Batchelder <[EMAIL PROTECTED]> wrote:
> >
> >
> > Partly on this topic: I would very much like to use sqlite in-memory
> databases for testing, even though I use MySQL for deployment. The speed
> difference is 10x.
Russell Keith-Magee wrote:
On 9/4/06, Ned Batchelder
<[EMAIL PROTECTED]>
wrote:
Partly on this topic: I
would very much like to use sqlite in-memory
databases for testing, even though I use MySQL for deployment. The
speed difference is 10x. One way to do this is to have a
TEST
Hi Russ,
Thanks, that explains the problem with my patch perfectly :)
Your solution looks great: it still solves the original problem while
bringing back the correct functionality if TEMPLATE_STRING_IF_INVALID
is not set.
I can't see that you've missed anything (but then again, I didn't
manage t
On 9/4/06, Ned Batchelder <[EMAIL PROTECTED]> wrote:
Partly on this topic: I would very much like to use sqlite in-memory
databases for testing, even though I use MySQL for deployment. The
speed difference is 10x. One way to do this is to have a
TEST_DATABASE_ENGINE setting, and add logi
Justin Bayer wrote:
> Hi django-users,
>
> I developed an application locally and used it with my postgres
> database, which used unicode as the server_encoding. Everything worked
> fine.
>
> Recently I deployed it onto a system where the postgres server_encoding
> is sql_ascii.
>
> After insta
Partly on this topic: I would very much like to use sqlite in-memory
databases for testing, even though I use MySQL for deployment. The
speed difference is 10x. One way to do this is to have a
TEST_DATABASE_ENGINE setting, and add logic to create_test_db().
Thoughts?
--Ned.
Adrian Holovat
