> I think partial updates are so rarely desirable, and so rarely give a > significant speed increase, that it is better to force the developer > to use raw SQL in that situation.
In case of acts_as_list and the move_higher method (e.g.) you have to change your model design - I think an option like :dynamic_update => true would be fine for this case. I love the Rails way of developing apps easily. If you use native SQL your code gets more ugly. Why not add an :dynamic_update => true to save, etc? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
