I haven't tracked down this functionality yet, so excuse me if it is already implemented.

As a developer and system administrator I came to a dilemma how to prevent myself to make changes to documents.

I can limit myself as a programmer, but as a administrator I can always logon to console and make changes ''by hand''.

I was thinking of read-only field type, which once set, could not be updated nor removed from document (although backup and restore is the first problem which comes to mind). This limit should be set on a database level. Read-only field could typically hold some computed hash value, which would guaranty that the field or document was not changed in any way.

There could also be collections with read-only documents. For example when ''read-only-document'' field is set, database would prevent any updates (deletes) to document. Although more problems can arise here. Like how to remove outdated documents or move them to archive collection.

by
TheR