Awesome. I look forward to investigating. I'd like to build something
that eventually leads to a coherent solution for people to choose
between various locking and updating methodologies.
Jeremy Kemper wrote:
On Jul 28, 2006, at 11:22 PM, Josh Susser wrote:
The other way to do dirty checking is to do it on an object basis,
instead of by columns. I'd love to be able to track what associated
objects had been modified so that when I save an order, all the line
items that got modified get saved too. Then of course I'll want an
identity map in AR so that I don't have multiple, possibly
inconsistent model objects floating around for just one record. I
think I can see a good way to do the identity map, but only the
vaguest idea of how AR might save dirtied children automatically.
Would these things be PDI-level enhancements, or a waste of time to
look into?
I recall Jamis did object-level dirty checking by MD5ing attributes.
Search for 'smart saves' on trac (when it's back with us, the
living-breathing.)
jeremy
_______________________________________________
Rails-core mailing list
Rails-core@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-core
--
Michael Genereux
SimianCodex - Web Application Development
949-874-6268
_______________________________________________
Rails-core mailing list
Rails-core@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-core
