Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

We've moved the forum!

Please use forum.silverstripe.org for any new questions (announcement).
The forum archive will stick around, but will be read only.

You can also use our Slack channel or StackOverflow to ask for help.
Check out our community overview for more options to contribute.

Data Model Questions /

Moderators: martimiz, Sean, Ed, biapar, Willr, Ingo, swaiba

Datastore design - history & archival, object versions


Go to End


931 Views

Avatar
zard

Community Member, 25 Posts

20 September 2013 at 3:29am

Hi,

I am developing an extension to build custom itineraries. The idea is that user picks from a list of destinations and this is then added to the itinerary.

I am now solving the problem of what happens to historical itineraries if a destination is modified or deleted? Ideally, once the itinerary is complete, I would like to "freeze" the destination object and make a link to that version from the itinerary. Then, if a destination is removed or modified, the original itinerary still shows the information when it was all valid.

My thinking is to use Versioned dataextension, however, does this also deal with deletions?

Versioned link: http://api.silverstripe.org/3.0/class-Versioned.html