I thought about doing the same thing. The problem with that is if the user walks away and the session dies. My solution was to create the records immediately (on the "new" action) , put the id in the session, and then always use that as a reference to update the DB. When all is said and done, and they click "Submit", THEN I associate the record(s) with the user.
<br><br>Hope that helps.<br><br>- Matt<br><br><div><span class="gmail_quote">On 1/30/06, <b class="gmail_sendername">Phil Craven</b> <<a href="mailto:pjcraven@mail.com">pjcraven@mail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
While working on a new application, a friend and I ran into what we<br>think is a problem with using ajax. Users are used to being able to<br>modify the contents of a screen until they are finished and then saving<br>(committing). There does not seem to be a way to do this with ajax,
<br>since you have to modify the model whenever you call back to the server.<br>The half baked solution that we came up with is to create a copy of the<br>child collections and the parent in the session, and modify them. Once
<br>the user submits, everything is then taken from the session and<br>committed. Is there a better way to allow for this kind of functionality<br>and use ajax?<br><br>--<br>Posted via <a href="http://www.ruby-forum.com/">
http://www.ruby-forum.com/</a>.<br>_______________________________________________<br>Rails mailing list<br><a href="mailto:Rails@lists.rubyonrails.org">Rails@lists.rubyonrails.org</a><br><a href="http://lists.rubyonrails.org/mailman/listinfo/rails">
http://lists.rubyonrails.org/mailman/listinfo/rails</a><br></blockquote></div><br><br clear="all"><br>-- <br>Matt Secoske<br><a href="http://www.secosoft.net">http://www.secosoft.net</a>