Hmm, that's interesting Russ.

So, if I understand what you are suggesting is a syntax that allows
the operation to be performed in the database and not on the server?

If the resultant sql utilizes a sub-query, that might be an issue (for
the same concurrency problems as stated above).

I think for now I have to resort to some hand-crafted sql and do a SET
TRANSACTION explicitly myself.

Thx
S


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to