[Bug 235928] New: digikam fails to open database at startup

[Marcel Wiesweg]

https://bugs.kde.org/show_bug.cgi?id=235928





--- Comment #38 from Marcel Wiesweg <marcel wiesweg gmx de>  2010-05-13 15:44:41 ---
SVN commit 1126274 by mwiesweg:

Fix bug where logic was reverted.
As there is no such thing as a null QSqlQuery, pass only the query text
and the last error to the error handler.

CCBUG: 235928

 M  +5 -5      digikam/databaseguierrorhandler.cpp  
 M  +2 -2      digikam/databaseguierrorhandler.h  
 M  +3 -3      libs/database/databaseerrorhandler.h  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1126274

--- Comment #39 from Marcel Wiesweg <marcel wiesweg gmx de>  2010-05-13 15:44:42 ---
SVN commit 1126275 by mwiesweg:

Fix various bugs with SQL error handling:
For SQLite, there is no sense in trying to close database and reconnect. In
fact, the database
will open again, but remain locked in this case, so that all subsequent
statements fail.
Limit connection error handling to MySQL.
Restructure query error handling, reuse code.

CCBUG: 235928

 M  +62 -59    databasecorebackend.cpp  
 M  +10 -1     databasecorebackend.h  
 M  +8 -7      databasecorebackend_p.h  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1126275

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Marcel Wiesweg]

https://bugs.kde.org/show_bug.cgi?id=235928





--- Comment #38 from Marcel Wiesweg <marcel wiesweg gmx de>  2010-05-13 15:44:41 ---
SVN commit 1126274 by mwiesweg:

Fix bug where logic was reverted.
As there is no such thing as a null QSqlQuery, pass only the query text
and the last error to the error handler.

CCBUG: 235928

 M  +5 -5      digikam/databaseguierrorhandler.cpp  
 M  +2 -2      digikam/databaseguierrorhandler.h  
 M  +3 -3      libs/database/databaseerrorhandler.h  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1126274

--- Comment #39 from Marcel Wiesweg <marcel wiesweg gmx de>  2010-05-13 15:44:42 ---
SVN commit 1126275 by mwiesweg:

Fix various bugs with SQL error handling:
For SQLite, there is no sense in trying to close database and reconnect. In
fact, the database
will open again, but remain locked in this case, so that all subsequent
statements fail.
Limit connection error handling to MySQL.
Restructure query error handling, reuse code.

CCBUG: 235928

 M  +62 -59    databasecorebackend.cpp  
 M  +10 -1     databasecorebackend.h  
 M  +8 -7      databasecorebackend_p.h  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1126275

--- Comment #40 from Marcel Wiesweg <marcel wiesweg gmx de>  2010-05-13 15:44:46 ---
SVN commit 1126276 by mwiesweg:

When a new tag was added by TagsCache, invalidate the internal cache.
When a transaction is active, the TagChangeset may arrive only later;
but we know that the tag was changed.
(this was the original SQL error that caused, though itself no problem,
 a lot of problems due to broken error handling in 235928)

CCBUG: 235928

 M  +8 -0      tagscache.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1126276

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Marcel Wiesweg]

https://bugs.kde.org/show_bug.cgi?id=235928


Marcel Wiesweg <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]




--- Comment #41 from Marcel Wiesweg <marcel wiesweg gmx de>  2010-05-13 15:50:28 ---
For me, the situation of a fresh installation with SQlite works now.

There are a few scenarios which I cannot easily test, like upgrading from <=
0.9, upgrading from 1.0/1.1/1.2.
Especially when upgrading from 0.9, a config key ("Album Path") has been
deleted by previous 1.3-svn which is needed by the SchemaUpdater. Julien's
problem may be related.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

https://bugs.kde.org/show_bug.cgi?id=235928





--- Comment #42 from Gilles Caulier <caulier gilles gmail com>  2010-05-13 18:38:33 ---
Marcel,

I can confirm that SQlite support is fixed now. Thanks a lots.

I will test Mysql embeded now.

Gilles

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

["Jens Müller"]

https://bugs.kde.org/show_bug.cgi?id=235928





--- Comment #43 from Jens Mueller <tschenser gmx de>  2010-05-14 10:08:51 ---
Starting in a fresh environment works also for me now, thanks Marcel! But
upgrade from 1.2 is still broken, I get:

digikam(4028)/digikam (core) Digikam::AlbumManager::setDatabase:
DatabaseParameters: [ Type "QSQLITE", Name "/home/jens/Bilder" (Thumbnails Name
"/home/jens/Bilder/thumbnails-digikam.db"); ]
digikam(4028)/digikam (core): Error while opening the database. Error details [
QSqlError(-1, "Fehler beim Öffnen der Datenbank", "unable to open database
file") ]
digikam(4028)/digikam (core): Error while opening the database. Error details [
QSqlError(-1, "Fehler beim Öffnen der Datenbank", "unable to open database
file") ]
digikam(4028)/digikam (core): Error while opening the database. Error details [
QSqlError(-1, "Fehler beim Öffnen der Datenbank", "unable to open database
file") ]
digikam(4028)/digikam (core): Error while opening the database. Error details [
QSqlError(-1, "Fehler beim Öffnen der Datenbank", "unable to open database
file") ]
...

If I can help you in some way, let me know.

Regards, Jens

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

https://bugs.kde.org/show_bug.cgi?id=235928





--- Comment #44 from Gandalf Lechner <gandalf lechner univie ac at>  2010-05-14 10:36:45 ---
Also here starting from scratch works again :-)

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Marcel Wiesweg]

https://bugs.kde.org/show_bug.cgi?id=235928





--- Comment #45 from Marcel Wiesweg <marcel wiesweg gmx de>  2010-05-14 17:56:39 ---
Jens: Is your digikamrc file original from 1.2, or was it touched by
intermediate 1.3-svn versions? Can you post the [Database Settings] section?
Your db is /home/jens/Bilder/digikam4.db?

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

["Jens Müller"]

https://bugs.kde.org/show_bug.cgi?id=235928





--- Comment #46 from Jens Mueller <tschenser gmx de>  2010-05-14 19:02:54 ---
Created an attachment (id=43590)
 --> (http://bugs.kde.org/attachment.cgi?id=43590)
Digikam Config 1.2

Yes my db is in /home/jens/Bilder/ Just to be shure, I created a new config
file and a new database with version 1.2 and tried then the upgrade to current
1.3 with the same result.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Marcel Wiesweg]

https://bugs.kde.org/show_bug.cgi?id=235928





--- Comment #47 from Marcel Wiesweg <marcel wiesweg gmx de>  2010-05-15 17:52:48 ---
SVN commit 1127144 by mwiesweg:

Fix problem upgrading the digikamrc file from 1.2 to 1.3:

Separate out the logic to get the db file from a path for SQLite into static
methods.
The problem was that isSQLite() is false for a recently constructed argument,
when calling parametersForSQLite().

CCBUG: 235928

 M  +50 -29    databaseparameters.cpp  
 M  +5 -0      databaseparameters.h  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1127144

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Marcel Wiesweg]

https://bugs.kde.org/show_bug.cgi?id=235928





--- Comment #48 from Marcel Wiesweg <marcel wiesweg gmx de>  2010-05-15 18:45:42 ---
Jens, yes there was a bug, I think it works now.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

["Jens Müller"]

https://bugs.kde.org/show_bug.cgi?id=235928





--- Comment #49 from Jens Mueller <tschenser gmx de>  2010-05-15 20:37:27 ---
Yes Marcel, all visible problems are gone. I checked again upgrad and fresh
install. But database section from upgrade differs compared to fresh install.

Fresh install:
[Database Settings]
Database Connectoptions=
Database Hostname=
Database Name=/home/jens/Bilder/
Database Name Thumbnails=/home/jens/Bilder/
Database Password=
Database Port=-1
Database Type=QSQLITE
Database Username=
Internal Database Server=false


Upgrad:
[Database Settings]
Database Connectoptions=
Database Hostname=
Database Name=
Database Name Thumbnails=
Database Password=
Database Port=-1
Database Type=
Database Username=
Internal Database Server=false

Regards, Jens

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

https://bugs.kde.org/show_bug.cgi?id=235928





--- Comment #50 from Julien Narboux <Julien narboux fr>  2010-05-15 21:41:09 ---
Thanks Marcel,

I can confirm that update from 1.2.0 to 1.3.0svn worked !

Julien

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Marcel Wiesweg]

https://bugs.kde.org/show_bug.cgi?id=235928





--- Comment #51 from Marcel Wiesweg <marcel wiesweg gmx de>  2010-05-15 22:20:39 ---
SVN commit 1127196 by mwiesweg:

In main(), when we have the db params to use, write them to the config file.
This is needed for all first-run or upgrade situations.

CCBUG: 235928

 M  +2 -0      main.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1127196

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

["Jens Müller"]

https://bugs.kde.org/show_bug.cgi?id=235928





--- Comment #52 from Jens Mueller <tschenser gmx de>  2010-05-16 22:27:02 ---
I think everything is fine for me now (but have not tested mysql support)

Jens

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

https://bugs.kde.org/show_bug.cgi?id=235928





--- Comment #53 from Gilles Caulier <caulier gilles gmail com>  2010-05-17 08:55:47 ---
I will switch my computers to Mysql and report today.

Gilles

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

https://bugs.kde.org/show_bug.cgi?id=235928





--- Comment #54 from Gilles Caulier <caulier gilles gmail com>  2010-05-17 11:09:07 ---
Marcel,

This is my condition to switch from SQlite to MysSQL :

- Clean up all, no DB file, no config file.
- Start digiKam from scratch from First Run Assistant.
- Go imediatly to DB config pannel, and swith from SQLite to Internal MySQL.

Results and remarks :

1/ I press on "Check DB connection" button. Why i can see these message on the
console :

digikam(1396)/digikam (core) Digikam::SetupDatabase::readSettings: Comparing
comboboxentry on index [ 0 ] [ "QSQLITE" ] with [ "QSQLITE" ]                  
digikam(1396)/digikam (core) Digikam::SetupDatabase::readSettings: Comparing
comboboxentry on index [ 1 ] [ "QMYSQL" ] with [ "QSQLITE" ]                    
digikam(1396)/digikam (core) Digikam::DatabaseParameters::defaultParameters:
ConnectOptions
"UNIX_SOCKET=/home/gilles/.kde4/share/apps/digikam/db_misc/mysql.socket"        
(3959) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]        
(3959) Digikam::DatabaseConfigElementLoader::readConfig:
"/usr/share/apps/digikam/database/dbconfig.xml"                      
(3959) Digikam::DatabaseParameters::defaultParameters: ConnectOptions
"UNIX_SOCKET=/home/gilles/.kde4/share/apps/digikam/db_misc/mysql.socket"        
(3959) Digikam::DatabaseServer::startMYSQLDatabaseProcess: Failed to use
database "digikam"                                  
(3959) Digikam::DatabaseServer::startMYSQLDatabaseProcess: Query error:
"Unknown database 'digikam' QMYSQL: Unable to execute query"                    
(3959) Digikam::DatabaseServer::startMYSQLDatabaseProcess: Database error:
"Can't connect to local MySQL server through socket
'/home/gilles/.kde4/share/apps/digikam/db_misc/mysql.socket' (2) QMYSQL: Unable
to connect"                                  
(3959) Digikam::DatabaseServer::startMYSQLDatabaseProcess: Trying to create
database now...                                  
(3959) Digikam::DatabaseServer::startMYSQLDatabaseProcess: Database was
successfully created                                  
QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in
use, all queries will cease to work.            
(3959) Digikam::PollThread::checkDigikamInstancesRunning: At least service [
"org.kde.digikam.KIO-digikamtags-30762" ] is using the database server          
(3959) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]        
(3959) Digikam::PollThread::checkDigikamInstancesRunning: At least service [
"org.kde.digikam.KIO-digikamtags-30762" ] is using the database server          
(3959) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]        
(3959) Digikam::PollThread::checkDigikamInstancesRunning: At least service [
"org.kde.digikam.KIO-digikamtags-30762" ] is using the database server          
(3959) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]        
timeChanged                                                                    
void SunLocator::update()                                                      
timeChanged                                                                    
void SunLocator::update()                                                      
(3959) Digikam::PollThread::checkDigikamInstancesRunning: At least service [
"org.kde.digikam.KIO-digikamtags-30762" ] is using the database server          
(3959) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]        
(3959) Digikam::PollThread::checkDigikamInstancesRunning: At least service [
"org.kde.digikam.KIO-digikamtags-30762" ] is using the database server          
(3959) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]        
(3959) Digikam::PollThread::checkDigikamInstancesRunning: At least service [
"org.kde.digikam.KIO-digikamtags-30762" ] is using the database server          
(3959) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]        
(3959) Digikam::PollThread::checkDigikamInstancesRunning: At least service [
"org.kde.digikam.KIO-digikamtags-30762" ] is using the database server
(3959) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]
(3959) Digikam::PollThread::checkDigikamInstancesRunning: At least service [
"org.kde.digikam.KIO-digikamtags-30762" ] is using the database server
(3959) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]
(3959) Digikam::PollThread::checkDigikamInstancesRunning: At least service [
"org.kde.digikam.KIO-digikamtags-30762" ] is using the database server
(3959) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]
timeChanged
void SunLocator::update()
timeChanged
void SunLocator::update()
(3959) Digikam::PollThread::checkDigikamInstancesRunning: At least service [
"org.kde.digikam.KIO-digikamtags-30762" ] is using the database server
(3959) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]
(3959) Digikam::PollThread::checkDigikamInstancesRunning: At least service [
"org.kde.digikam.KIO-digikamtags-30762" ] is using the database server
(3959) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]
(3959) Digikam::PollThread::checkDigikamInstancesRunning: At least service [
"org.kde.digikam.KIO-digikamtags-30762" ] is using the database server
(3959) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]
(3959) Digikam::PollThread::checkDigikamInstancesRunning: At least service [
"org.kde.digikam.KIO-digikamtags-30762" ] is using the database server
(3959) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]
(3959) Digikam::PollThread::checkDigikamInstancesRunning: At least service [
"org.kde.digikam.KIO-digikamtags-30762" ] is using the database server
(3959) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]
(3959) Digikam::PollThread::checkDigikamInstancesRunning: At least service [
"org.kde.digikam.KIO-digikamtags-30762" ] is using the database server
(3959) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]
timeChanged
void SunLocator::update()
timeChanged
void SunLocator::update()
(3959) Digikam::PollThread::checkDigikamInstancesRunning: At least service [
"org.kde.digikam.KIO-digikamtags-30762" ] is using the database server
(3959) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]
(3959) Digikam::PollThread::checkDigikamInstancesRunning: At least service [
"org.kde.digikam.KIO-digikamtags-30762" ] is using the database server
(3959) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]
(3959) Digikam::PollThread::checkDigikamInstancesRunning: At least service [
"org.kde.digikam.KIO-digikamtags-30762" ] is using the database server
(3959) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]

