On 3 syys, 03:17, Jeremy Dunck wrote:
> I have been working on a master/slave router library [1] and have run
> into some trouble testing a client application of it.
>
> The issue is that TestCase (as designed) holds test db writes in a
> transaction, but the read slave connection (which is to the
I have been working on a master/slave router library [1] and have run
into some trouble testing a client application of it.
The issue is that TestCase (as designed) holds test db writes in a
transaction, but the read slave connection (which is to the same DB
under TEST_MIRROR) does not have visibi
… and this is exactly why the app-refactor has been a topic of
discussion for several years. Hopefully we'll get a chance to thrash
out some of the details this week at DjangoCon US; I know Preston (who
has been working on the patch of late) is keen to discuss what he's
done.
Yours,
Russ Magee %-)
Another good reason for model loading at startup is a good idea; without it,
models.get_models becomes a lie.
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/django-
