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

[Marcel Wiesweg]

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





--- Comment #59 from Marcel Wiesweg <marcel wiesweg gmx de>  2010-06-12 16:05:39 ---
There is a bug with the command line option, see fix.

What does "start with no database" mean? When you start with an empty config,
the first run wizard should appear.

--
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 #59 from Marcel Wiesweg <marcel wiesweg gmx de>  2010-06-12 16:05:39 ---
There is a bug with the command line option, see fix.

What does "start with no database" mean? When you start with an empty config,
the first run wizard should appear.

--- Comment #60 from Marcel Wiesweg <marcel wiesweg gmx de>  2010-06-12 16:05:42 ---
SVN commit 1137359 by mwiesweg:

Fix reading db file from command line

CCBUG: 235928

 M  +3 -3      main.cpp  


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

--
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 #61 from Dany <dany natzo com>  2010-06-12 21:50:23 ---
I was not getting the wizard at all. I went ahead and deleted digikamrc and now
I get the wizard again.

Regarding the fix for the command line bug. Can I just use the mentioned file
with the 1.3.0 release (not SVN) ?

--
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 #62 from Dany <dany natzo com>  2010-06-13 09:05:43 ---
Recompiled SVN version and can now open my database from command line. Thank
you for the suggestions.

--
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


Bruno Friedmann <[hidden email]> changed:

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




--- Comment #63 from Bruno Friedmann <brunofr ioda net>  2010-08-01 11:13:48 ---
Info about digikam rpm :
Repository: @System
Name: digikam
Version: 1.3.0-41.1
Arch: i586
Vendor: obs://build.opensuse.org/KDE
Installed: Yes
Status: up-to-date
Installed Size: 15.5 MiB
Summary: A KDE Photo Manager

Context : in a project to store and work with ~1500000 photos we have to use
mysql (several computers need access to the same db)
Those mysql server is up and running a user exist and have all rights to it's
digikam db.
(All works with akonadi and amarok)

What steps will reproduce the problem?

1. Open digikam 1.3.1, and try to setup the use of mysql

2. Mysql is setup to use innodb engine by default ( necessary for akonadi ) and
also the digikam database ( triggers )

3. digikam stop  with the error of unable to write table : this is due to the
use of string in index without limiting them to a max of 255

4. I've not found how can I pre setup the digikam to directly use the mysql
before indexing my folders.

5. We try to correct manually the qsql instruction as you wrongly use string
index that are more than 255 and this is not supported by innodb.

What is the actual output?
lot's of error

What is the expected output?
a smooth working database.

Even trying to use the mysql embedded server ...

