<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">Hi Maik,</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Thank you very much for your fast
reply.</div>
<p>At the time that I installed Digikam a few weeks ago, 7.1.0 was
the release version. The 7.2.0 version on the site that you linked
is described as:</p>
<pre>```
IMPORTANT: these bundle files, are built weekly and can be used to test new features quickly.
Do not use these versions in production, unless you know what are you doing.
```
</pre>
<p>I guess after spending a few weeks merging in 50k+ media files,
I'm a bit nervous about using a bleeding edge version. In your
opinion, is the 7.2.0 release candidate stable enough for neophyte
end-users like myself?</p>
<p>Thanks for pointing out the debugging settings. I'll try that
tomorrow and post the results to the list.</p>
<p>Cheers,</p>
<p>~Tomer<br>
</p>
<pre></pre>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">On 2/7/21 10:53 PM, Maik Qualmann
wrote:<br>
</div>
<blockquote type="cite" cite="mid:2289609.dIE4cauaJ5@linux-tpgn">
<pre class="moz-quote-pre" wrap="">First of all, digiKam-7.1.0 is too old for MacOS. Use the current release
candidate digiKam-7.2.0-RC from here:
<a class="moz-txt-link-freetext" href="https://files.kde.org/digikam/">https://files.kde.org/digikam/</a>
Then we need the debug output from the terminal as described here, don't
forget to set the debug environment variable:
<a class="moz-txt-link-freetext" href="https://www.digikam.org/contribute/">https://www.digikam.org/contribute/</a>
Maik
Am Montag, 8. Februar 2021, 06:10:20 CET schrieb Tomer Altman:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">To the digikam community:
I hope that this finds you well. I am a new digikam user and have been
very happy using it to merge several large sets of photos & videos into
a single collection. Until now I have used the SQLite DB back-end, but
my intention has been to move on to using the external MySQL server DB
back-end to allow me to edit the collection from multiple machines.
I am using Digikam v.7.1.0
(commits.kde.org/digikam/d52927ebc98ee24c9fc3a3a34f527d4d21b09fb3) on
Mac OS X v10.13.6. I have been using the following documentation to
guide me:
<a class="moz-txt-link-freetext" href="https://docs.kde.org/trunk5/en/extragear-graphics/digikam/using-setup.html">https://docs.kde.org/trunk5/en/extragear-graphics/digikam/using-setup.html</a>
I installed MySQL v8.0, and executed the following SQL commands to set
up the database (see below). Note that I had to go beyond the
documentation and add the "WITH mysql_native_password" clause in order
for MySQL to use a password plugin that is supported by Digikam (at
least the Mac version).
When using the DB migration tool, I am able to connect to the MySQL
server, but when I try to initiate the migration, I get a pop up window
saying "Error while creating the database schema".
I'm not sure what the error is. I do see on the server side that the
digikam_core database does get populated with tables. The digikam
database does not.
I have some DBA experience, so I'm sure that I could work past any
mis-configuration issues on the MySQL side, if only I could see a more
detailed error message. Any suggestions on how to get past this
uninformative error message would be greatly appreciated. Thanks!
Cheers,
~Tomer
---
CREATE USER 'digikam'@'%' IDENTIFIED WITH mysql_native_password BY
<password>;
GRANT ALL ON *.* to 'digikam'@'%';
CREATE DATABASE digikam;
GRANT ALL PRIVILEGES ON digikam.* TO 'digikam'@'%';
CREATE DATABASE digikam_core;
GRANT ALL PRIVILEGES ON digikam_core.* TO 'digikam'@'%';
FLUSH PRIVILEGES;
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
</pre>
</blockquote>
<p><br>
</p>
<pre class="moz-signature" cols="72">--
Please do not send me sensitive information (e.g., passwords, personal details, financial/health information) via email, as it is not secure.
Please contact me to determine the best way to transfer sensitive information safely. Thank you!
</pre>
</body>
</html>