I will be heading to Brussels on Friday for FOSDEM.
Tuesday, January 31, 2017
Friday, January 20, 2017
How upgrading MariaDB Server failed because 50M warnings were ignored
This post is part of the series "please do not ignore warnings in MySQL/MariaDB". The previous post of the series can be found here.
In this post, I will present why ignoring warnings made me lose time in upgrading MariaDB Server. I think this war story is entertaining to read and it is also worth presenting to people claiming that ignoring warnings is no big deal.
In this post, I will present why ignoring warnings made me lose time in upgrading MariaDB Server. I think this war story is entertaining to read and it is also worth presenting to people claiming that ignoring warnings is no big deal.
Wednesday, January 18, 2017
Why I wrote "please do not ignore warnings" and "to always investigate/fix warnings" (in MySQL/MariaDB)
In a last post, I wrote the two following sentences:
- please do not ignore warnings
- always investigate/fix warnings
I realized that without context, this might be hard to understand. In this post, I want to give more background about these two sentences.
Friday, January 13, 2017
Oracle MySQL and the funny replication breakage of Friday, January 13
In my previous post, I talked about a funny replication breakage that I experienced with MariaDB. So what about different versions of MySQL...
Funny replication breakage of Friday, January 13
A funny replication breakage kept me at the office longer than expected today (Friday 13 is not kind with me).
So question of the day: can you guess what the below UPDATE statement does (or what is wrong with it) ?
So question of the day: can you guess what the below UPDATE statement does (or what is wrong with it) ?