# How to use set\_versionstamped\_key

**URL:** <https://forums.foundationdb.org/t/how-to-use-set-versionstamped-key/604>\
**Category:** Using FoundationDB\
**Created:** [August 1, 2018, 9:53am UTC](https://forums.foundationdb.org/t/how-to-use-set-versionstamped-key/604 "2018-08-01T09:53:50Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![alloc](https://sea1.discourse-cdn.com/foundationdb/user_avatar/forums.foundationdb.org/alloc/32/9_2.png) [@alloc](https://forums.foundationdb.org/u/alloc)\
**Post date:** [August 2, 2018, 8:27pm UTC](https://forums.foundationdb.org/t/how-to-use-set-versionstamped-key/604/3 "2018-08-02T20:27:30Z")

</div>

In addition to what @alexmiller mentioned, you might also want to see this [discussion](https://forums.foundationdb.org/t/versionstamp-uniqueness-and-monotonicity/602), which went into some pitfalls that you might run into if you need to perform a restore on a database that you have decided to use versionstamp operations or if you decide you need to be able to copy versionstamped data between FDB clusters.

---

_[View the full topic](https://forums.foundationdb.org/t/how-to-use-set-versionstamped-key/604)._