custom timestamp

[ktmud]

So if I read the code correctly, we can use

db.put(key, value, { version: timestamp })

to set custom timestamp for a record, instead of current Date?

How about make it explicit by alias options.version to options.timestamp?

db.put(key, value, { timestamp: ... })

It is also preferable if some option is provided to indicate that we are using timestamp as the version when creating an instance of level-version .

[brycebaril]

I would be fine adding an alias that maps options.timestamp to options.version

I'm not sure I follow the last part about level-version -- the default version stamp function in level-version is Date.now()

[ktmud]

What I'm trying to say is, when timestreamdb creates a level-version instance, it depends on the version stamp to be a timestamp, but not explicitly asked it.

If this level-version is a totally 3rd party module, when its maintainer changes this default behavior, timestreamdb will break.

Also, by stating timestamp configuration both in creating and transforming, it will be easier to understand the code, without the need to dive into what does level-version secretly do.