Re: Transactions and model.save()

On 5/17/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > > On 5/16/06, Elver Loho <[EMAIL PROTECTED]> wrote: > > Let's take the poll sample. We've got the vote() view going on. > > > > choice.votes += 1 > > choice.save() > > > > Suppose we've got thread1 and thread2 going on (high-load website): >

Re: Transactions and model.save()

On 5/16/06, Elver Loho <[EMAIL PROTECTED]> wrote: > Let's take the poll sample. We've got the vote() view going on. > > choice.votes += 1 > choice.save() > > Suppose we've got thread1 and thread2 going on (high-load website): > > choice.votes is originally 16 > > thread1.choice.votes += 1 > thread

Re: Transactions and model.save()

Elver Loho wrote: > Hiya! > > Someone raised this question in the comments of the 4th tutorial and > it's been bugging me to no end. > > Let's take the poll sample. We've got the vote() view going on. > > choice.votes += 1 > choice.save() > > Suppose we've got thread1 and thread2 going on (hig

Transactions and model.save()

Hiya! Someone raised this question in the comments of the 4th tutorial and it's been bugging me to no end. Let's take the poll sample. We've got the vote() view going on. choice.votes += 1 choice.save() Suppose we've got thread1 and thread2 going on (high-load website): choice.votes is origin