(23291) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]
(23291) Digikam::DatabaseConfigElementLoader::readConfig:
"/usr/share/kde4/apps/digikam/database/dbconfig.xml"
(23291) Digikam::DatabaseParameters::defaultParameters: ConnectOptions
"UNIX_SOCKET=/home/bruno/.kde4/share/apps/digikam/db_misc/mysql.socket"
(23291) Digikam::DatabaseServer::startMYSQLDatabaseProcess: Failed to use
database "digikam"
(23291) Digikam::DatabaseServer::startMYSQLDatabaseProcess: Query error:
"Unknown database 'digikam' QMYSQL: Unable to execute query"
(23291) Digikam::DatabaseServer::startMYSQLDatabaseProcess: Database error:
"Can't connect to local MySQL server through socket
'/home/bruno/.kde4/share/apps/digikam/db_misc/mysql.socket' (2) QMYSQL: Unable
to connect"
(23291) Digikam::DatabaseServer::startMYSQLDatabaseProcess: Trying to create
database now...
(23291) Digikam::DatabaseServer::startMYSQLDatabaseProcess: Database was
successfully created
QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in
use, all queries will cease to work.
(23291) Digikam::PollThread::checkDigikamInstancesRunning: At least service [
"org.kde.digikam.KIO-digikamtags-20202" ] is using the database server
(23291) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]
QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in
use, all queries will cease to work.
QSqlDatabasePrivate::removeDatabase: connection 'digikamDatabase-139614608' is
still in use, all queries will cease to work.
QSqlDatabasePrivate::addDatabase: duplicate connection name
'digikamDatabase-139614608', old connection removed.
digikam(20046)/digikam (core): Error while opening the database. Error details
[ QSqlError(-1, "Erreur lors de l'ouverture de la base de données", "unable to
open database file") ]
digikam(20046)/digikam (core): Error while opening the database. Error details
[ QSqlError(-1, "Erreur lors de l'ouverture de la base de données", "unable to
open database file") ]
digikam(20046)/digikam (core): Error while opening the database. Error details
[ QSqlError(-1, "Erreur lors de l'ouverture de la base de données", "unable to
open database file") ]
digikam(20046)/digikam (core): Error while opening the database. Error details
[ QSqlError(-1, "Erreur lors de l'ouverture de la base de données", "unable to
open database file") ]
digikam(20046)/digikam (core): Error while opening the database. Error details
[ QSqlError(-1, "Erreur lors de l'ouverture de la base de données", "unable to
open database file") ]
digikam(20046)/digikam (core): Error while opening the database. Error details
[ QSqlError(-1, "Erreur lors de l'ouverture de la base de données", "unable to
open database file") ]
digikam(20046)/digikam (core): Error while opening the database. Error details
[ QSqlError(-1, "Erreur lors de l'ouverture de la base de données", "unable to
open database file") ]
digikam(20046)/digikam (core): Error while opening the database. Error details
[ QSqlError(-1, "Erreur lors de l'ouverture de la base de données", "unable to
open database file") ]
(23291) Digikam::PollThread::checkDigikamInstancesRunning: At least service [
"org.kde.digikam.KIO-digikamtags-20202" ] is using the database server
(23291) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]
digikam(20046)/digikam (core): Error while opening the database. Error details
[ QSqlError(-1, "Erreur lors de l'ouverture de la base de données", "unable to
open database file") ]


What version of the product are you using? On what target Application (e.g.
Firefox 3.5.1, etc.)? On what operating system?
Extension Version =
Application =
OS =

Please provide any additional information below. In some cases
errors/warnings may be logged in the Error Console (in Firefox) which is
available under the Tools menu or using Ctrl+Shift+J. If you find any
related to this extension, please report that too.

Also our global mysql configuration is utf-8 as we have picture name coming
from several countries which are not latin1

our modified xml.

None of the triggers actually works with a mysql 5.1.46

--
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 #64 from Bruno Friedmann <brunofr ioda net>  2010-08-01 11:20:07 ---
Created an attachment (id=49725)
 --> (http://bugs.kde.org/attachment.cgi?id=49725)
Modified xml to reduce index string to 254

each instruction run by hand on mysql console work.

none of the triggers works for the moment syntax error on 5.1.46 mysql server.

Have commented thumbnail setting as settings table already exist.

--
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 #65 from Marcel Wiesweg <marcel wiesweg gmx de>  2010-08-02 09:56:15 ---
Holger needs to have a look at that one. He's CC'ed.

--
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 #66 from Quallenauge <Hamsi2k freenet de>  2010-08-03 12:36:54 ---
Hi,

We should split up the problems on external and internal database here.
I also get an error when I try to use an internal database, which is not sql
statement related.

I suggest to investigate the case, when using an external DB.

Can you give some more information about the following points:

>4. I've not found how can I pre setup the digikam to directly use the mysql
before indexing my folders.

What do you mean here in detail?

>none of the triggers works for the moment syntax error on 5.1.46 mysql server.

I have looked at the mysql-global.conf file (which is used by the internal
started dbms) and found a comment from me, that some functions (triggers) are
not working with innodb. Maybe you have an suggestion how to make it
compatible? Can you provide the error messages?

--
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 #67 from Marcel Wiesweg <marcel wiesweg gmx de>  2010-08-04 12:10:25 ---

> >4. I've not found how can I pre setup the digikam to directly use the mysql
> before indexing my folders.
>
> What do you mean here in detail?

I think the problem is that the first-run wizard always sets up SQLite, without
an option to choose MySQL from the beginning. So your files will first be
indexes into SQLite. This can and will be fixed, but I think it's a minor
problem because the information will be copied on migration, so no need to
re-index the whole collection.

--
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

[km]

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


km <[hidden email]> changed:

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




--- Comment #68 from km <kmm riseup net>  2010-08-20 03:25:29 ---
I still have this problem with mysql (internal server) after upgrade from 1.2

--
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 #69 from Gilles Caulier <caulier gilles gmail com>  2010-08-20 08:37:40 ---
Install digiKam 1.3.0 release and try again

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

[km]

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





--- Comment #70 from km <kmm riseup net>  2010-08-27 13:57:46 ---
still the same with digikam 1.4

--
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 #71 from Quallenauge <Hamsi2k freenet de>  2010-09-15 11:45:02 ---
I've checked in some changes related to this
problem into the gsoc branch.

Can you please try if this fixes the problem with the following steps:

Delete your (internal) digikam database files
rm ~/.kde4/share/apps/digikam/db*
rm ~/.kde4/share/apps/digikam/mysql*

Then modify the database template which is located on
/usr/share/apps/digikam/database/mysql-global.conf
and enabled the following setting:
#default_storage_engine=innodb

After that switch to the internal mysql method
via config dialog and see if it works.

If this is also true for you, we can enable it as default.

--
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 #72 from Gilles Caulier <caulier gilles gmail com>  2010-10-06 15:25:02 ---
Gandalf,

Do you see comment #71 ?

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

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





--- Comment #73 from Bruno Friedmann <brunofr ioda net>  2010-10-07 09:40:02 ---
Tested today with digikam 1.4.0.4 opensuse 11.3 / mysql-comunity 5.1.46
innodb as default engine
Result = failed during migration 7%

digikam
QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in
use, all queries will cease to work.
Time elapsed: 176 ms
Time elapsed: 2 ms
Model: Time elapsed: 311 ms
TextureColorizer: Time elapsed: 100 ms
Time elapsed: 2 ms
Time elapsed: 2 ms
Model: Time elapsed: 10 ms
(7726) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]
(7726) Digikam::DatabaseConfigElementLoader::readConfig:
"/usr/share/kde4/apps/digikam/database/dbconfig.xml"
(7726) Digikam::DatabaseParameters::defaultParameters: ConnectOptions
"UNIX_SOCKET=/home/bruno/.kde4/share/apps/digikam/db_misc/mysql.socket"
(7726) Digikam::DatabaseServer::startMYSQLDatabaseProcess: Failed to use
database "digikam"
(7726) Digikam::DatabaseServer::startMYSQLDatabaseProcess: Query error:
"Unknown database 'digikam' QMYSQL: Unable to execute query"
(7726) Digikam::DatabaseServer::startMYSQLDatabaseProcess: Database error:
"Can't connect to local MySQL server through socket
'/home/bruno/.kde4/share/apps/digikam/db_misc/mysql.socket' (2) QMYSQL: Unable
to connect"
(7726) Digikam::DatabaseServer::startMYSQLDatabaseProcess: Trying to create
database now...
(7726) Digikam::DatabaseServer::startMYSQLDatabaseProcess: Database was
successfully created
QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in
use, all queries will cease to work.
(7726) Digikam::PollThread::checkDigikamInstancesRunning: At least service [
"org.kde.digikam.KIO-digikamtags-7140" ] is using the database server
(7726) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]
QSqlDatabasePrivate::removeDatabase: connection 'MigrationToDatabase182567520'
is still in use, all queries will cease to work.
QSqlQuery::prepare: empty query
(7726) Digikam::PollThread::checkDigikamInstancesRunning: At least service [
"org.kde.digikam.KIO-digikamtags-7140" ] is using the database server
(7726) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]
(7726) Digikam::PollThread::checkDigikamInstancesRunning: At least service [
"org.kde.digikam.KIO-digikamtags-7140" ] is using the database server
(7726) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]
(7726) Digikam::PollThread::checkDigikamInstancesRunning: At least service [
"org.kde.digikam.KIO-digikamtags-7140" ] is using the database server
(7726) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]
(7726) Digikam::PollThread::checkDigikamInstancesRunning: At least service [
"org.kde.digikam.KIO-digikamtags-7140" ] is using the database server
(7726) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]
(7726) Digikam::PollThread::checkDigikamInstancesRunning: At least service [
"org.kde.digikam.KIO-digikamtags-7140" ] is using the database server
(7726) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]
(7726) Digikam::PollThread::checkDigikamInstancesRunning: At least service [
"org.kde.digikam.KIO-digikamtags-7140" ] is using the database server
(7726) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]
QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in
use, all queries will cease to work.
QSqlDatabasePrivate::removeDatabase: connection 'MigrationToDatabase182567520'
is still in use, all queries will cease to work.
QSqlQuery::prepare: empty query
(7726) Digikam::PollThread::checkDigikamInstancesRunning: At least service [
"org.kde.digikam.KIO-digikamtags-7140" ] is using the database server
(7726) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]
(7726) Digikam::PollThread::checkDigikamInstancesRunning: At least service [
"org.kde.digikam.KIO-digikamtags-7140" ] is using the database server
(7726) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]
QSqlDatabasePrivate::removeDatabase: connection 'MigrationToDatabase182567520'
is still in use, all queries will cease to work.
QSqlQuery::prepare: empty query
(7726) Digikam::PollThread::checkDigikamInstancesRunning: At least service [
"org.kde.digikam.KIO-digikamtags-7140" ] is using the database server
(7726) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]
(7726) Digikam::PollThread::checkDigikamInstancesRunning: At least service [
"org.kde.digikam.KIO-digikamtags-7140" ] is using the database server
(7726) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]
(7726) Digikam::PollThread::checkDigikamInstancesRunning: At least service [
"org.kde.digikam.KIO-digikamtags-7140" ] is using the database server
(7726) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]
(7726) Digikam::PollThread::checkDigikamInstancesRunning: At least service [
"org.kde.digikam.KIO-digikamtags-7140" ] is using the database server
(7726) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]
(7726) Digikam::PollThread::checkDigikamInstancesRunning: At least service [
"org.kde.digikam.KIO-digikamtags-7140" ] is using the database server
(7726) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]
QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in
use, all queries will cease to work.
QSqlDatabasePrivate::removeDatabase: connection 'MigrationToDatabase182567520'
is still in use, all queries will cease to work.
QSqlQuery::prepare: empty query
(7726) Digikam::PollThread::checkDigikamInstancesRunning: At least service [
"org.kde.digikam.KIO-digikamtags-7140" ] is using the database server
(7726) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]
(7726) Digikam::PollThread::checkDigikamInstancesRunning: At least service [
"org.kde.digikam.KIO-digikamtags-7140" ] is using the database server
(7726) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]
(7726) Digikam::PollThread::checkDigikamInstancesRunning: At least service [
"org.kde.digikam.KIO-digikamtags-7140" ] is using the database server
(7726) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]
(7726) Digikam::PollThread::checkDigikamInstancesRunning: At least service [
"org.kde.digikam.KIO-digikamtags-7140" ] is using the database server
(7726) Digikam::PollThread::run: Waiting  10  seconds...stop: [ false ]

Also tried with the non-embeded server
only the albumroots table is created.

cause : indexes for innodb are too long ... picked from dbconfig.xml

mysql> CREATE TABLE Albums
    ->                             (id INTEGER PRIMARY KEY NOT NULL
AUTO_INCREMENT,
    ->                             albumRoot INTEGER NOT NULL,
    ->                             relativePath LONGTEXT CHARACTER SET utf8 NOT
NULL,
    ->                             date DATE,
    ->                             caption LONGTEXT CHARACTER SET utf8,
    ->                             collection LONGTEXT CHARACTER SET utf8,
    ->                             icon INTEGER,
    ->                             UNIQUE(albumRoot, relativePath(332)));
ERROR 1071 (42000): Specified key was too long; max key length is 767 bytes

with the modified dbconfig.xml
(change all 332 & 333 index length to 254, migration works.)

But going to configuration, and setting digikam to use the migrated database
failed immediately with a table creation error ...
Why creation tables if they already exist and contain data ... ( checked with
mysql tools )

--
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 #74 from Gandalf Lechner <gandalf lechner univie ac at>  2010-10-08 09:48:55 ---
(In reply to comment #72)
> Gandalf,
>
> Do you see comment #71 ?
>
> Gilles Caulier

For me, this problem has long since disappeared - see #44.

Gandalf

--
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 #75 from Gilles Caulier <caulier gilles gmail com>  2010-10-08 10:08:58 ---
Marcel, Quallenauge,

Can this file can be closed, or it still some pending investiguations to do ?

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 #76 from Marcel Wiesweg <marcel wiesweg gmx de>  2010-10-09 12:25:23 ---
I'd say there are still problems with InnoDB, but I'm not familiar with that
stuff.

--
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 #77 from Bruno Friedmann <brunofr ioda net>  2010-10-09 13:51:11 ---
For the innodb creation, the trouble is only due to the use of big varchar
index
(332 or 333 length ) and should be limited to 254

see my comment #73

--
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 #78 from Quallenauge <Hamsi2k freenet de>  2010-10-09 20:29:55 ---
I made some patches in gsoc branch:

- limit all table index length to 254
- added a fix which prevents the interbal database server from closing while
  the db is created

For me it's working both the internal database server
and also a external mysql dbms which defaults to the InnoDB backend when a
table is created.

Can you please try the gsoc branch? In case that it is working, I'm willing to
transfer the changes to the trunk.

--
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