Hello, I''ve encountered some annoying problem with accepts_nested_attributes_for Model is: http://pastie.org/584213 Request is: http://pastie.org/584216 Controller is: http://pastie.org/584222 Record before request = Record after request: http://pastie.org/584225 Within the request, asemployees_attributes is a hash containing two key/value pairs: key 0 - An employee already associated with this relation key 1250268515769 : An employee added using javascript while updating the event For some reason 1250268515769 is not associated with the object - no "INSERT INTO asemployees_events (..) VALUES (...)" happens on SQL-side. What might be wrong here? Thanks in advance Keep smiling yanosz
Hello, On Friday 14 August 2009 18:59:19 Jan Lühr wrote:> I''ve encountered some annoying problem with accepts_nested_attributes_for > Model is: http://pastie.org/584213 > Request is: http://pastie.org/584216 > Controller is: http://pastie.org/584222 > Record before request = Record after request: http://pastie.org/584225 > > Within the request, asemployees_attributes is a hash containing two > key/value pairs: > > key 0 - An employee already associated with this relation > key 1250268515769 : An employee added using javascript while updating the > event > > For some reason 1250268515769 is not associated with the object - > no "INSERT INTO asemployees_events (..) VALUES (...)" happens on SQL-side. >I filed it as https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/3052-assign_nested_attributes_for_collection_association-ought-to-assign-objects-for-collection-if-an-id-is-given-but-the-object-is-currently-not-associated Feel free to comment. Keep smiling yanosz