(proposal) Journal transaction editing history

[sfount]

We currently have no way of differentiating transactions that have been edited and transactions that were directly written by the system.

If an accountant or developer is trying to audit the system to find out where something has gone wrong it would be very useful to know if something has been changed to know where to look for the issue.

I propose we introduce a new table transaction_history that we will write in every time an editing session is successfully run on a transaction.

The columns would be

• uuid
• transaction_uuid
• timestamp
• user_id
• (optional) Operations ['EDITING', 'DELETING', 'ADDING']

Whilst this doesn't give us a history of the full transaction it will be a good first step towards answering questions:

Has a transaction been edited?

SELECT COUNT(uuid) as numberOfEdits FROM transaction_history WHERE transaction_uuid = ?

Who has edited a specific transaction?

SELECT user_id, timestamp FROM transaction_histroy JOIN user ON user_id = user.id WHERE transaction_uuid = ?

[jniles]

To clarify, transaction_uuid should be record_uuid, correct?

This proposal LGTM. Just knowing if a transaction has been messed with can inform us what next questions to ask.

[jniles]

Note - this is tangentially related to #1559

[jniles]

I'll tackle this one.

The optional fields don't make much sense to me - this kind of resolution needs to be available on a line-by-line basis, not a transaction basis.

The only update I'll make is renaming transaction_uuid -> record_uuid since that is the column name found in the posting_journal and general_ledger.

[jniles]

Closed in #2156.