[opensuse-kde] Digikam database migration sqlite -> mysql fails
This was originally asked on opensuse@opensuse.org but got no responses, so I'm trying the KDE list. Hi all. I'm hoping someone else may have come across this and found a solution. I wanted to convert my digikam setup from sqlite to mysql. Digikam includes a database migration tool so I; -Set up a user for digikam in mysql -Created 2 empty databases as required by digikam (one called digikam, one called thumbnails) -Granted global priveleges to the digikam user (UGLY! but it won't work otherwise - digikam complains that "CREATE TRIGGER" priveleges are not granted if you only grant database-level privleges) :-( -Configured digikam to talk to the correct mysql database -Clicked on "Test DB Connection" in Digikam and got "Database connection test successful". So far so good. Unfortunately, when trying to use the database migration tool, I get the an error message: "Error while creating the database schema". Go into mysql and confirm that "show tables;" in each database returns an empty result, so nothing has been created in the databases. OK, maybe digikam wants to create the databases itself..."drop database <dbname>;" - digikam then complains "Error opening target database". Recreate the databases, double check priveleges, still the same result. Running Digikam 2.3.0, KDE 4.6.5 on oS 11.4 with mysql 5.1.53. Has anyone gotten this to work recently? TIA, Rodney. PS There is an open bug for this - according to the bug report it was supposed to have been fixed in 2.0.0 (the bug was raised against 1.9.5) but it seems not to be fixed...it is also reported to work with Ubuntu but to be broken in Fedora and, it seems, oS. Perhaps there is something not correctly packaged... -- =================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au =================================================== -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Thursday 19 January 2012 13:36:33 Rodney Baker wrote:
This was originally asked on opensuse@opensuse.org but got no responses, so I'm trying the KDE list.
Hi all. I'm hoping someone else may have come across this and found a solution. I wanted to convert my digikam setup from sqlite to mysql. Digikam includes a database migration tool so I;
<snip>
Has anyone gotten this to work recently?
I would try turning on debugging (using kdebugdialog) then run digikam from the command line and try again, see if a more specific error is output.
PS There is an open bug for this - according to the bug report it was supposed to have been fixed in 2.0.0 (the bug was raised against 1.9.5) but it seems not to be fixed...it is also reported to work with Ubuntu but to be broken in Fedora and, it seems, oS. Perhaps there is something not correctly packaged...
What is the bug URL? Will -- Will Stephenson | openSUSE Board, openSUSE Boosters Team, KDE Developer SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On 01/19/2012 11:08 AM, Will Stephenson wrote:
On Thursday 19 January 2012 13:36:33 Rodney Baker wrote:
This was originally asked on opensuse@opensuse.org but got no responses, so I'm trying the KDE list.
Hi all. I'm hoping someone else may have come across this and found a solution. I wanted to convert my digikam setup from sqlite to mysql. Digikam includes a database migration tool so I;
<snip>
Has anyone gotten this to work recently?
I would try turning on debugging (using kdebugdialog) then run digikam from the command line and try again, see if a more specific error is output.
PS There is an open bug for this - according to the bug report it was supposed to have been fixed in 2.0.0 (the bug was raised against 1.9.5) but it seems not to be fixed...it is also reported to work with Ubuntu but to be broken in Fedora and, it seems, oS. Perhaps there is something not correctly packaged...
What is the bug URL?
Will
-- Will Stephenson | openSUSE Board, openSUSE Boosters Team, KDE Developer SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany
Will https://bugs.kde.org/show_bug.cgi?id=235928 & https://bugs.kde.org/show_bug.cgi?id=262321 My fixes for that was drop the use of digikam :-( -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Ambassador GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Freitag, 20. Januar 2012, 09:33:31 schrieb Bruno Friedmann:
That one is considered as fixed with 2.0. So you would have to re-open it if it still applies. Sven -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Thu, 19 Jan 2012 20:38:41 Will Stephenson wrote:
On Thursday 19 January 2012 13:36:33 Rodney Baker wrote:
This was originally asked on opensuse@opensuse.org but got no responses, so I'm trying the KDE list.
Hi all. I'm hoping someone else may have come across this and found a solution. I wanted to convert my digikam setup from sqlite to mysql. Digikam includes a database migration tool so I;
<snip>
Has anyone gotten this to work recently?
I would try turning on debugging (using kdebugdialog) then run digikam from the command line and try again, see if a more specific error is output.
PS There is an open bug for this - according to the bug report it was supposed to have been fixed in 2.0.0 (the bug was raised against 1.9.5) but it seems not to be fixed...it is also reported to work with Ubuntu but to be broken in Fedora and, it seems, oS. Perhaps there is something not correctly packaged...
What is the bug URL?
Will
Sorry for the delay in answering, Will, and thanks for your interest. I haven't had time yet to get back to this, but I will try to get to it in the next day or two. It would be good to get this resolved once and for all, if it is in fact a definite bug (rather than just a misconfigured/missing package on my system somehow). Regards, Rdoney. -- =================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au =================================================== -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Thu, 19 Jan 2012 20:38:41 Will Stephenson wrote:
On Thursday 19 January 2012 13:36:33 Rodney Baker wrote:
This was originally asked on opensuse@opensuse.org but got no responses, so I'm trying the KDE list.
Hi all. I'm hoping someone else may have come across this and found a solution. I wanted to convert my digikam setup from sqlite to mysql. Digikam includes a database migration tool so I;
<snip>
Has anyone gotten this to work recently?
I would try turning on debugging (using kdebugdialog) then run digikam from the command line and try again, see if a more specific error is output.
OK, found this (sorry about the line wrap): digikam(13542)/kdeui (KNotification) KNotificationManager::close: 204 QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in use, all queries will cease to work. Note: The above message appears immediately after pressing the "Check DB Connection" button. Subsequently, queries fail. digikam(13542)/digikam (core) Digikam::SchemaUpdater::update: SchemaUpdater update digikam(13542)/digikam (core) Digikam::DatabaseCoreBackend::prepareQuery: Prepare failed! digikam(13542)/digikam (core) Digikam::DatabaseCoreBackendPrivate::debugOutputFailedQuery: Failure executing query: "SELECT value FROM Settings WHERE keyword=?;" Error messages: "QMYSQL3: Unable to prepare statement" "Table 'digikam.Settings' doesn't exist" 1146 2 Well, of course it doesn't! You haven't created it yet! We started with an empty database! Bound values: () digikam(13542)/digikam (core) Digikam::DatabaseCoreBackendPrivate::debugOutputFailedQuery: Failure executing query: "SELECT value FROM Settings WHERE keyword='DBVersion';" Error messages: "QMYSQL: Unable to execute query" "Table 'digikam.Settings' doesn't exist" 1146 2 Bound values: (QVariant(QString, "DBVersion") ) digikam(13542)/digikam (core) Digikam::DatabaseCoreBackend::prepareQuery: Prepare failed! digikam(13542)/digikam (core) Digikam::DatabaseCoreBackendPrivate::debugOutputFailedQuery: Failure executing query: "SELECT value FROM Settings WHERE keyword=?;" Error messages: "QMYSQL3: Unable to prepare statement" "Table 'digikam.Settings' doesn't exist" 1146 2 Bound values: () digikam(13542)/digikam (core) Digikam::DatabaseCoreBackendPrivate::debugOutputFailedQuery: Failure executing query: "SELECT value FROM Settings WHERE keyword='DBVersionRequired';" Error messages: "QMYSQL: Unable to execute query" "Table 'digikam.Settings' doesn't exist" 1146 2 Bound values: (QVariant(QString, "DBVersionRequired") ) digikam(13542)/digikam (core) Digikam::SchemaUpdater::startUpdates: Have a database structure version 0 digikam(13542)/digikam (core): DBVersion not available! Giving up schema upgrading. It isn't supposed to be upgrading the Schema - it's supposed to be creating it! digikam(13542)/kdeui (KNotification) KNotificationManager::notificationClosed: 209 Hmmm - not sure what I'm doing wrong here (if anything)... -- =================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au =================================================== -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Thu, 19 Jan 2012 20:38:41 Will Stephenson wrote:
On Thursday 19 January 2012 13:36:33 Rodney Baker wrote:
This was originally asked on opensuse@opensuse.org but got no responses, so I'm trying the KDE list.
Hi all. I'm hoping someone else may have come across this and found a solution. I wanted to convert my digikam setup from sqlite to mysql. Digikam includes a database migration tool so I;
<snip>
Has anyone gotten this to work recently?
I would try turning on debugging (using kdebugdialog) then run digikam from the command line and try again, see if a more specific error is output.
PS There is an open bug for this - according to the bug report it was supposed to have been fixed in 2.0.0 (the bug was raised against 1.9.5) but it seems not to be fixed...it is also reported to work with Ubuntu but to be broken in Fedora and, it seems, oS. Perhaps there is something not correctly packaged...
What is the bug URL?
Will
https://bugs.kde.org/show_bug.cgi?id=280678 -- =================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au =================================================== -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Sun, 22 Jan 2012 00:23:56 +1030, Rodney Baker <rodney.baker@iinet.net.au> wrote:
On Thu, 19 Jan 2012 20:38:41 Will Stephenson wrote:
On Thursday 19 January 2012 13:36:33 Rodney Baker wrote:
This was originally asked on opensuse@opensuse.org but got no responses, so I'm trying the KDE list.
Hi all. I'm hoping someone else may have come across this and found a solution. I wanted to convert my digikam setup from sqlite to mysql. Digikam includes a database migration tool so I;
<snip>
Has anyone gotten this to work recently?
I would try turning on debugging (using kdebugdialog) then run digikam from the command line and try again, see if a more specific error is output.
PS There is an open bug for this - according to the bug report it was supposed to have been fixed in 2.0.0 (the bug was raised against 1.9.5) but it seems not to be fixed...it is also reported to work with Ubuntu but to be broken in Fedora and, it seems, oS. Perhaps there is something not correctly packaged...
What is the bug URL?
Will
https://bugs.kde.org/show_bug.cgi?id=280678
-- =================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au ===================================================
.cgi?id=280678
-- =================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au ===================================================
.cgi?id=280678
-- =================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au ===================================================
digiKam Software Collection 2.5.0 Its released. - http://www.digikam.org/drupal/node/638 - https://projects.kde.org/projects/extragear/graphics/digikam/repository/revi... Glenn -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Sun, 22 Jan 2012 01:33:08 doiggl@velocitynet.com.au wrote:
digiKam Software Collection 2.5.0 Its released.
- http://www.digikam.org/drupal/node/638 - https://projects.kde.org/projects/extragear/graphics/digikam/repository/rev isions/master/entry/project/NEWS.2.5.0 Glenn
Yes, but this isn't fixed! I just upgraded to the latest git source and built it (after sourcing all the dependencies) which builds as 2.6.0 - the exact same behaviour is observed. :-( -- =================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au =================================================== -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
participants (5)
-
Bruno Friedmann -
doiggl＠velocitynet.com.au -
Rodney Baker -
Sven Burmeister -
Will Stephenson