Bug#895937: database upgrade from schema 8 to 9 fails - workaround

2020-02-17 Thread tv.deb...@googlemail.com

On 17/02/2020 22:39, Agustin Martin wrote:

On Sat, Apr 21, 2018 at 02:16:26AM +0530, tv.deb...@googlemail.com wrote:

Since Digikam crashes on Mariadb database conversion I tried reverting to
older Digikam version, but that only gave me an empty view. So the database
is unusable with the previous Digikam versions.
Restoring a previous database version leads to the same result: failed
conversion, corruption that makes it unusable with previous Digikam version.

I downloaded the Digikam 5.9 appimage from digikam.org, which fails to
convert the database too, but doesn't crash. From it I was able to migrate
the Mariadb database to sqlite (conversion is very slow). Using the sqlite
was totally impractical due to sluggishness and high system load, so I
converted it back to "external Mysql" (Mariadb) with the exact same settings
in database configuration as the previous one 'user, db names...).
Again conversion is slow but about twice as fast as the other way round.

Important, once conversion back to Mariadb is complete, and Digikam settings
have been switched back to external Mysql database, Digikam scanned all
content but displayed an empty view. I needed to close and relaunch before I
could see the images.

I can now use Digikam 5.9 from Debian Unstable with the newly converted
Mariadb external database, I did not notice any data loss, tags are intact
too..

So problem solved for me, the double database conversion workaround is time
expensive but works.


Hi,

According to upstream bugtracking system

   https://bugs.kde.org/show_bug.cgi?id=393855

this seems fixed in digikam 6.0. Since Debian sid already has 6.4.0, I expect
this problem to be fixed in Debian.

Can we close this bug report?

Thanks for your contribution to Debian.

Regards,

Hi, as far as I am concerned this bug can be closed. All new upgrades 
proceeded without any problem regarding the database.
Currently using 6.4 from unstable with Mariadb (about 6 
photos/videos in the main library, + tags and faces) and having no issues.


Thank you for your time and your hard work.



Bug#895937: database upgrade from schema 8 to 9 fails - workaround

2020-02-17 Thread Agustin Martin
On Sat, Apr 21, 2018 at 02:16:26AM +0530, tv.deb...@googlemail.com wrote:
> Since Digikam crashes on Mariadb database conversion I tried reverting to
> older Digikam version, but that only gave me an empty view. So the database
> is unusable with the previous Digikam versions.
> Restoring a previous database version leads to the same result: failed
> conversion, corruption that makes it unusable with previous Digikam version.
> 
> I downloaded the Digikam 5.9 appimage from digikam.org, which fails to
> convert the database too, but doesn't crash. From it I was able to migrate
> the Mariadb database to sqlite (conversion is very slow). Using the sqlite
> was totally impractical due to sluggishness and high system load, so I
> converted it back to "external Mysql" (Mariadb) with the exact same settings
> in database configuration as the previous one 'user, db names...).
> Again conversion is slow but about twice as fast as the other way round.
> 
> Important, once conversion back to Mariadb is complete, and Digikam settings
> have been switched back to external Mysql database, Digikam scanned all
> content but displayed an empty view. I needed to close and relaunch before I
> could see the images.
> 
> I can now use Digikam 5.9 from Debian Unstable with the newly converted
> Mariadb external database, I did not notice any data loss, tags are intact
> too..
> 
> So problem solved for me, the double database conversion workaround is time
> expensive but works.

Hi,

According to upstream bugtracking system

  https://bugs.kde.org/show_bug.cgi?id=393855

this seems fixed in digikam 6.0. Since Debian sid already has 6.4.0, I expect
this problem to be fixed in Debian.

Can we close this bug report?

Thanks for your contribution to Debian.

Regards,

-- 
Agustin



Bug#895937: database upgrade from schema 8 to 9 fails - workaround

2018-04-20 Thread tv.deb...@googlemail.com
Since Digikam crashes on Mariadb database conversion I tried reverting 
to older Digikam version, but that only gave me an empty view. So the 
database is unusable with the previous Digikam versions.
Restoring a previous database version leads to the same result: failed 
conversion, corruption that makes it unusable with previous Digikam version.


I downloaded the Digikam 5.9 appimage from digikam.org, which fails to 
convert the database too, but doesn't crash. From it I was able to 
migrate the Mariadb database to sqlite (conversion is very slow). Using 
the sqlite was totally impractical due to sluggishness and high system 
load, so I converted it back to "external Mysql" (Mariadb) with the 
exact same settings in database configuration as the previous one 'user, 
db names...).

Again conversion is slow but about twice as fast as the other way round.

Important, once conversion back to Mariadb is complete, and Digikam 
settings have been switched back to external Mysql database, Digikam 
scanned all content but displayed an empty view. I needed to close and 
relaunch before I could see the images.


I can now use Digikam 5.9 from Debian Unstable with the newly converted 
Mariadb external database, I did not notice any data loss, tags are 
intact too..


So problem solved for me, the double database conversion workaround is 
time expensive but works.