Well I'm trying to do it from the list action, so there is no save button, though I could do that. It's not a bad idea. Maybe enable/ reveal a link_to or button_to after a change is made?
On Nov 10, 7:50 am, Ar Chron <[EMAIL PROTECTED]> wrote: > 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 viahttp://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 -~----------~----~----~----~------~----~------~--~---
