On Oct 20, 1:40 pm, David Lee <[email protected]> wrote: > I originally thought up a similar solution, but realized that it, like > your proposed solution, always did an UPDATE of the row, even if > columns of the row did not change. I don't think there's a good way to > go about this except for the change the happen in Sequel's > implementation of hooks. I know you think the change would require > overturning a lot of the current implementation, but that's the amount > of work it would take to override the current behavior in a subclass.
You may not be aware that if no columns have changed, but the record is considered modified, and you call save_changes, Sequel doesn't actually send an UPDATE query. That may change how you think about the problem. Hint, you may want to look at the nested_attributes plugin. :) Jeremy --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sequel-talk" 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/sequel-talk?hl=en -~----------~----~----~----~------~----~------~--~---
