Correct. Lift's mapper doesn't change the default isolation level of your connections, nor does it make explicit use of pessimistic concurrency control.
However, the default connection manager set the connection to autocommit=false, runs a local transaction for the scope of HTTP requests and automatically commits after the request by default. You can control the isolation level using JDBC (e.g., passing parameters in your JDBC URL) or by setting the isolation explicitly in a custom ConnectionManager. Anything beyond that we can probably implement, we just need a good reason... alex On Sun, Dec 6, 2009 at 6:54 PM, cody koeninger <[email protected]> wrote: > Do mapper or record provide any assistance for avoiding race > conditions caused by the database transaction isolation level? I > didn't notice anything in my initial skim of the lift book, and > grepping the code for obvious suspects like "for update" didn't return > anything. > > If not, what are people with production lift apps doing? Run postgres > in default read committed and cross your fingers? > > -- > > You received this message because you are subscribed to the Google Groups > "Lift" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<liftweb%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/liftweb?hl=en. > > > -- You received this message because you are subscribed to the Google Groups "Lift" 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/liftweb?hl=en.
