[digikam] [Bug 379987] UpdateSchemaFromV7ToV8: Unable to execute query (MySQL specific)

2018-01-04 Thread Quincy
https://bugs.kde.org/show_bug.cgi?id=379987 --- Comment #15 from Quincy --- Current AppImage Version (including your fixes) happily upgrade DB Version 8->9. Upgrade of a restored V7 DB to 8 (and then 9) first fails with: digikam.dbengine: Failure executing query: Error messages: "QMYSQL: Unable

[digikam] [Bug 379987] UpdateSchemaFromV7ToV8: Unable to execute query (MySQL specific)

2017-12-30 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=379987 --- Comment #14 from Maik Qualmann --- Git commit 051d57aa66d72ff3aa35e7240aed027434576254 by Maik Qualmann. Committed on 30/12/2017 at 19:21. Pushed by mqualmann into branch 'master'. add drop procedure to delete index M +24 -18 data/database/db

[digikam] [Bug 379987] UpdateSchemaFromV7ToV8: Unable to execute query (MySQL specific)

2017-12-30 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=379987 Maik Qualmann changed: What|Removed |Added Latest Commit||https://commits.kde.org/dig |

[digikam] [Bug 379987] UpdateSchemaFromV7ToV8: Unable to execute query (MySQL specific)

2017-12-30 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=379987 --- Comment #12 from caulier.gil...@gmail.com --- yes it clear now. I would to patc the handbook about the 127.0.01 tip from Maik when you use a local (remote) database, but if you said that it do not work as expected, i wait more details before. Gille

[digikam] [Bug 379987] UpdateSchemaFromV7ToV8: Unable to execute query (MySQL specific)

2017-12-30 Thread Quincy
https://bugs.kde.org/show_bug.cgi?id=379987 --- Comment #11 from Quincy --- I'm using MySQL on the very same computer as digikam. This is "local", but not internal to digikam as the MySQL server is running separately (for web development and other stuff, too). Because it is the same computer this

[digikam] [Bug 379987] UpdateSchemaFromV7ToV8: Unable to execute query (MySQL specific)

2017-12-30 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=379987 --- Comment #10 from caulier.gil...@gmail.com --- I'm not sure to understand all. You use Mysql (or Mariadb) on your host computer (not in a remote one), but connected to digiKam as a remote one. Right ? If yes, this is why Maik talk about locahost ad

[digikam] [Bug 379987] UpdateSchemaFromV7ToV8: Unable to execute query (MySQL specific)

2017-12-30 Thread Quincy
https://bugs.kde.org/show_bug.cgi?id=379987 --- Comment #9 from Quincy --- I'n not in a hurry given the raised points. A new image with localhost/socket support does not change things. @Maik: I already went for a more manual (and cumbersome) step-by-step approach to migrate V7->8: - doing the in

[digikam] [Bug 379987] UpdateSchemaFromV7ToV8: Unable to execute query (MySQL specific)

2017-12-30 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=379987 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment

[digikam] [Bug 379987] UpdateSchemaFromV7ToV8: Unable to execute query (MySQL specific)

2017-12-30 Thread Quincy
https://bugs.kde.org/show_bug.cgi?id=379987 --- Comment #7 from Quincy --- As Maik said the new version does not solve/change this bug, so I am wondering why Gilles has posted to try the appimage to especially this bug. At least I could test the upgrade from V8 to 9 with my manually "migrated" V

[digikam] [Bug 379987] UpdateSchemaFromV7ToV8: Unable to execute query (MySQL specific)

2017-12-29 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=379987 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #6 from Maik

[digikam] [Bug 379987] UpdateSchemaFromV7ToV8: Unable to execute query (MySQL specific)

2017-12-29 Thread Quincy
https://bugs.kde.org/show_bug.cgi?id=379987 --- Comment #5 from Quincy --- Wanted to check the new update capabilities, but was unfortunately stopped by bug #388345. -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 379987] UpdateSchemaFromV7ToV8: Unable to execute query (MySQL specific)

2017-12-18 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=379987 Maik Qualmann changed: What|Removed |Added CC||rech...@vlado-do.de --- Comment #4 from Maik Qu

[digikam] [Bug 379987] UpdateSchemaFromV7ToV8: Unable to execute query (MySQL specific)

2017-12-13 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=379987 --- Comment #3 from caulier.gil...@gmail.com --- With next 5.8.0 release Mysql support have been well improved and a lots of bugs fixed. Please test with pre release 5.8.0 bundles that we provide and give us a feedback https://files.kde.org/digikam/ T

[digikam] [Bug 379987] UpdateSchemaFromV7ToV8: Unable to execute query (MySQL specific)

2017-10-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=379987 se...@pdmi.ras.ru changed: What|Removed |Added CC||se...@pdmi.ras.ru --- Comment #2 from se...@

[digikam] [Bug 379987] UpdateSchemaFromV7ToV8: Unable to execute query (MySQL specific)

2017-08-23 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=379987 Maik Qualmann changed: What|Removed |Added CC||ogkara...@mailbox.org --- Comment #1 from Maik