On Monday 02 June 2003 08:18 pm, Andr� van Toly wrote: > Pierre van Rooden heeft op maandag, 2 jun 2003 om 16:21 > (Europe/Amsterdam) het volgende geschreven: > > [...] > > > [1c] Since MMBase has no locking mechanism, the wizard maintains a > > 'original data' xml tree. The Dove uses this tree to validate changes > > (so if someone changes the object, the wizard issues an error). > > Perhaps a less memory-consuming way can be found to check on changes > > in an object (so the original data tree is not needed), but I gather > > this would either require versioning (or 'last modified dates'), or > > another method to make comparison easy (hashcodes?). > > All nodes in MMBase have at least two fields: number and owner. These > are deeply rooted in the core but is it not worth investigating to add > an extra field 'updated' or 'modified'? Or would that involve a > complete rewrite of MMBase? This is quite possible (at least for new installation) and it's a nice to have but i don't think this solves the problem. it still doesn't allow locking. it is something like a timestamp field
what we need is a form of locking. wiab did this by first creating a copy of a node (with relations) and keeping meta data in a nodeversions builder. > Nodes could be checked out and tagged with the last modified date. And > when they are checked in again they can be checked against the last > modified date in the database. > > ---Andr� > > ------------------------------------------->><<--------- > Andr� van Toly > http://www.toly.nl > 06-27233562 > > -- Kees Jongenburger Mediapark C101 Hilversum +31 (0)35 6772910
