kpozin
Joined 16 years ago
Karma
1,291
Submissions
174
Member since
Nov 16
hn@{username}.net
View on Hacker NewsJoined 16 years ago
https://www.nytimes.com/interactive/2017/07/15/world/middlee...
https://www.bellingcat.com/news/middle-east/2016/11/01/battl...
https://www.huffpost.com/entry/mosul-satellite_n_596d34a3e4b...
- Google Authenticator
I then had more success signing up with the mobile app, despite using the same phone number; I guess they don't trust their website for account creation.
(The same confusion comes up regularly whenever you touch Next.js apps.)
When I needed to ensure atomicity in such a multi-part "transaction", I ended up making a batch request, where the first statement in the batch checks a precondition and forces a JSON parsing error if the precondition is not met, aborting the rest of the batch statements.
SELECT
IIF(<precondition>, 1, json_extract("inconsistent", "$")) AS consistent
FROM ...
I was lucky here. For anything more complex, one would probably need to create tables to store temporary values, and translate a lot of application logic into SQL statements to achieve atomicity.