by uziubalmy » Tue Sep 30, 2014 10:25 am
Thanks, but as you can imagine I perfectly know that I can delete the db.
But I have hundreds of playlists and thousands of playcounts that aren't tag in the file and the ratings in the db not Always are the same of the file.
For me make a db from zero is not a choice.
I've a backup of ten days ago, but in these days I've do a lot of things on the added tracks.... I know that it's my fault that I don't have a back up (1,6GB of dayily backup can happen that the space is not enough sometimes and the backup stops for few days)
so I tried to use sqlite3.exe, I can dump perfectly all the sql. The problem is the IUNICODE collation is not supported and I can't remake the db.
So I tried softwares that can load the dll with the IUNICODE collation like SqliteBrowser and SQLiteSpy.
SQLiteSpy can't export/dump the db/sql.
SqliteBrowser can do the dump with no problem, can make a new db, but when I try to execute the sql exported it crash (its 1,3GB of sql file, I don't know if it's the size or other...)
and hower also with SQLiteSpy that is fully supported with the mediamonkey.dll gives an error reading the db (unkown tokenizer: mm) on a table (songstext)
reading on internet seems that if there were not all these specific things (like the custom collation) people can restore a corrupted db with sqlite3.exe.
it' scandalous that in 2014 for a simple writing error there are engines that corrupt the db.
opensource enginees of my in then BallmerWorldOfSqlCEOrSqlServer would never have happened.
Thanks, but as you can imagine I perfectly know that I can delete the db.
But I have hundreds of playlists and thousands of playcounts that aren't tag in the file and the ratings in the db not Always are the same of the file.
For me make a db from zero is not a choice.
I've a backup of ten days ago, but in these days I've do a lot of things on the added tracks.... I know that it's my fault that I don't have a back up (1,6GB of dayily backup can happen that the space is not enough sometimes and the backup stops for few days)
so I tried to use sqlite3.exe, I can dump perfectly all the sql. The problem is the IUNICODE collation is not supported and I can't remake the db.
So I tried softwares that can load the dll with the IUNICODE collation like SqliteBrowser and SQLiteSpy.
SQLiteSpy can't export/dump the db/sql.
SqliteBrowser can do the dump with no problem, can make a new db, but when I try to execute the sql exported it crash (its 1,3GB of sql file, I don't know if it's the size or other...)
and hower also with SQLiteSpy that is fully supported with the mediamonkey.dll gives an error reading the db (unkown tokenizer: mm) on a table (songstext)
reading on internet seems that if there were not all these specific things (like the custom collation) people can restore a corrupted db with sqlite3.exe.
it' scandalous that in 2014 for a simple writing error there are engines that corrupt the db.
opensource enginees of my in then BallmerWorldOfSqlCEOrSqlServer would never have happened.