4 ms·
With concurrency it's certainly reasonable to hit constraints in production. Another session deletes something, another inserts a row that attempt to reference
by anarazel 9y ago
With concurrency it's certainly reasonable to hit constraints in production. Another session deletes something, another inserts a row that attempt to reference the deleted row. Or you have multiple users registering with the same account name at the same time. Etc.
- maxxxxx 9y agoThat makes sense. I guess most of the stuff I do doesn't do much concurrent database access.
- semiquaver 9y agoYou might think that, but the most common cause of constraint violation in the web-programming world is unintentional user double clicks setting up a race between simultaneous requests.
- Something1234 9y agoCause they get frustrated when your app isn't fast or responsive enough.
- vbsteven 9y agoYou would be surprised to see how many (often older) people double click everything by default. Explorer folders, desktop shortcuts, web forms, it is all the same to them. I’ve run a number of event sites for luxury car brands and it was stunning how many double-click form submissions we received on those. Often just milliseconds apart.
- maxxxxx 9y agoIt's not only old.people who do the double click thing. I see the same with a lot of our sales reps when I watch them use our stuff.
- daveFNbuck 9y agoThe mouse I use at work turns a large percentage of my single clicks into double clicks. There are lots of reasons people might double-click other than frustration.