On Sat, 17 May 2008 13:04:36 +0200 Sebastian Bauer <[EMAIL PROTECTED]> wrote: > Thank you for answer, but for update, i think, is really important > for commercial projects and places where you need to be sure that no > one changed row in parallel
I don't think that commercial projects have an exceptional position. But if FOR UPDATE is important for your project, you can use the patch as Russel already told you. But if the only thing you want to do is to ensure that data aren't changed between several SQL statements you can go with transactions, which are supported very well, by django at the moment. Regards Sebastian Noack
signature.asc
Description: PGP signature
