Do you want MySQL with the best possible performance? Then stick to version 5.6, as long as you don't mind it's been EOL for 12 years. 5.7 also has better performance than newer versions, although not as good as 5.6. Some performance regressions are just not being fixed.

https://smalldatum.blogspot.com/2025/08/sysbench-for-mysql-56-thru-94-on-small.html

^^ Veteran database performance guru, Mark Callaghan, former tech lead for MySQL at Facebook and Google, is now an independent consultant who blogs about database benchmarking.

(For my own account as a MariaDB fanboy I must add that another option could be migrating to MariaDB which is a plug-in replacement for MySQL 5.6, as MariaDB has done a better job at avoiding and fixing performance regressions.)

Feel like your collection website could be better but don't know the necessary tools? A few seats left in UMaine's online course in Digital Collections and Exhibitions starting 3 Sep, which teaches  the fundamentals of getting your records in a database and putting them online https://DigitalCuration.UMaine.edu

#Archives #Collections #Data #DigitalCuration #Digitization #Museums #OnlineLearning
#Archives #Collections #DigitalCuration #Digitization #GLAM #Museums #OnlineLearning #PHP #MySQL #Database

Doing a test #mysql to #postgres #database migration for my #mattermost instance. No pressure…

With version 11, that will be mandatory so might as well do it now.

Nothing like running migration tools in #docker as well ;).

Let’s see how this will end up.

#AskFedi how do you implement #database migrations (both schema or data changes) in your app? Say, the new version needs a new table or a new register in an existing table?

Can the end-user access that data or is it encrypted?

Boosts appreciated.
#MySQL #MariaDB #Postgres #PostgreSQL #SQLite #C #Cpp

Has your OS ever refused to install the MariaDB client package or the MySQL client package due to a conflict with the other?

It feels like it should be possible to have both, but unfortunately I have yet to see a solution for this.

For a subset of these cases, all that you want is just to have the client tools such as the mariadb/ mysql CLI and the mariadb-dumper/ mysqldumper backup programs co-existing on the same OS. (I.e. you don't care about the static/dynamic libmariadbclient/libmysqlclient libs etc).

So, I decided to write up my solutions for this:
https://dbdemon.com/installing_mariadb_and_mysql_clients_on_same_unix_host/

If anyone decided to set up #Nextcloud, I've learned that it runs so much better on #PostgreSQL than #MySQL or #MariaDB.

Got Cobra working in Go for my db2xlsx project which exports a MySQL / MariaDB database structure to an Excel file.

Benefits:

Simplifies the parsing
Allows for sub commands
Supports mandatory arguments

Three issues closed as a result, and I'll be able to tackle two of the others based on the groundwork laid.

https://github.com/godev-uk/db2xlsx

Speaker confirmed for #NextcloudConf25!

Michael “Monty” Widenius, creator of #MySQL and co-founder of #MariaDB, will be joining us in Berlin!

Decades of #OpenSource wisdom, from a true pioneer.
Sept 27–28
Berlin, Germany

Tickets: https://nextcloud.com/conference-2025/

Today's fun challenge:

Can't export a MySQL database using MariaDB mysqldump because the tools have now diverged too far

Can't install the MySQL mysqldump because it conflicts with the MariaDB one

Can't use the Docker MySQL image because it doesn't allow interaction (to provide the password)

Can't use the Docker MySQL image with an environment variable because that's ignored when redirecting output to a file

I've used #MySQL before (last time was 2016, I think), but today I'm mostly onto #Postgres (and sometimes, #SQLite). I know PG is superior to MySQL is pretty much all aspect I could think of, but still, it seems that MySQL still has a quite big user base.

What's the catch? What am I missing here? Why would someone use MySQL over Postgres to build smt since Postgres [apparently] is better than MySQL in every single possible aspect?

It's a honest question. Please help me understand it – and perhaps, consider modern MySQL/MariaDB in next projects. :)

TIL: The MySQL Docker image restarts the server after the initial data import, which means if you have enabled the query log using an SQL query it gets reset to being disabled.

If you enable the query log in the config file, this logs every query of the import.

So you have to:

1. Enable in config.
2. Disable using query before import.
3. When the server is restarted, the query log will be enabled.

Better experience and fast, secure way to create a connection with MariaDB.

// Config.php

$mariadb = ini_get('pdo_mysql.default_socket');

$pdo = new PDO("mysql:unix_socket=$mariadb;dbname=test", 'root', '');

if($pdo){
echo "Database connection success!";
}

Want smoother user experience in your PHP apps? Learn how I implement MySQL pagination without the bloat. Clean, scalable, and dev-friendly.
https://mikelopez.com/blog/1118
#PHP #MySQL #DevLife #Pagination #WebDevelopment #BasicPHP

Hey! I’m Yasser Elgammal a backend developer passionate about building clean, scalable solutions with Laravel

I share code, ideas, and open-source projects.

Check out my work on GitHub and let’s connect!
https://github.com/YasserElgammal

#github #php #laravel #backend
#mysql

Aktuell laufen in der Oracle University zwei Event an denen man kostenlos sein Wissen rund um Cloud, Datenbanken, DevOps aufbessern kann. Außerdem kann man kostenlose Voucher für Zertifizierungen erhalten.

Zum einen veranstaltet #Oracle erneut das Race To Certification-Event (bis Ende Oktober) und zum anderen findet im Rahmen des 30. Jubiläums von #MySQL ein ähnliches Event mit Kursen und Zertifikaten statt (bis Ende Juli)

https://education.oracle.com/race-to-certification-2025

https://education.oracle.com/mysql-promo

History : Ericsson Review article about #NdbCluster development at Ericsson. Starts at page 167 (pdf page 179) 1997 volume 4
#MySQL #DistributedSQL

https://www.ericsson.com/4ac5c3/assets/local/about-ericsson/ericsson-history/lme-review/documents/da2011-35598-ericsson_review_vol_74_1997.pdf