Justin Reagor on 24 Jan 2008 11:49:45 -0800

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Re: [PhillyOnRails] ActiveRecord: updating a single attribute

  • From: Justin Reagor <justinwr@gmail.com>
  • To: talk@phillyonrails.org
  • Subject: Re: [PhillyOnRails] ActiveRecord: updating a single attribute
  • Date: Thu, 24 Jan 2008 14:49:21 -0500
  • Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:mime-version:in-reply-to:references:content-type:message-id:from:subject:date:to:x-mailer; bh=4epUafOQa/2MeRP8rWjI7umXBu4VuUHIKcmSgVxSQc4=; b=FY6tvyR+B/tgmvSEqMdqqS41wBa86RcZNA7QZI+edOgK/4Kl1fSo2ArtTxiAHuWttW6Mw/ZoJPyLtVILRJujXfo/iemNQ1W/NujE0ElmLJw3Ji0Z72UXj/IpJZBS3QcpJZr27j+6HHi5HNrQSz6NUxKfYTNgczwAro7uHZybu+I=
  • List-archive: <http://lists.phillyonrails.org/pipermail/talk>
  • Reply-to: talk@phillyonrails.org
  • Sender: talk-bounces@phillyonrails.org

I believe this also jives with Sequel...

On Jan 24, 2008, at 2:43 PM, Eric Snyder wrote:

"ActiveRecord updates every column in a row during a save whether that

column changed or not. So it performs work it doesn't really need to.

Which is much slower, and is likely to eat data during concurrent

access if you don't go around adding locking support to everything."

To unsubscribe or change your settings, visit: