[Digikam-devel] [Bug 267733] Automatical initialisation of Internal MySQL database doesn't work after digikam start

Francesco Riosa francesco+kde at pnpitalia.it
Mon May 9 19:27:17 BST 2011


--- Comment #6 from Francesco Riosa <francesco+kde pnpitalia it>  2011-05-09 20:27:16 ---
(In reply to comment #5)
> Hi,
> I'm sorry if this is a redundant comment, i didn't really try out your patch
> (need a stable digikam on this machine) but I just want to make sure this
> really fixes the "database doesn't autostart" issue.

Work here for me, but would like to see other success/failure reports.

To test new this new script is possible to install digikam from sources as
user, leaving the system digikam stable, backup of ~/.kde* and digikam
databases is needed tough.

There is a small guide in
would be very nice to see result of testing. Check 2.0 beta is running in the
help menu.

> What I mean is: this patch seems to address initialization/migration issues, or
> issues on recreating tables, but in this case the database works perfectly, it
> only seems that the mysqld binary is never actually invoked to act as a local
> server.

I've seen it invoked but failing initialization.

> Then, maybe it's just me not knowing enough of this SQL XML things, or probably
> this really fixes things, but better a doublecheck than overlooking things. :)

you're welcome

> I can obviously give more details if needed!

if it still fail more details will be needed, for example run `kdebugdialog`
and activate debug before starting, possibly also modifying mysql-global.conf
to include 

log-output = FILE
general_log = 1
general_log_file = $HOME/tmp/general_log.sql

$HOME/tmp MUST have sufficient permission for the database to write into it

Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the Digikam-devel mailing list