hi graham, no need to apologize! we are definitely not taking your work for granted, and are thankful for your cotinuous support.
cheers, r. On Oct 28, 7:25 am, "Graham Dumpleton" <[EMAIL PROTECTED]> wrote: > 2008/10/28 roberto <[EMAIL PROTECTED]>: > > > > > > >> This is RDBMS specific and also relies on how and where you set up > >> your database connection in the case of database write operations > >> (INSERT, UPDATE, possibly DELETE). > > >>http://www.postgresql.org/docs/8.2/interactive/transaction-iso.html > > >> Postgresql defaults to Read Committed Isolation Level and this appears > >> to also affect how concurrent inserts happen as Erik Jones describes > >> here: > > >>http://bytes.com/forum/post2901040-6.html > > >> Start of thread here: > > >>http://bytes.com/forum/thread728130.html > > >> I would avoid using serializable transaction isolation level as it > >> looks like it needs more code written to handle failed transactions. > > > hopefully graham can tell us more about it, if he comes by. > > Sorry, been overwhelmed with stuff at the moment and haven't even > followed thread well enough to understand problems. I will review the > thread and see if I can come back with a summary of what I think you > are saying the problem is and then hopefully ask some intelligent > questions. :-) > > Graham --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en -~----------~----~----~----~------~----~------~--~---
