http://gallium.inria.fr/blog/intel-skylake-bug/
"More experienced programmers know very well that the bug is generally in their code: occasionally in third-party libraries; very rarely in system libraries; exceedingly rarely in the compiler; and never in the processor."
If it causes an issue with our own systems it also gives me a very good justification for doing it.
And then many other times I honestly don't have the knowledge to be able to contribute into large third party systems and it seems very rare to get an issue resolved without submitting a pr.
And lastly sometimes it's hard to judge if unexpected behavior is really a 'bug'. Similar to the last point, it can honestly be hard to tell the difference sometimes.
Given that you mention China in your story, did GB 18030 have anything to do with your problems?
Writing the pre-ANSI-JOIN-support SQL dialect code was pretty good fun though.
Near as I can tell, we assume there is some bit of magic built into the foreign key concept that handles this for us, but that is not the case.
But it seems like I am missing your point: care to expand on it so I can learn about the gotcha as well? What are you attempting to do, and what's making the performance slow?
Or in the case of Silicon Valley, leave everything in tact with a disabled flag and then spam you for the next decade or so.
Which is more or less what the GP says as well, deletes are not implemented because doing it properly requires proper design.
Oracle was called in, "en masse". Keep also in mind that Oracle Portal was basically running on top of lots of dedicated tables and stored procedures and you could not access the data directly, you interacted to the contents only through vistas, aliases etc.
It was indeed due to a smallish version bump. But we had a pretty good Team Leader who had made Oracle declare that the two different version were absolutely compatible and allowing us to write code on the older version.
He made them state this in written form, before starting the development so it was later impossible to blame the developers for the problem.
load tests usually only happens on staging env, not production, that is the policy.
This was the first time regular people could go buy tickets for events & they had been lining up overnight at Bank of China locations through the country. We were down for over a day before we called it off. Apparently this led to minor upheaval at several locations in Beijing & riot police were called in.
We were pretty puzzled as we had an index and had load tested extensively. We had Oracle support working directly with us & couldn't figure out why queries had started to become table scans.
The culprit? A point upgrade to DBD::Oracle (something like X.Y.3 to X.Y.4) introduced subtle but in character sets. So the index required using a particular Unicode character set, and we were specifying it, but when it was translated into the actually query, it wasn't exactly the right one, so the DB assumed it couldn't use the index. Then, when all the banks opened & a large portion of very populous country tried to buy tickets at the same time, things just melted.
Not a fun day.