![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://programming.dev/pictrs/image/3d2f8ea4-8ed4-47c2-bc1c-756d51a0cbf3.webp)
1·
1 year agoEven if I had a createOrUpdate function I would still have an explicit create function so that I can have a permission model that allows for creating but not updating. For meetings maybe it doesn’t matter, but I worked in a financial setting where a very unfortunate design decision was made early on in the development of a ledger where it was crucial that transactions couldn’t be updated, but the database was designed in such a way that there wasn’t a way to give the application permission to create new transactions without also allowing it to update existing ones. Required quite a bit of work to build around this limitation and have a way to prove that a series of transactions hadn’t been altered.
I’m so hyped for this. One of my absolute favorite games for the past 20 or so years!