A VersionConstraint specifies, upon FullDataSet::prune(), what values to actually prune, and which to keep, what DataSetTags to keep, and if the whole DataSets should be deleted or not.
Located in /harmoni/core/dataManager/versionConstraints/VersionConstraint.interface.php (line 14)
| Class | Description |
|---|---|
| DateVersionConstraint | Limits pruning based on a cutoff date, specified in the past. The date is passed to the constructor, and can be a specific date or a relative date, like "-2 weeks" or "-12 hours". Dates in the future will throw an error. |
| NumberVersionConstraint | Removes versions based on the number for a certain value stored in the database. The maximum number allowed is passed to the constructor, and any extra values will be deleted based on age. |
| PruneAllVersionConstraint | Prunes out ALL inactive values, of everything. |
Takes a Record and returns if it is still valid or should be deleted. TRUE if it's still OK.
NOTE: if a Record is flagged for deletion and the children are not, then there's gonna be broken data in the database.
Takes a RecordFieldValue object and sets "prune" flags for all versions based on whether it should be
pruned from the database or not, depending on the constraint specified in this object. If the version is active, though, nothing is done!
Takes a Record and checks all the tags to make sure none of them fail the constraints. If they do, it asks the RecordTagManager to delete them from the database.
Documentation generated on Wed, 19 Sep 2007 10:27:41 -0400 by phpDocumentor 1.3.0RC3