Soemthing is wrong with this message : "Digikam::PollThread::run: Waiting  10
seconds...stop: [ false ]"

Note : this message continu to be printed on the console after than digiKam
instance is closed. It's relevant of digikamdatabaseserver.

[gilles@pc-caulier digikam]$ ps -ax |grep digikamdata
 3959 ?        Sl     0:00 /usr/lib/kde4/libexec/digikamdatabaseserver
[gilles@pc-caulier digikam]$

If i kill it, this message disappear.

2/ I press Ok button from DB config pannel. digiKam show Collection File paths
settings panel. Why ? digiKam is not able to take SQlite collection paths and
import it as well ?

3/ I set by hand the unique collection path (/mnt/data/photos) where DB files
are hosted. I press ok. Collection File paths settings panel still displayed
with the progress dialog starting to scan collection path. I think that
collection settings panel can be closed there. Progress dialog look fine.

4/ When Scanning is complete, all dialog are closed properly and focus go back
to icon view. On the console i can always seen :

(3959) Digikam::PollThread::checkDigikamInstancesRunning: At least service [
"org.kde.digikam.KIO-digikamtags-30762" ] is using the database server
(3959) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]
(3959) Digikam::PollThread::checkDigikamInstancesRunning: At least service [
"org.kde.digikam.KIO-digikamtags-30762" ] is using the database server
(3959) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]
(3959) Digikam::PollThread::checkDigikamInstancesRunning: At least service [
"org.kde.digikam.KIO-digikamtags-30762" ] is using the database server
(3959) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]
(3959) Digikam::PollThread::checkDigikamInstancesRunning: At least service [
"org.kde.digikam.KIO-digikamtags-30762" ] is using the database server
(3959) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]
(3959) Digikam::PollThread::checkDigikamInstancesRunning: At least service [
"org.kde.digikam.KIO-digikamtags-30762" ] is using the database server
(3959) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]
(3959) Digikam::PollThread::checkDigikamInstancesRunning: At least service [
"org.kde.digikam.KIO-digikamtags-30762" ] is using the database server
(3959) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]

