@Adriaan
Switching the database backend (local to MySQL or MySQL to PostgreSQL) You can not directly clone the database because there needs to be some conversion done.
But it is pretty straight forward. Now as you have setup your new backend and still have your old backend (local) available. You launch the mAirlist Database select your local database on startup and somewhere in the Menu you will find Import and Export funktion. Choose CSV as the target to export.
Than close your mAirlist database and open it again. Now choose your new MySQL Backend. Here you can import the CSV File you have exported before.
Actually I’m not sure if you have to initialise the Database first like in your screenshot
Or if you can just start the import, just give it a try.
Ok, so you want to migrate your existing (local mode) mAirListDB to a MySQL backend, right?
This is what “Clone database” in the DB App (Database → Export → Clone Database) is made for. Works for any SQL type (networked or local mode) for source and target.
These are the steps to perform:
Create user and empty SQL database in your MySQL server. Do not add the connection to the mAirList configuration at this time! In particular, do not perform the initial setup (create tables) in the config! The database must be entirely empty, and no tables created! (@Adriaan, just remove and recreate the database in the MySQL administration to start over.)
Open the DB app (of the existing local mode app) and go to Database → Export → Clone database. Select MySQL as the target type, and enter IP/user/password/database as required. Cloning will copy the tables row by row, so it might take a long time. You can choose to transfer only part of the playlist history to speed up the process.
When the cloning is done, close the DB app and make sure no mAirList.exe process is running anymore.
Go to the config, Databases section, and remove the existing local mode DB connection.
Then add a new connection of type “mAirListDB (MySQL)”, enter host/etc. again, and use the “Test login” button to check if everything is working.
Step 4 (remove old connection) is very important; there must not be the original and the cloned connection set up at the same time, this would confuse the system because both databases have the same ID. Removing the connection will not delete the .mldb file. You can and should keep it as a backup, and you can re-add it anytime later as a local mode connection if anything goes wrong, or you need to restart the clone for any reason.
Check your library if there are any items with a “Loudness” value of “-INF”. (You can add Loudness as a library column in the View menu, and then sort by that column.)
It was caused by a bug in the R128 scanner in earlier versions. Not a real problem until you try to use the Clone function
Use Mass Edit to re-do the loudness scan for these items. The -INF should go away in favor of just an empty entry. Then retry to the clone.
“Change Database ID” is only necessary if you want to use the old (local) and new (SQL) databases side by side. If you remove the old connection as described in my earlier post, don’t change the ID.
Tonight I also changed the lokal db to my sql.
Almost at the eind I also get a fault a file was bigger as expected.
The database looked fine but I noticed that all the history, last played is missing.
Any chance to get it back.
I still have the original lokal db file.
My nas (Synology) runs on 6.2 yesterday I got an email that support ends 24 Oktober. You should upgrade to 7 but 7 don’t support maria bd 5. So I need to upgrade to Maria db 10 before I upgrade to version 7. On the Synology website it looks quite simple export the database in maria db 5 and Import it in 10. Are there additional staps in mairlist to make or is it that simple?
