Summary: | Error updating scheme from digikam 4 | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Rafael Rios Saavedra <rafael.rios.saavedra> |
Component: | Database-Migration | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | metzpinguin, mhoppstaedter |
Priority: | NOR | ||
Version: | 5.4.0 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | https://commits.kde.org/digikam/6dd0f1cb219ecb5062f1434cf82de942f10629fd | Version Fixed In: | 5.5.0 |
Description
Rafael Rios Saavedra
2017-01-13 20:03:25 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 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;" ] |