2007/10/10, David Larlet <[EMAIL PROTECTED]>:
>
> BTW, no more thought about the way of handling PUT? I've just added a
> patch against test.client which add .put() and .delete(), I'm waiting
> for (a) reaction(s) to add tests and documentation.
>
Sorry for insisting on that point but this is imp
http://spielwelt6.knightfight.de/?ac=vid&vid=121044096
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscrib
On Oct 15, 5:10 pm, Stefan Bethge <[EMAIL PROTECTED]> wrote:
> Just an addition. I would not recommend using oracle with django if
> you don't have an enterprise version which contains the oracle
> connection manager. Without it you won't have connection pooling
> functionality which slows down dj
Ivan Sagalaev napsal(a):
> Malcolm Tredinnick wrote:
>> However, I think all our Python db wrappers pull things to the client
>> immediately
>
> BTW, a couple of months ago we were investigating behavior of mysqldb in
> this regard and found out that doing fetchall and fetchmany indeed eats
> t
