dm-is-versioned doesn't work with dm-timestamps

[solnic]

Due to changes in the way dm-timestamps updates the timestamps, dm-is-versioned will no longer trigger the saving of new versions when updated_at changes. This is because dm-timestamps bypasses the property accessor methods dm-is-versioned uses to determine changes and instead uses property#set.

See the attached script for the effect this has.

---

Created by Jonathan Stott (namelessjon) - 2010-01-20 13:46:29 UTC

Original Lighthouse ticket: http://datamapper.lighthouseapp.com/projects/20609/tickets/1184

[solnic]

It’s no longer an issue.

by Piotr Solnica (solnic)

[solnic]

hmm actually it still doesn’t work even though dm-timestamps uses #attribute_set now

by Piotr Solnica (solnic)

[solnic]

You do have a pull request sitting in the repository that actually fixes this:

#3

The original bug is related to dm-is-versioned hooking #{attribute}= and keeping track of changes itself instead of using datamappers internal tracking of dirty attributes. So it never sees change done by attribute_set.

Sorry for the late mentioning in the bugtracker.

Regards,
Florian Gilcher

by Florian Gilcher