title: Rails doesn't reset ActiveRecord object (new_record?) after error
body: <p>This has been asked here before, but it has been 3 years.  Unfortunately we're still back using Rails 2.3.14, so it's a problem I'm having now and it wasn't really answered back then.</p>
  
  <p>I have 2 models...</p>
  
  <p>Organization
  Organizationpermissions</p>
  
  <p>In the organizations controller, create method, I have the saving of the Organization and the Organizationpermissions objects wrapped in an Organization transaction.</p>
  
  <p>If the Organization saves fine, without error, but the Organizationpermission object fails, the transaction does not properly roll back the Organization object.  The method new_record? thinks the object is not new anymore, which then forces my form to an update action, which I do not want.</p>
  
  <p>This was asked here in 09...</p>
  
  <p><a href="http://bit.ly/MbYGXd" rel="nofollow">http://bit.ly/MbYGXd</a></p>
  
  <p>The outcome was that it was a bug in 2.3.5, but no answer as to how to get around it.</p>
  
  <p>Is there a way around this?</p>
  
  <p>Thanks</p>
  
  <p><strong>UPDATE:</strong></p>
  
  <p>Just trying to bump this to the top.  Probably shouldn't have posted on the weekend.  :)</p>
  
  <p>I still can not figure out what to do here.  When an error is raised and it's not in the main object the ActiveRecord object is not set to new_record? and the page doesn't reflect a create anymore, it's now an update, which is definitely not going to work.</p>
  
  <p>I could have sworn there is a way around this but I can't find it in my code anywhere.</p>