Help/DB stats dialog show right information.
I can navigate through folder view, search tools, and other. It sound to work.

5/ I close digiKam. I can see these messages on the console :

(3959) Digikam::PollThread::checkDigikamInstancesRunning: At least service [
"org.kde.digikam.KIO-digikamtags-30762" ] is using the database server
(3959) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]
Model deleted: Marble::MarbleModel(0xa294350)
Deleting FileStorageWatcher
Model deleted: Marble::MarbleModel(0xbe56dd8)
Deleting FileStorageWatcher
QSqlDatabasePrivate::removeDatabase: connection 'digikamDatabase-156351760' is
still in use, all queries will cease to work.
QSqlDatabasePrivate::removeDatabase: connection 'digikamDatabase-214966704' is
still in use, all queries will cease to work.
QSqlDatabasePrivate::removeDatabase: connection 'thumbnailDatabase-214966704'
is still in use, all queries will cease to work.
(3959) Digikam::PollThread::checkDigikamInstancesRunning: At least service [
"org.kde.digikam.KIO-digikamtags-30762" ] is using the database server
(3959) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]
Error in my_thread_global_end(): 2 threads didn't exit
[gilles@pc-caulier digikam]$ (3959)
Digikam::PollThread::checkDigikamInstancesRunning: At least service [
"org.kde.digikam.KIO-digikamtags-30762" ] is using the database server
(3959) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]
(3959) Digikam::PollThread::checkDigikamInstancesRunning: At least service [
"org.kde.digikam.KIO-digikamtags-30762" ] is using the database server
(3959) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]

