I'm assuming it's the "I'm sure it'll be fine to read/write this unsynchronized, what's the worst that could happen?" locking strategy.

That just sounds like the "read uncommitted" transaction level. Works as long as you know what to do :)

IIRC some IBM DBs have a level called 'chaos', it may be read uncommitted but with other side effects...

Is that like accidentally pure functions?

"what's the worst that could happen?" implies some forethought. Delusional Locking just goes "It's gonna be fine! LALALALALA I CaN'T HeAr YoU"

You can submit a feedback! https://docs.google.com/forms/d/e/1FAIpQLSf7XQBKbpjtOqzFi0jB...