>From my point of view, the most natural way to reestablish the "least surprise" principle would be to
1. implement .insert and .update methods which would simply execute SQL and return it's errors. 2. abandon the .destroyed? method and its @destroyed instance variable 3. switch .persisted? (@persisted) to false when the record is destroyed or if its .id is manually changed in the program 4. implement .save as something intelligent. Of course such drastic changes might not seem practical... Alexey. -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: 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/rubyonrails-talk?hl=en.
