Re: [PhillyOnRails] ActiveRecord: updating a single attribute

["Grant Ammons" <grant@fakeboard.com>]

The more I hear about merb, the more I want to move to it.

merb + YARV would be a sexy beast.  Too early though.

The grass is always greener...

-Grant

On Jan 24, 2008 2:43 PM, Eric Snyder < snyderep@gmail.com> wrote:

I've just started mucking about with Datamapper & merb and came across
this from the DataMapper "Why Datamapper?" page.

"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."

Just sharing, I too am perfectly ok with the way ActiveRecord handles updates.



On Jan 24, 2008 2:29 PM, Colin A. Bartlett

<phillyonrails@colinabartlett.com> wrote:
>
>
> On Jan 24, 2008, at 2:22 PM, Aaron Blohowiak wrote:
>
> Remember, when it comes to performance: "it's not a problem, until its a
> problem."
>
> Amen.
>
> I'm an advocate of not nitpicking over performance at first.
> Of course, there's always low hanging fruit that you can take care of out of
> the box.
>
> C
>
>
> Colin A. Bartlett
> Kinetic Web Solutions
> http://blog.kineticweb.com
>
>
>
>

> _______________________________________________
> To unsubscribe or change your settings, visit:
> http://lists.phillyonrails.org/mailman/listinfo/talk
>
>
_______________________________________________
To unsubscribe or change your settings, visit:
http://lists.phillyonrails.org/mailman/listinfo/talk

_______________________________________________
To unsubscribe or change your settings, visit:
http://lists.phillyonrails.org/mailman/listinfo/talk