#174 dirty objects shouldn't clear changed attributes after a save failure - Ruby on Rails

Type	To find
responsible:me	tickets assigned to you
tagged:"@high"	tickets tagged @high
milestone:next	tickets in the upcoming milestone
state:invalid	tickets with the state invalid
created:"last week"	tickets created last week
sort:number, importance, updated	tickets sorted by #, importance or updated
Combine keywords for powerful searching.
Use advanced searching »

This project is archived and is in readonly mode.

#174 ✓resolved

dirty objects shouldn't clear changed attributes after a save failure

Reported by Xavier Noria | May 12th, 2008 @ 11:55 PM

Dirty objects shouldn't clear changed attributes after a save failure.

Repository May 13th, 2008 @ 01:05 AM
- State changed from “new” to “resolved”
(from [593e21d6aedcc05d744be4996bd7180edce57efe]) Dirty attributes aren't cleared if save fails. [#174 state:resolved]
Signed-off-by: Jeremy Kemper
http://github.com/rails/rails/co...

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

<h2 style="font-size: 14px">Tickets have moved to Github</h2>

The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>