Update problem - no track at the playlist

[turntable]

The Update from 1.6.5.7 to 1.7.0 doesn't work properly - see the screen shot.

Maybe I make a fault during the update process?

First I did a database backup, using the Database Setup Tool from the old 1.6.5.7 version - like the explanation.

Then I Select Update File from the unzipped SQL-Folder from the NEW version. Trying the update with 1.6.5.8 RC7 - Update from RC4 and older.sql. - This update process stopped in the middle. Than I tried the other version (1.6.5.8. RC7 - Update from RC6) - the update is complete! Wonder why?

Then I copied all files from the new version to the folder with the old version. Starting the new radiodj.exe the database setup asked for the name from the database und the password. I did it. The result is the screen shot - there are no songs at the playlist.

I hope, anybody has a solution for this problem - thanks in advance!

[attachment deleted by admin]

[Marius]

When it stopped, it showed some error?
If you skip that update the program won't run!

[turntable]

When it stopped, it showed some error?

Jep, when it stopped the infobox of the Database Installation shows:

Restore process was interrupted by an exception.
Import ErrorMySql.Data. MySqlClient. MySqlException: Out of range value for column "bpm" at row 3361 bei MySql.Data.MySqlClient. MySq ...

The following infos are cutted, because there is no way to scroll the infobox.

[Marius]

Ok, now we are getting somewhere. It seems that a track has larger value for bpm that it was designed for the database.

First, restore the old unmodified database backup.
Open "1.6.5.8 RC7 - UPDATE FROM RC4 AND OLDER.sql" in notepad and search for

Code: [Select]

ALTER TABLE `songs` CHANGE `bpm` `bpm` DOUBLE(5, 1) NOT NULL;
and change it to

Code: [Select]

ALTER TABLE `songs` CHANGE `bpm` `bpm` DOUBLE(11, 1) NOT NULL;
and apply the update. That's the only update file you need to apply.

PS: Update RadioDJ directly to 1.7.2 and don't stick with older versions please.

[turntable]

TNX Marius,

the problem is now solved!
After editing the SQL-file, the update works!