On 11/02/2011 12:47 PM, Marco Paolini wrote:
if that option is true, sqlite shoud open one connection per cursor
and psycopg2 should use named cursors
The sqlite behavior leads to some problems with transaction management -
different connections, different transactions (or is there some sort of
"shared
transaction" in sqlite?). I would just fetch all the data in one go when
using
sqlite. I wouldn't worry about performance problems when using sqlite, it is
meant mostly for testing when using Django.
This will cause some overhead for small querysets but will save some memory
for huge ones
For PostgreSQL this would be a nice feature. Any idea what MySQL and Oracle
do currently?
- Anssi
--
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 unsubscribe from this group, send email to
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.
