Shadowing Practice: MySQL took 21 years to fix this bug - Learn English Speaking with YouTube
C1
In my 16 years as a software developer,
190 sentences
If sentences are too short or too long, click Edit to adjust them.
1
In my 16 years as a software developer,
2
nothing made me happier than avoiding an annoying bug long enough for someone else to accidentally fix it,
3
or for the entire feature to be removed before I ever had to touch that code.
4
In fact, after years of hard work and dedication,
5
I can proudly say that I have polished this skill to perfection.
6
As some of the more experienced among you already know,
7
avoiding a ticket without looking like you are avoiding a ticket is an art form.
8
You cannot just ignore it,
9
because that is amateur work.
10
A seasoned senior software developer who earns their keep will occasionally comment something vague,
11
like, I'll have to circle back to it when my priorities allow it,
12
or this is a tough one,
13
but I believe I'm finally close to a solution.
14
Then, they let a little more time pass and hope for the best.
15
And, hope, as you eventually learn,
16
is basically at the core of software development.
17
So when I tell you
18
that the MySQL team avoided a single bug ticket for 21 years and somehow made it look almost professional,
19
understand that I say this with deep, deep respect.
20
When a bug is first reported in 2005,
21
and you get to fix it in 2026,
22
we should all sit down,
23
take notes and learn a thing or two about surviving this industry.
24
The bug in question is MySQL bug number 11472,
25
filed on June 21st, 2005.
26
To give you a sense of how long ago that was,
27
the iPhone did not exist,
28
the most popular browser on Earth was Internet Explorer 6
29
and Sam Altman was busy creating a social network instead of convincing the world
30
that AI tokens are as important as access to electricity or water.
31
We see a future where intelligence is a utility,
32
like electricity or water, and people buy it from us.
33
Anyway, the reported bug was apparently pretty straightforward.
34
Triggers were not firing when a foreign key cascade modified a row.
35
For those unfamiliar with relational databases,
36
a foreign key is basically a rule that says that this piece of data,
37
like some orders, depends on some other piece of data, like a customer.
38
Cascades, on the other hand,
39
are what happen when the database automatically propagates a change through that relationship.
40
So when you delete a customer,
41
the database can be told to automatically delete that customer's orders for you.
42
Now, there is a whole separate discussion about whether physically deleting records from a database is a bad practice,
43
but that is not the topic of this video.
44
Just keep in mind that in many cases,
45
you are better off keeping the records in the database and using a soft delete instead,
46
which simply means marking a row as deleted with a boolean flag.
47
Back to the bug, when one of these automated cascade deletes happens,
48
my SQL goes and removes the affected child rows for you,
49
but it does it quietly.
50
So quietly that the triggers attached to those rows have no idea anything happened.
51
Triggers, if you have not run into them before,
52
are little bits of code that you tell the database to run automatically whenever a specific event happens on a specific table.
53
Again, there is an entire discussion on the topic of best practices
54
when it comes to triggers and there is an ongoing fight about them in the industry.
55
The modern application crowd will tell you triggers are invisible,
56
untestable and a debugging nightmare
57
and honestly they are not wrong a trigger does not show up in your git dev
58
or in code review and a new developer joining your team might be surprised to find out
59
that half the logic of your application is happening inside the database fired off by little scripts
60
that nobody has looked at for the past 15 years also triggers do not translate
61
when you migrate from one database to another because every database has its own slightly different trigger syntax.
62
On the other hand, the database crowd,
63
mostly old-school DBAs, will tell you
64
that triggers are the only thing in your entire stack that catches every change to your data,
65
no matter where it came from.
66
If you have three different services,
67
a cron job, and some random script all writing to the same database,
68
only a trigger sees all the changes reliably.
69
But enough with the boring theory,
70
let's get back to the actual bug report.
71
A few days after the initial report,
72
the MySQL team says the plan is to fix it in their upcoming 5.1 release.
73
Again, take notes, because this is the kind of confidence you guys need to succeed in this career.
74
Then, a few days, sorry,
75
a few years pass, and in 2007,
76
a new comment from the team states that MySQL's own foreign key implementation will eventually fix this,
77
but it will still take some time.
78
Then, two years later, the confirmation that this bug will not be fixed in 5.1 is posted.
79
In 2013, 8 years in,
80
a user asks for an update.
81
The official reply this time,
82
and I want you to appreciate the craftsmanship here,
83
says Note that there is major development work needed to fix this issue,
84
it will not be a mere bug fix.
85
At this point, the bug is starting to become somewhat of a meme because a user replies in the thread,
86
the guys over at Oracle probably aren't getting any of these messages because their triggers aren't firing.
87
This joke was funny for 13 years straight.
88
It's important to note that during this time MySQL changed owners multiple times.
89
It started as an open source database built by a small Swedish company.
90
It was bought by Sun Microsystems in 2008 for $1 billion,
91
which at the time felt like a lot of money.
92
Then, in 2010, Oracle bought Sun and inherited MySQL together with the second best programming language in the world.
93
And since we are talking about billions of dollars,
94
please let me tell you a few words about today's sponsor.
95
PostHog is a platform built to help developers and product managers build their dream projects by helping debug their product,
96
understand their customers, analyze usage and ship more successful features faster.
97
They make things really easy for you by putting all the tools and data you need in one place.
98
This means product analytics, web analytics,
99
session replay, error tracking, experimentation,
100
feature flags, LLM analytics, surveys and many more.
101
Then, they give you an actually useful AI agent to make sense of it all.
102
PostHog's data infrastructure is tailored for data engineers who need to build a robust
103
and flexible data stack to house all their business data.
104
And since all data lives on the same platform,
105
you can watch what users actually did,
106
see where they got stuck,
107
roll out a fix behind the feature flag,
108
test whether it worked, and then use the same data to decide what to build next.
109
The setup is as simple as installing one of the available SDKs or pasting a snippet into your site header,
110
which will then auto-capture data like page views, button clicks and sessions.
111
So, if you are building a product and want analytics,
112
replay, flags, experiments, errors, surveys and AI-powered insights without stitching together 5 different tools,
113
please check out PostHog using the link below.
114
Back to the video, by 2015,
115
the comment section enters its second phase when users start showing up on the bug's birthday to leave congratulatory messages like,
116
Happy Anniversary, it's 10 years already,
117
this defect is going to be attending middle school in the fall and happy 13th birthday they grow up so fast.
118
By 2020, we hit a third phase.
119
A user writes, this bug is older than me.
120
The original reporter, who filed a bug in 2005,
121
gets pinged by someone asking if he's still alive
122
and he shows up the next day to confirm he is still using MySQL.
123
Now, jokes aside, the reason this bug took 21 years to fix is actually pretty interesting
124
and it traces its roots in an architectural decision made in the late 90s
125
that turned out to be very hard to walk back.
126
To explain what happened, I need to tell you a little about how MySQL is built,
127
because once you understand the structure,
128
the whole bug starts to make sense.
129
MySQL is built into layers.
130
On top, you have what is called the SQL layer,
131
sometimes also called the server layer.
132
This is the part of MySQL that takes your queries,
133
parses them, plans how to execute them,
134
and then asks for the data.
135
It is also the part that handles things like triggers,
136
views, stored procedures and user permissions.
137
Anything that thinks in terms of SQL statements lives here.
138
Underneath, you have the storage engine.
139
The storage engine is the part that actually reads and writes the bytes on disk.
140
This component deals with pages, indexes, logs and transactions.
141
My SQL is unusual because its storage engine is pluggable,
142
which means you can swap it out,
143
but for the past 15 years,
144
everyone has been using InnoDB.
145
Now, in most databases, foreign keys live in the SQL layer.
146
This layer knows about the foreign key,
147
this layer enforces it, and when a cascade fires,
148
this is the layer that generates the cascade operation as if it were a normal SQL statement.
149
As a result, triggers fire normally,
150
because triggers are also a SQL layer concept.
151
MySQL on the other hand implemented foreign keys inside the InnoDB storage engine.
152
The reason is historical and this is also your awesome trivia for the day.
153
Early versions of MySQL did not support foreign keys at all.
154
The MySQL team famously did not really believe in them
155
and you can actually find a page in their version 3 manual titled Reasons not to use foreign keys.
156
Their arguments age like milk.
157
The first reason they mentioned in the manual is
158
that foreign keys make life very complicated because the foreign key definitions must be stored in a database.
159
The second reason was that foreign keys are slow and unnecessary and you,
160
the developer, will simply remember to insert records in the right order.
161
So when they finally added foreign key support,
162
they bolted it onto InnoDB,
163
because InnoDB was the only engine at the time that supported transactions.
164
The SQL layer was never involved,
165
so foreign keys became strictly an InnoDB feature.
166
So when you run a query such as this one,
167
here is what actually happens step by step.
168
The SQL layer parses your query,
169
it fires the before delete trigger if it exists,
170
then it hands the actual delete operation to InnoDB.
171
InnoDB then notices, on its own,
172
that there is a foreign key with onDelete cascade pointing at the orders table.
173
So it walks the orders table,
174
finds all the orders that belong to that customer and deletes them itself right there in the storage engine.
175
But then, the engine never bubbles back up to the SQL layer to notify it about the additional deletions.
176
So the SQL layer, sitting up there with all the triggers,
177
is perfectly willing to fire them,
178
waiting for someone to tell it that rows on the orders table have changed.
179
This was the issue, and as you can see,
180
this is what the MySQL team meant in 2013,
181
when they wrote that this was not a mere bug fix,
182
but major development work.
183
The two systems that need to talk to each other are architecturally separated.
184
And to finally fix the problem,
185
the team did the thing they had been putting off for 21 years.
186
They moved foreign keys out of InnoDB and up into the SQL layer.
187
If you liked this video,
188
you should consider joining our community where I'm posting more dedicated weekly content.
189
Please don't forget to smash all the buttons and until next time,
190
thank you for watching.
Download App
AI scoring for every sentence you speak
TRENDING
Popular
Why practice speaking with this video?
Engaging with the content of the video titled "MySQL took 21 years to fix this bug" offers a unique opportunity to enhance your English speaking skills. As the speaker shares their experiences in the software development industry, they not only provide insight into technical topics but also showcase conversational nuances that are beneficial for learners. By watching and practicing with this video, you can improve your ability to articulate complex ideas and technical jargon, which is essential for IELTS speaking practice and professional environments.
Additionally, the speaker's use of humor and personal anecdotes makes the content relatable, providing you with an engaging context to practice your spoken English. The idea of "avoiding a ticket" creatively illustrates how seasoned professionals navigate challenges, allowing learners to grasp story-telling elements in English communication. This combination of narrative and technical discussion helps learners expand both vocabulary and ability to express thoughts in varied contexts, making it an effective choice for those looking to learn English with YouTube.
Grammar & Expressions in Context
Throughout the transcript, the speaker employs several key grammatical structures and expressions that can enhance your English speaking proficiency:
- Past Perfect Tense: The speaker refers to their experiences with phrases like "I have polished this skill to perfection." This structure emphasizes the completion of an action before another point in the past, useful for narrating personal achievements.
- Conditional Sentences: Phrases such as "If you get to fix it" illustrate hypothetical situations. Understanding and utilizing conditionals can help you express possibilities and scenarios succinctly.
- Descriptive Language: The speaker employs rich descriptions, such as "avoid an annoying bug long enough." This adds color and detail to communication, making it more engaging and effective in conveying ideas.
- Vague Language: The use of non-specific comments like "I’ll have to circle back to it" highlights how native speakers often use indirect language in professional settings. Understanding this nuance can greatly improve your workplace communication skills.
Common Pronunciation Traps
As you practice speaking with this video, be mindful of particular words and phrases that may present pronunciation challenges:
- “Cascades”: The 'c' and 's' sounds can be tricky. Practice breaking it down into syllables: cas-cades.
- “Propagates”: This word features multiple syllables, making it easy to stumble. Focus on clear articulation and rhythmic pacing: prop-a-gates.
- “Deleting”: The 'd' and 'l' sounds in succession can be difficult for learners. Slow down and emphasize each sound to enhance clarity.
- “Trivially”: This adverb may trip you up. Try practicing it in sections: triv-i-al-ly, ensuring you articulate each syllable distinctly.
By practicing with these points in mind, you will not only improve your vocabulary but also gain confidence in your speaking abilities, making your english speaking practice sessions more productive. Embrace the content of the video and let it guide your journey toward fluency!
What is the Shadowing Technique?
Shadowing is a science-backed language learning technique originally developed for professional interpreter training and popularized by polyglot Dr. Alexander Arguelles. The method is simple but powerful: you listen to native English audio and immediately repeat it out loud — like a shadow following the speaker with just a 1–2 second delay. Unlike passive listening or grammar drills, shadowing forces your brain and mouth muscles to simultaneously process and reproduce real speech patterns. Research shows it significantly improves pronunciation accuracy, intonation, rhythm, connected speech, listening comprehension, and speaking fluency — making it one of the most effective methods for IELTS Speaking preparation and real-world English communication.
☕ Buy us a coffee
ShadowingEnglish remains 100% free thanks to your support. Server and AI costs are high — your coffee keeps us going! 🙏