[digikam] [Bug 388422] DBVersion setting does not exist

2020-05-20 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=388422

caulier.gil...@gmail.com changed:

   What|Removed |Added

   Version Fixed In||7.0.0

--- Comment #18 from caulier.gil...@gmail.com ---
Thanks for the feedback

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 388422] DBVersion setting does not exist

2020-05-20 Thread Marcel
https://bugs.kde.org/show_bug.cgi?id=388422

Marcel  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #17 from Marcel  ---
Problem came from the old MySQL Version from the NAS, that can not be updated
as it does offer a newer version and has no support for docker. This is not a
problem from Digikam, it is a problem from Zyxel.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 388422] DBVersion setting does not exist

2018-01-06 Thread Marcel
https://bugs.kde.org/show_bug.cgi?id=388422

--- Comment #16 from Marcel  ---
Created attachment 109703
  --> https://bugs.kde.org/attachment.cgi?id=109703=edit
Startup log of digikam 5.6 and 5.8

Here are different startup with different db's. With sqlite both versions work
fine. With local MySql I get on both a similar error. With Server MySql I get
the same error but I'm not able to start digikam 5.8 any more. Digikam 5.6 can
be started with an invalid db so the db can be changed again.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 388422] DBVersion setting does not exist

2018-01-04 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=388422

--- Comment #15 from Maik Qualmann  ---
If I look at the log of comment 7, something seems to be missing at the
beginning. Can you create a new log, the beginning is important. I expect
something like this:

digikam.general: AlbumWatch use QFileSystemWatcher
digikam.general: Database Parameters:
   Type: "QMYSQL"
   DB Core Name: "digikam"
   DB Thumbs Name:   "digikam"
   DB Face Name: "digikam"
   Connect Options:  ""
   Host Name:"localhost"
   Host port:3306
   Internal Server:  false
   Internal Server Path: ""
   Internal Server Serv Cmd: ""
   Internal Server Init Cmd: ""
   Username: "maik"
   Password: ""

digikam.dbengine: Loading SQL code from config file
"/usr/share/digikam/database/dbconfig.xml"
digikam.dbengine: Checking XML version ID => expected:  3  found:  3
digikam.coredb: Core database: running schema update
digikam.coredb: Core database: have a structure version  9
digikam.coredb: Core database: makeUpdates  9  to  9

Maik

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 388422] DBVersion setting does not exist

2018-01-04 Thread Marcel
https://bugs.kde.org/show_bug.cgi?id=388422

--- Comment #14 from Marcel  ---
The package libqt5sql5-mysql was already installed with the newest version
5.9.1+dfsg-10ubuntu1. 

Marcel

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 388422] DBVersion setting does not exist

2018-01-04 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=388422

--- Comment #13 from Maik Qualmann  ---
I think the package is called libqt5sql5-mysql under Ubuntu. Is it installed?

Maik

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 388422] DBVersion setting does not exist

2018-01-03 Thread Marcel
https://bugs.kde.org/show_bug.cgi?id=388422

--- Comment #12 from Marcel  ---
How can I install or at least find out witch package is missing of Qt to
support MySQL?

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 388422] DBVersion setting does not exist

2018-01-02 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=388422

--- Comment #11 from caulier.gil...@gmail.com ---
I can confirm : Centos and Mageia have also switched to Mariadb.

Note : in my office where we have a ReadHat account, we recieve tips to let's
Mysql DB for huge data instead Mariadb. This last one has serious performance
problem with huge data storage (more than one Peta bytes by days).

By change, this is not same case with digiKam DB (:=)))...

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 388422] DBVersion setting does not exist

2018-01-02 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=388422

--- Comment #10 from Maik Qualmann  ---
The error message "QSqlDatabase: driver not loaded" usually indicates a missing
package of Qt to support MySQL.

Maik

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 388422] DBVersion setting does not exist

2018-01-02 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=388422

