diff options
author | Johnny Holton <johnny@holton.co> | 2013-04-10 23:29:19 -0400 |
---|---|---|
committer | Johnny Holton <johnny@holton.co> | 2013-05-02 03:27:06 -0400 |
commit | 483c301e0a132a6415355be2296fb932d07bd1c5 (patch) | |
tree | 2d644bfa199b89e6df0584772a5d24585e5d7779 /railties/.gitignore | |
parent | dfd5dc93a1ead62353cc33f5065e23b4fdf25b3e (diff) | |
download | rails-483c301e0a132a6415355be2296fb932d07bd1c5.tar.gz rails-483c301e0a132a6415355be2296fb932d07bd1c5.tar.bz2 rails-483c301e0a132a6415355be2296fb932d07bd1c5.zip |
destroys association records before saving/inserting new association records
fixes bug introduced by #3329
These are the conditions necessary to reproduce the bug:
- For an association, autosave => true.
- An association record is being destroyed
- A new association record is being created.
- There is a unique index one of the association's fields.
- The record being created has the same value as the record being
destroyed on the indexed field.
Before, the deletion of records was postponed until after all
insertions/saves. Therefore the new record with the identical value in
the indexed field caused a non-unique value error to be thrown at the database
level.
With this fix, the deletions happen first, before the insertions/saves.
Therefore the record with the duplicate value is gone from the database
before the new record is created, thereby avoiding the non-uniuqe value
error.
Diffstat (limited to 'railties/.gitignore')
0 files changed, 0 insertions, 0 deletions