Why not defer making changes at the DB level until the person is done with the page. Ye olde Save or Cancel (or just navigate away).
An Ajax request and DB update per "fiddle" with a row seems overdone to me, but if your interface doesn't use an explicit "save" button or something similar, then it could work. As for the Ajax part, I haven't ventured there myself yet. -- 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 -~----------~----~----~----~------~----~------~--~---
