Wouldn’t that be an error due to serialisation failure if in postgres if you enabled serialisable isolation?
If you didn’t, you could get anything, because unless I’m mistaken this is the typical example used to illustrate what goes wrong when you don’t have full serialisable isolation.
Ah yes, cats, so aloof. Meanwhile my cats: won’t stop miaowing until I pick them up, pet them or play with them, if I put my hand out will jump up to bop it before I can reach them, will tap me for pets if I’m out of reach…
So aloof!
What if my favourite are Gentoo’s but I don’t want to spend years of my life waiting for my OS to compile from source?
You can get a caffeine free coke zero and diet coke tho
Bras are just a pair of pockets if you think about it.
And right now…
Fuck you I WANT A BIG CHOMP
What’s it like having parents who are proud of you?
Why would repeatable read raise an error? I’m a little rusty but I thought it was only serialisable that could do, and that repeatable read simply ensured that the committed writes of transaction 2 would not be read in transaction 1, so it updating over the top of 2 is fine.