Given a database that supports `GET`, atomic `SET`, and atomic `DELETE` operations, is it possible to implement a list that can be safely appended to?

洪民憙 (Hong Minhee)

Given a database that supports GET, atomic SET, and atomic DELETE operations, is it possible to implement a list that can be safely appended to?

{Insert Pasta Pun}

@hongminhee does order need to be preserved, and do you care about duplicates?

dee, love and enby

@hongminhee is only-once reading of a list item important to you?

Emelia 👸🏻

@hongminhee I'd think no, since the client would need to first read the data before appending to the data and writing it back.

{Insert Pasta Pun}

@dee @hongminhee or if you had to pick:

At most once

Or

At least once

{Insert Pasta Pun}

@thisismissem @hongminhee is there a case for "use sqlite it will work most of the time"? (If you can make it act like redis)