Arya Asemanfar

I don't disagree. In fact that solution was stated in my original ticket. The reason I patched it the way I did was because my particular use case needed me to ...

I can understand not wanting to have the old value be in the unserialized form, but why can't the new value be the raw value as well?

Patch doesn't apply anymore because the relevant code was moved from base.rb to persistence.rb, but the problem still exists. I just tried the test on master an...

Here is a patch and test for this ticket.

My earlier comment cleared the assigned user because I had loaded the form before it was assigned, so I'm assigning it...

Here is a patch for a test as described above. It's not the same situation as described in the original ticket, but it does break the same assumption that cause...

To create a failing test, there would have to be an identity map or the test would have to override AR's instantiate method to shim in identity behavior.

To cla...

I should clarify that the ID column is not an auto-increment column.

@matt Facebook application, we use their facebook user id as the id column. When you interact with a friend on the app, their record is created by their ID.

If there is a race to create a new record for the same ID, and you try to reload, the resulting record is in an inconsistent state.

For example, if two processe...

I'll start off by saying this bug is not reproducible without the use of an in-process identity map plugin. Given that, the bug is in the way ActiveRecord choos...