Changes between Version 19 and Version 20 of metadatachanges
- Timestamp:
- Jan 10, 2012, 3:04:42 PM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
metadatachanges
v19 v20 54 54 The second approach is slightly more difficult to code: subversion changes need to be bundled by keeping the subversion commit editor open and using a listener to commit/ignore the changes to the subversion repository when the database is committed/aborted. This scenario is complicated by the design of the tmatesoft api which does not allow reentrant calls on a subversion repository object and does not allow files and directories in the repository to be opened more than once in a transaction eg. as described at http://osdir.com/ml/version-control.subversion.javasvn.user/2007-10/msg00053.html. 55 55 56 The third approach is the one that has been implemented. The coding is slightlymore straightforward than the second approach and only slightly more complex than the first.56 The third approach is the one that has been implemented. The coding is more straightforward than the second approach and only slightly more complex than the first. 57 57 58 58 To illustrate the third approach, let's examine a typical scenario where we wish to capture changes to the privileges of a metadata record made by a user in the 'Set Privileges' function: