Dave's MySQL Stuff

I help facilitate the MySQL track at SCaLE. I am seeking first-time presenters who can discuss MySQL.  I am also looking for old-timers who haven't spoken in a while at a conference and those who have forgotten to submit a talk.  The MySQL Community is at a crossroads, and the MySQL track will cap off a day with a panel on the past, present, and future of MySQL.  T he 23rd Annual Southern California Linux Expo –   SCaLE 23X   – will be held   March 5-8, 2026   at the   Pasadena Convention Center   in Pasadena, California, near Los Angeles. You are invited to share your work on  FOSS programs  and  open hardware projects  with the rest of the community, as well as exchange ideas with some leading experts in these fields. Please share your MySQL skills and experiences! You can make a significant impact by sharing with others, and this is an excellent opportunity to professionally network at the largest open-source ...

  You are trying to load a CSV file into a database, and almost inevitably, you run into an  ERROR: value too long for type character varying 64  if you are using PostgreSQL.  Or  SQL Error [1406] [22001]: Data truncation: Data too long for column 'Name' at row 1  if you are using MariaDB or MySQL. It doesn't matter if you are using the  DBeaver  application or the native database import tools. Newbies will look at the first line of the CSV file to examine the very first line and scratch their heads, as there is no error in the first line. The database is ingesting the data one line at a time, so each line in the file is the first line. Your line in the CSV file is hiding deep in the file. And there may be many of them in there.  The error message you receive is helpful, but it DOES NOT tell you which line in the CSV file is causing you this grief. You could use an 'eyeball inspection' of the data, which quickly becomes tedious. And if the CS...

There are many reasons you may want to migrate from MySQL to PostgreSQL, which we will skip over for brevity.  I see many questions about moving tables and data, and sadly, the answers range from sloppy to incredibly complicated.  Each database migration is unique, as issues range from heavily relying on a vendor's feature to extremely complex schemas that require attention to minute detail. Step 1 This may seem obvious, but the first step is access to the original 'source' database. You will need FULL admin access to the database.  If you do not have full access for security, administrative, or other reasons, you will most likely not receive all the desired data.  We will use DBeaver Enterprise to connect to the source database. We need to choose a MySQL database driver Configure the connection We will be porting the World database. In this example, we will port the MySQL World database. This dataset has been used for decades in MySQL documentation, training, and ex...