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.
Do others disagree? Evan On Mar 5, 11:44 am, "Oliver Paulus" <[EMAIL PROTECTED]> wrote: > I think it would be nice to have an option to choose if I want partial > updates or not. The default should be the full update. Then every > developer can choose. e.g. In the case of acts_as_list with no extra > relation to the blob I would choose the partial update option. In the > other cases I do not need to change the default. For performance > tuning the developers can test it with the option and without - to > decide if it is needed to have the model "full validated" - means the > validation of different fields in combination, because in the simple > case all fields are present and can be validated against "simple" > rules. If you have 2 or more fields which must be validated in > combination - you should choose the full update option (the default). > What do you think about this? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
