Request option to write multiple versions in a single batch

[songmelted]

So, I was able to find a temporary work around here:

Keeping key version when adding same key on the same transaction

Is it possible to keep the key version when adding the same key from the same transaction (or write batch)? For example: If I add a key a in the same transaction twice, only the last one is commited: txn := db.NewTransaction(true) defer txn.Discard() err = txn.Set([]byte("a"), []byte("41")) if err != nil { log.Fatal(err) } err = txn.Set([]byte("a"), []byte("42")) if err != nil { log.Fatal(err) } if err := txn.Commit(); err != nil { log.Fatal(err) } This will return only 42 when I itera…

Relevant quote below

open the database as a managed DB…specify the version timestamp for each key and then my values will be added correctly

HOWEVER

My transactions are coming in so fast that time.Now().UnixNano() returns the same value for multiple entries. Because time.Now().UnixNano() is not designed to return the current nanosecond. On my hardware, it can take 10ms before it updates. This causes the undesired behavior of dropping versions.

To work around that I keep an incremental counter that I add to the result of time.Now().UnixNano() to guarantee uniqueness.

All of this seems a bit hacky. I would like to see an option that causes this behavior. Additionally, I am unsure if this hacky approach could have potentially unwanted side effects.

To me, it seems like if there is a ‘keep multiple versions’ option, there should be a related option to ‘keep multiple versions within a single transaction’. It seems reasonable to me that if someone wants to keep multiple versions that they would want to do so even within the same transaction.