--- Comment #9 from Maik Qualmann  ---
The problem with the internal MySQL server is known, see bug 379959. MySQL has
removed the program "mysql_install_db" Can you test it with MariaDB? In future,
we will probably only support MariaDB. In my openSUSE is MySQL already removed.

Maik

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 388422] DBVersion setting does not exist

2018-01-02 Thread Marcel
https://bugs.kde.org/show_bug.cgi?id=388422

--- Comment #8 from Marcel  ---
No success with local mysql ether. I uploaded the terminal output and another
screenshot of the error. By the way I'm using ubuntu 17.10. Probably that is
the reason because mysql is not jet officially supported by this version

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 388422] DBVersion setting does not exist

2018-01-02 Thread Marcel
https://bugs.kde.org/show_bug.cgi?id=388422

--- Comment #7 from Marcel  ---
Created attachment 109623
  --> https://bugs.kde.org/attachment.cgi?id=109623=edit
Terminal output with digicam 5.8

Only line 2+3 are shown until the error occurs

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 388422] DBVersion setting does not exist

2018-01-02 Thread Marcel
https://bugs.kde.org/show_bug.cgi?id=388422

--- Comment #6 from Marcel  ---
Created attachment 109622
  --> https://bugs.kde.org/attachment.cgi?id=109622=edit
Error with use of local db

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 388422] DBVersion setting does not exist

2018-01-01 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=388422

--- Comment #5 from Maik Qualmann  ---
Is there another error message when you start digiKam in the console? Maybe try
and set up a local MySQL server?

Maik

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 388422] DBVersion setting does not exist

2018-01-01 Thread Marcel
https://bugs.kde.org/show_bug.cgi?id=388422

--- Comment #4 from Marcel  ---
Yes I have, otherwise the check connection would not be successful anyway. For
the SERVERADRESS I have used my IP address.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 388422] DBVersion setting does not exist

2018-01-01 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=388422

caulier.gil...@gmail.com changed:

   What|Removed |Added

  Component|Database|Database-Schema
 CC||caulier.gil...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 388422] DBVersion setting does not exist

2018-01-01 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=388422

--- Comment #3 from Maik Qualmann  ---
But you have replaced the variables USERNAME, PASSWORD or SERVERADRESS with the
settings that you have set in digiKam?

Maik

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 388422] DBVersion setting does not exist

2018-01-01 Thread Marcel
https://bugs.kde.org/show_bug.cgi?id=388422

--- Comment #2 from Marcel  ---
I tried the following: 
Created a new MySyl db with the given SQL orders for creation (@maik an
apostrophe is missing after USERNAME)
Used digikam version 5.8

The issue is the same with digikam 5.8. It does not even give the chance to
change the db by gui again. On the terminal is:
-- digiKam AppImage Bundle
-- Use 'help' as CLI argument to know all available options
digikam.coredb: Core database: cannot process schema initialization
QThreadStorage: Thread 0x7f6f4a349600 exited after QThreadStorage 11 destroyed

When I migrate the db the error "Error while creating the database schema." is
appearing. 

Same problem for 
'USERNAME@'SERVERADRESS';
"Check connection" returns successful

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 388422] DBVersion setting does not exist

2018-01-01 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=388422

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #1 from Maik Qualmann  ---
You can test the pre-release appImage from digiKam-5.8.0.

https://files.kde.org/digikam/

Many improvements to MySQL support have been added. The question is, however,
whether you have created the database with the appropriate rights? For example:

CREATE USER 'USERNAME'@'%' IDENTIFIED BY 'PASSWORD';
GRANT ALL ON *.* TO 'USERNAME'@'%' IDENTIFIED BY 'PASSWORD';
CREATE DATABASE digikam;
GRANT ALL PRIVILEGES ON digikam.* TO 'USERNAME@'%';
FLUSH PRIVILEGES;

Instead of:

'USERNAME@'%'

Maybe also:

'USERNAME@'SERVERADRESS';

Maik

-- 
You are receiving this mail because:
You are watching all bug changes.