QLDB Removing Document Updates when updating multiple documents within the same transaction.

Question

I am commiting several updates to several documents within one transaction. I use the transaction id to the request those documents which have been updated.

If I commit an update with 3 changes to a single document it looks like it only creates a single document with last change reflected.  I cannot force QLDB to record the changes as three separate document versions, which is what I want.

Is there some optimisation that happens on the updates Im sending or is there a way to force QLDB to create three versions of the document for each change. I want to track the changes individually, I dont want an optimised change?

Dan

Answer

Hello,

Thank you for using AWS QLDB.

QLDB records history per transaction. Anything executed between StartTransaction and CommitTransaction will have the same transactionId, hence users sees 1 history record. If the user would like to see multiple histories they can run multiple transactions in a QLDB session. [[QLDB session lifecycle] ](https://docs.aws.amazon.com/qldb/latest/developerguide/driver-session-management.html#driver-session-mgmt.lifecycle)

Hope my above response has helped and answered your query.

QLDB Removing Document Updates when updating multiple documents within the same transaction.

Relevant content