encapsulate revisions caused by a single transaction in revisionIndex
Opened this issue · 2 comments
GoogleCodeExporter commented
By starting a transaction all including querys should be encapsulated in a
single "transaction-revision". It should be possible to provide key-value meta
information to the transaction (e.g. user executing query, query-origin, ...)
which are reflected in a meta-set inside the transaction-revision.
Advantages would be:
- users expect to be able to see what was caused by a tmql update query as a
single "transaction-revision"
- users would expect the same for rollbacks
- it is important to connect changes made by users to revisions for security
and usability reason (future versions of mt or rtm could provide basic
access-control e.g. modifying a topic is only allowed to he who created a topic)
Original issue reported on code.google.com by michael....@gmail.com on 14 Sep 2010 at 1:00
GoogleCodeExporter commented
Original comment by Sven.Kro...@googlemail.com on 23 Sep 2010 at 6:58
- Added labels: Type-Enhancement
- Removed labels: Type-Defect
GoogleCodeExporter commented
Original comment by Sven.Kro...@googlemail.com on 18 Feb 2011 at 6:12
- Added labels: Milestone-2.0.0