[digikam] [Bug 394291] cannot upgrade mysql db from v7 to v9

[bugzilla_noreply]

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

caulier.gil...@gmail.com changed:

   What|Removed |Added

   Version Fixed In||6.0.0
 CC||caulier.gil...@gmail.com
 Resolution|WONTFIX |FIXED

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 394291] cannot upgrade mysql db from v7 to v9

[Kusi]

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

Kusi  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WONTFIX

--- Comment #6 from Kusi  ---
workaround in comment #1 is good enough

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 394291] cannot upgrade mysql db from v7 to v9

[Kusi]

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

--- Comment #5 from Kusi  ---
I solved the issue by export/import of the database. That is probably good
enough also for other users with this issue. I'm closing this bugreport

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 394291] cannot upgrade mysql db from v7 to v9

[bugzilla_noreply]

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

--- Comment #4 from caulier.gil...@gmail.com ---
Can you reproduce the dysfunction using digiKam 6.0.0 pre-release bundle
available here :

https://files.kde.org/digikam/

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 394291] cannot upgrade mysql db from v7 to v9

[Maik Qualmann]

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

--- Comment #3 from Maik Qualmann  ---
No, the image ids do not change. Presumably, many orphaned will no longer exist
after the migration. The database will certainly be smaller, but nothing should
be lost.

Maik

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 394291] cannot upgrade mysql db from v7 to v9

[Kusi]

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

--- Comment #2 from Kusi  ---
my db is over 12 years old I guess. Looking at the mysql dump, there's indeed
alot of garbage (many unneeded constraints and indexes) compared to how a new
db looks like. Digikam with db v9 is now running, but I'll probably do the
migration to a new db anyways. 

Just one question: do the ids for the images change during migration? I've
added another table (for another project) whos foreign key is images.id.
Therefore I currently rely on Images.id not being changed

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 394291] cannot upgrade mysql db from v7 to v9

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #1 from Maik Qualmann  ---
Your database is probably very old. I can not reproduce at what time the "name"
column in the "Images" table was a BLOB/TEXT field. Log into the database with
mysql and do this:

UPDATE Settings SET value=9 WHERE keyword='DBVersion';

Create a new digiKam database. Then start digiKam and use the migration tool to
export the old current database to the new.

Maik

-- 
You are receiving this mail because:
You are watching all bug changes.