Bug 375019 - Error updating scheme from digikam 4
Summary: Error updating scheme from digikam 4
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Database-Migration (show other bugs)
Version: 5.4.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-13 20:03 UTC by Rafael Rios Saavedra
Modified: 2017-08-06 21:51 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 5.5.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rafael Rios Saavedra 2017-01-13 20:03:25 UTC
Hi,
  I usually use digikam 4.14.0 from the kubuntu 16.10 packages but today I decided to give a try to digikam 5.4.0.
  I am using digikam 5.4.0 packages from philip5 ppa.

  When I launched digikam5 it asked me to upgrade the database. I am using a mysql server 5.5.52 backend from my NAS server. In the process of updating the schema it reported the following error:
 
  Error messages: "QMYSQL: No es posible ejecutar la consulta" "Specified key was too long; max key length is 1000 bytes" 1071 2 
Bound values:  ()
digikam.dbengine: Error while executing DBAction [ "UpdateSchemaFromV7ToV8" ] Statement [ "ALTER TABLE DownloadHistory MODIFY COLUMN filesize BIGINT;" ]
digikam.coredb: Core database: schema update to V 8 failed!

  The complete log is in the attached log file.
Comment 1 Maik Qualmann 2017-01-14 20:17:05 UTC
Git commit 6dd0f1cb219ecb5062f1434cf82de942f10629fd by Maik Qualmann.
Committed on 14/01/2017 at 19:56.
Pushed by mqualmann into branch 'master'.

fix MySQL DB update to V8 in the table DownloadHistory
FIXED-IN: 5.5.0

M  +2    -1    NEWS
M  +11   -8    data/database/dbconfig.xml.cmake.in

https://commits.kde.org/digikam/6dd0f1cb219ecb5062f1434cf82de942f10629fd
Comment 2 mhoppstaedter 2017-08-06 21:51:50 UTC
Hi,

I also do get that error message in digikam version 5.6.0:

Error messages: "QMYSQL: Die Abfrage konnte nicht ausgeführt werden" "Specified key was too long; max key length is 1000 bytes" 1071 2 
Bound values:  ()
digikam.dbengine: Error while executing DBAction [ "UpdateSchemaFromV7ToV8" ] Statement [ "ALTER TABLE DownloadHistory MODIFY COLUMN filesize BIGINT;" ]