4 ms·
Or a traditional database with read-only credentials and a function that adds "ORDER BY version DESC LIMIT 1".
by mathnmusic 5y ago
Or a traditional database with read-only credentials and a function that adds "ORDER BY version DESC LIMIT 1".
- deleted 5y ago[deleted]
- lojack 5y agobut is a traditional database cryptographically secure? if a super user with write permissions (or, say, direct access to the physical data store) modifies records are users able to validate the integrity of the data?
- jayd16 5y agoYou could use permissions and stored procedures that ensure append only.
- jeroiraz 5y agoThe difference is that client applications does not need to trust proper "append-only" permissions were enforced on server side but they will be have the chance to detect any tampering while in the former approach, it won't be noticeable
- mathnmusic 5y agoUsers just need to insert signed data into the database for tamper-proofing.
- dillondoyle 5y agothat's basically what I do in bigquery sometimes just with a time or timestamp column 'last_updated' and a uuid