Something is wrong there ?

Gilles Caulier

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

https://bugs.kde.org/show_bug.cgi?id=235928





--- Comment #55 from Gilles Caulier <caulier gilles gmail com>  2010-05-17 11:16:09 ---
Marcel,

This is an other request from me. I'm sure that users will complain about in
the future. It's about internal MySQl settings panel which is inconsistent
against SQlite settings panel.

SQlite provide a way to setup DB files path independently that collection path.
By default MySQl settings use cached kde4 dir from user home dir :

~/.kde4/share/apps/digikam/db_misc/

I cannot set-up something like /mnt/data/database, hosted in a separate HDD
partition. This is important to not fill home dir with huge DB files. It's
better to have a way to configure MySQL files paths hosted in a separate
partition or a remote path mounted locally.

What do you think about ?

Gilles Caulier

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Marcel Wiesweg]

https://bugs.kde.org/show_bug.cgi?id=235928





--- Comment #56 from Marcel Wiesweg <marcel wiesweg gmx de>  2010-05-17 18:36:36 ---
For the debug message from the database server, I guess we can safely disable
it.

It seems most of the functionality is working.
I agree the migration process leaves room to polish, there are also these bugs
relevant:
- 233762 Provide reasonable defaults and help for the database settings page
- 233763 Changing to mysql with invalid settings is "possible"
- 233765 Ask for migration after changing database settings
- 233769 Inform about migration into existing database
- 233770 Error messages after changing to mysql

which have a "(Holger)" currently on my todo list ;-)

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Johannes Wienke-3]

https://bugs.kde.org/show_bug.cgi?id=235928





--- Comment #57 from Johannes Wienke <languitar semipol de>  2010-05-17 20:14:55 ---
"Bug 233549 [database] Stuck at saving new image" also needs to be fixed to my
mind as it is a major loss of functionality if someone else encounters this.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

https://bugs.kde.org/show_bug.cgi?id=235928


Dany <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]




--- Comment #58 from Dany <dany natzo com>  2010-06-12 09:11:14 ---
Upgraded to 1.3 release on ArchLinux. I get the same error when starting with
no database:

QSqlDatabase:  driver not loaded
QSqlDatabase: available drivers: QSQLITE QMYSQL3 QMYSQL QODBC3 QODBC QPSQL7
QPSQL
digikam(4263)/digikam (core): Error while opening the database. Error details [
QSqlError(-1, "Driver not loaded", "Driver not loaded") ]


Now if I use my regular command (digikam --database-directory
/media/PHOTOS/PHOTOS/Digikam/) to use the database and pictures located on my
external hard drive I get:

Digikam(4532)/digikam (core): The given database-directory does not exist or is
not readable. Ignoring.
QSqlDatabase:  driver not loaded
QSqlDatabase: available drivers: QSQLITE QMYSQL3 QMYSQL QODBC3 QODBC QPSQL7
QPSQL
digikam(4532)/digikam (core): Error while opening the database. Error details [
QSqlError(-1, "Driver not loaded", "Driver not loaded") ]
digikam(4532)/digikam (core): Error while opening the database. Error details [
QSqlError(-1, "Driver not loaded", "Driver not loaded") ]

There are both digikam4.db and thumbnails-digikam.db in the above directory.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel