Screw MySQL/MariaDB. Who the fuck thought not to document that utf8 is only 3 bytes and not unicode capable. You have to use utf8mb4 for it to work. Fuck those idiots that don't want to admit they made a mistake and put this info in a footnote on a pricy documentation piece.

Ok, so I basically spent my weekend trying to work out why the fuck my python docker container would not connect to my mariadb docker container. Tried fucking everything, bridged network, host network, links (even though theyre deprecated), you name it. It would NOT WORK!

In my despair I finally turned to StackOverflow. There I was told 5min after posting the question that the reason was probably that mysql is a quite heavy service, which takes a bit to start up.

I thought to myself "Oh, get the fuck outta here, that can't be it, shit's way too easy to work!"
I tried it nevertheless by adding a 10sec delay before querying the database AND THE MOTHERFUCKING PIECE OF SHIT ACTUALLY WORKS!! So, I essentially just lost a weekend because I was too impatient... I think I'm gonna punch some trees now.

Spent the last month creating a really scalable chat application, with fast front end, all kinds of neat functions such as polls, and a really efficient database structure in Apache Cassandra.. Everything is built to use NoSQL, and even the front-end is using all kinds of features to speed up itself... Now, guess what... The company I'm doing an internship decided that everything needs to be done in MariaDB, and I can basically remove 1/3 of my program, event the front end will get a huge purge of code, and as much as I explained that MariaDB IS NOT FUCKING USABLE FOR A CHAT APPLICATION, and when there are many messages, the access times will get realllllyyy sloow, and that the whole structure there currently is based on NoSQL... Now I can remove all the clustering, custom data types, and bucketing of messages... And store FUCKING JSON IN 'TEXT' FIELDS IN A STUPID SQL DATABASE. FUCK ME

I just created an Oracle account just to comment on a mysql bug report in order to inform people to use mariadb as a fix ¯\_(ツ)_/¯

^w should delete back a word, not to the beginning of the line! This is broken because instead of readline, Oracle's mysql-client uses editline.

Yet why the fuck do you compile mysql-client with editLine wrapper that breaks the common keybindings?

Licenses is why. Oracle wants to avoid using GNU GPL, and readline uses just that, so they use editline since it has BSD. And they just don't seem to give a damn if it breaks usability.

STOOOOP TELLING ME THE TABLE DOESN'T EXIST. YOU'RE FUCKING SUPPOSED TO CREATE THE DAMN TABLE NOT TELL ME IT DOESN'T EXIST! YOU FUCKING DID IT AT HOME ON MY DESKTOP SO WHY DO YOU DO THIS TO MEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEeeAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

God fucking damn this stupid MariaDB is full of bugs... First access denied because I tried to login as root as non root and now that... Damn...

I some time's feel stupid when my Ubuntu start acting up on prod, purge this and that ,fuck apache can't start system CTL that ps ax grep in the p#$#@* , damn apt install nginx full good, mysql can't start too ,OK apt install mariadb-client else percona && apt postgresql thanks ,god no client noticed ..

Why the actual fuck is MariaDB disguised as MySQL in the AUR?!? Is there just no way to install MySQL from the AUR anymore?

Fuck PHP, fuck Lamp stack and fuck MariaDB

Fuck!

I just accidentally installed mariadb and completely fucked mysql. Probably by now I've deleted my databases, but luckily nothing very important.

Time to get round to setting some proper backup system I suppose.

What the absolute fuck

Can someone explain why `SELECT foobar FROM sometable` works in MariaDB while `SELECT sometable.foobar` doesn't?

The error is "code 1109. Unknown table foobar in field list"