Problem with changes hash about audited

[bkeepers]

@lesburg: I've run into this issue before too. It is because AR already has a #changes method defined, which show the changes to the current model since it was last saved. And due to the way that AR defines attribute accessors lazily, when you first call #changes, you're getting AR's version. But dumping the record causes it it define the attribute accessors.

To work around this, acts_as_audited should either explicitly define #changes, or rename it to something else that doesn't conflict.

[robg]

I'd vote for renaming to something other than #changes. Having an audit-specific #changes attribute causes problems with some of our change detection logic.

I'm find with doing that. I don't have time to work on it anytime soon, but if someone wanted to submit a patch, I'd be happy to pull it.

The patch should probably keep compatibility with the current version, and maybe deprecate the #changes method.

[kennethkalmer]

As part of #30, the changes field has been renamed to audited_changes and should address this just fine. I'm closing this issue, please re-open if I've missed the plot completely.

[psahni]

When I use object.attributes['changes'], the problem seems to be resolved for temporily

eg:-
a1 = Audit.first

a1.changes # {}
a1.attributes['changes'] # required changes hash say {:name => ['Prashant', 'Prashant Sahni']}