[digikam] [Bug 375019] Error updating scheme from digikam 4

2017-08-06 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=375019

mhoppstaed...@gmx.de changed:

   What|Removed |Added

 CC||mhoppstaed...@gmx.de

--- Comment #2 from mhoppstaed...@gmx.de ---
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;" ]

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

[digikam] [Bug 375019] Error updating scheme from digikam 4

2017-01-14 Thread Maik Qualmann 
https://bugs.kde.org/show_bug.cgi?id=375019

Maik Qualmann  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
  Latest Commit||https://commits.kde.org/dig
   ||ikam/6dd0f1cb219ecb5062f143
   ||4cf82de942f10629fd
   Version Fixed In||5.5.0
 CC||metzping...@gmail.com
 Resolution|--- |FIXED

--- Comment #1 from Maik Qualmann  ---
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-1NEWS
M  +11   -8data/database/dbconfig.xml.cmake.in

https://commits.kde.org/digikam/6dd0f1cb219ecb5062f1434cf82de942f10629fd

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