[okfn-help] vdm: pending state

Wed Sep 22 20:51:21 BST 2010

Hi there,

I'm trying to work out how to implement a 'pending' story for vdm.

My use case is something as follows:

* there's an application that edits the data: the "editable" data or "pending"

* there's also the "published" version of the data.

* certain can publish changes (add/update/removals made)

I understand vdm maintains the database in the normal tables, which
you'd access as if the content wasn't
revisioned. It then retains information about this and other revisions
in the revision tables.

In the pending use case, should the normal tables contain the pending
information or the published information? Both
kinds of information needs to be easily accessible - one by the edit
application and the published data by applications that handle this.

It was suggested to me in the past to add information with the state
set to PENDING, but how would one transition away from that state?

Any design suggestions?

Regards,

Martijn