dk 4.0 problems with cropping

[Dr. Martin Senftleben]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I just installed dk 4 and found some serious problem when editing an
image. I tried to crop an image (a rectangular selection out of the
image) and then clicked "cut to selection" (or however it is called -
in German it's "Auf Auswahl zuschneiden"). Suddenly there was a black
bar at the bottom of the image. So I tried to select a smaller portion
that didn't include the black bar, and also reduced the width of the
selection a bit. After again hitting "cut to selection" I had the
selection placed over the previous image. I first thought that's only
a graphics card problem, but when I closed the editor, I saw that the
image was in fact saved like I saw it before: the selection on top of
the previous image, only resized to match the screen's size. So I had
to reopen the image and again cut out the desired portion. This time
it worked right. Most likely it's not easily reproducable, but I'll
see, because such cropping I do quite often.

Regards

Martin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iEYEARECAAYFAlN8v3kACgkQUmmuY48ByEiFgACeJqNoaQnv1TFkFiefPAu37nQS
u+YAoIvUdRH54QiUfHQZKKWkg58mdamP
=UMgv
-----END PGP SIGNATURE-----

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-4]

Reproducible. Again, it's a side effect of Qt4 model/view port.

Note : normalization of crop area work fine if you go outside of
left/top corener of image. Other corners has a dysfunction.

Please report this problem to bugzilla. Thanks in advance

Gilles Caulier

2014-05-21 17:00 GMT+02:00 Dr. Martin Senftleben <[hidden email]>:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I just installed dk 4 and found some serious problem when editing an
> image. I tried to crop an image (a rectangular selection out of the
> image) and then clicked "cut to selection" (or however it is called -
> in German it's "Auf Auswahl zuschneiden"). Suddenly there was a black
> bar at the bottom of the image. So I tried to select a smaller portion
> that didn't include the black bar, and also reduced the width of the
> selection a bit. After again hitting "cut to selection" I had the
> selection placed over the previous image. I first thought that's only
> a graphics card problem, but when I closed the editor, I saw that the
> image was in fact saved like I saw it before: the selection on top of
> the previous image, only resized to match the screen's size. So I had
> to reopen the image and again cut out the desired portion. This time
> it worked right. Most likely it's not easily reproducable, but I'll
> see, because such cropping I do quite often.
>
> Regards
>
> Martin
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
>
> iEYEARECAAYFAlN8v3kACgkQUmmuY48ByEiFgACeJqNoaQnv1TFkFiefPAu37nQS
> u+YAoIvUdRH54QiUfHQZKKWkg58mdamP
> =UMgv
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users
>

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-4]

Martin,

I found the problem. I fixed it with this commit :

http://commits.kde.org/digikam/38770ddd94ba95e4ebd27c98f5a2d7e11adb36e9

If you can use current implementation from git/master (next 4.1.0),
please try and report...

Gilles Caulier

2014-05-21 17:11 GMT+02:00 Gilles Caulier <[hidden email]>:

> Reproducible. Again, it's a side effect of Qt4 model/view port.
>
> Note : normalization of crop area work fine if you go outside of
> left/top corener of image. Other corners has a dysfunction.
>
> Please report this problem to bugzilla. Thanks in advance
>
> Gilles Caulier
>
> 2014-05-21 17:00 GMT+02:00 Dr. Martin Senftleben <[hidden email]>:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> I just installed dk 4 and found some serious problem when editing an
>> image. I tried to crop an image (a rectangular selection out of the
>> image) and then clicked "cut to selection" (or however it is called -
>> in German it's "Auf Auswahl zuschneiden"). Suddenly there was a black
>> bar at the bottom of the image. So I tried to select a smaller portion
>> that didn't include the black bar, and also reduced the width of the
>> selection a bit. After again hitting "cut to selection" I had the
>> selection placed over the previous image. I first thought that's only
>> a graphics card problem, but when I closed the editor, I saw that the
>> image was in fact saved like I saw it before: the selection on top of
>> the previous image, only resized to match the screen's size. So I had
>> to reopen the image and again cut out the desired portion. This time
>> it worked right. Most likely it's not easily reproducable, but I'll
>> see, because such cropping I do quite often.
>>
>> Regards
>>
>> Martin
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1
>>
>> iEYEARECAAYFAlN8v3kACgkQUmmuY48ByEiFgACeJqNoaQnv1TFkFiefPAu37nQS
>> u+YAoIvUdRH54QiUfHQZKKWkg58mdamP
>> =UMgv
>> -----END PGP SIGNATURE-----
>>
>> _______________________________________________
>> Digikam-users mailing list
>> [hidden email]
>> https://mail.kde.org/mailman/listinfo/digikam-users
>>

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Anders Lund]

On Onsdag den 21. maj 2014 17:00:13, Dr. Martin Senftleben wrote:

> I just installed dk 4 and found some serious problem when editing an
> image. I tried to crop an image (a rectangular selection out of the
> image) and then clicked "cut to selection" (or however it is called -
> in German it's "Auf Auswahl zuschneiden"). Suddenly there was a black
> bar at the bottom of the image. So I tried to select a smaller portion
> that didn't include the black bar, and also reduced the width of the
> selection a bit. After again hitting "cut to selection" I had the
> selection placed over the previous image. I first thought that's only
> a graphics card problem, but when I closed the editor, I saw that the
> image was in fact saved like I saw it before: the selection on top of
> the previous image, only resized to match the screen's size. So I had
> to reopen the image and again cut out the desired portion. This time
> it worked right. Most likely it's not easily reproducable, but I'll
> see, because such cropping I do quite often.
>
> Regards
>
> Martin

I'm hit by this to a degree of digikam being unusable :-(

--
Anders
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Samuel Gilbert]

I confirm this issue.  I have exactly the same problem.

Samuel

On May 23, 2014 19:29:57 Anders Lund wrote:

> On Onsdag den 21. maj 2014 17:00:13, Dr. Martin Senftleben wrote:
> > I just installed dk 4 and found some serious problem when editing an
> > image. I tried to crop an image (a rectangular selection out of the
> > image) and then clicked "cut to selection" (or however it is called -
> > in German it's "Auf Auswahl zuschneiden"). Suddenly there was a black
> > bar at the bottom of the image. So I tried to select a smaller portion
> > that didn't include the black bar, and also reduced the width of the
> > selection a bit. After again hitting "cut to selection" I had the
> > selection placed over the previous image. I first thought that's only
> > a graphics card problem, but when I closed the editor, I saw that the
> > image was in fact saved like I saw it before: the selection on top of
> > the previous image, only resized to match the screen's size. So I had
> > to reopen the image and again cut out the desired portion. This time
> > it worked right. Most likely it's not easily reproducable, but I'll
> > see, because such cropping I do quite often.
> >
> > Regards
> >
> > Martin
>
> I'm hit by this to a degree of digikam being unusable :-(

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-4]

fixed in current implementation. It will be published in 4.1.0

Gilles Caulier

2014-05-23 19:39 GMT+02:00 Samuel Gilbert <[hidden email]>:

> I confirm this issue.  I have exactly the same problem.
>
> Samuel
>
> On May 23, 2014 19:29:57 Anders Lund wrote:
>> On Onsdag den 21. maj 2014 17:00:13, Dr. Martin Senftleben wrote:
>> > I just installed dk 4 and found some serious problem when editing an
>> > image. I tried to crop an image (a rectangular selection out of the
>> > image) and then clicked "cut to selection" (or however it is called -
>> > in German it's "Auf Auswahl zuschneiden"). Suddenly there was a black
>> > bar at the bottom of the image. So I tried to select a smaller portion
>> > that didn't include the black bar, and also reduced the width of the
>> > selection a bit. After again hitting "cut to selection" I had the
>> > selection placed over the previous image. I first thought that's only
>> > a graphics card problem, but when I closed the editor, I saw that the
>> > image was in fact saved like I saw it before: the selection on top of
>> > the previous image, only resized to match the screen's size. So I had
>> > to reopen the image and again cut out the desired portion. This time
>> > it worked right. Most likely it's not easily reproducable, but I'll
>> > see, because such cropping I do quite often.
>> >
>> > Regards
>> >
>> > Martin
>>
>> I'm hit by this to a degree of digikam being unusable :-(
>
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Samuel Gilbert]

Cool!  That was fast!  Thank you Gilles!

Samuel

On May 23, 2014 22:30:09 Gilles Caulier wrote:

> fixed in current implementation. It will be published in 4.1.0
>
> Gilles Caulier
>
> 2014-05-23 19:39 GMT+02:00 Samuel Gilbert <[hidden email]>:
> > I confirm this issue.  I have exactly the same problem.
> >
> > Samuel
> >
> > On May 23, 2014 19:29:57 Anders Lund wrote:
> >> On Onsdag den 21. maj 2014 17:00:13, Dr. Martin Senftleben wrote:
> >> > I just installed dk 4 and found some serious problem when editing an
> >> > image. I tried to crop an image (a rectangular selection out of the
> >> > image) and then clicked "cut to selection" (or however it is called -
> >> > in German it's "Auf Auswahl zuschneiden"). Suddenly there was a black
> >> > bar at the bottom of the image. So I tried to select a smaller portion
> >> > that didn't include the black bar, and also reduced the width of the
> >> > selection a bit. After again hitting "cut to selection" I had the
> >> > selection placed over the previous image. I first thought that's only
> >> > a graphics card problem, but when I closed the editor, I saw that the
> >> > image was in fact saved like I saw it before: the selection on top of
> >> > the previous image, only resized to match the screen's size. So I had
> >> > to reopen the image and again cut out the desired portion. This time
> >> > it worked right. Most likely it's not easily reproducable, but I'll
> >> > see, because such cropping I do quite often.
> >> >
> >> > Regards
> >> >
> >> > Martin
> >>
> >> I'm hit by this to a degree of digikam being unusable :-(
> >
> > _______________________________________________
> > Digikam-users mailing list
> > [hidden email]
> > https://mail.kde.org/mailman/listinfo/digikam-users
>
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Dr. Martin Senftleben]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Gilles and all others,

Am 23.05.2014 22:30, schrieb Gilles Caulier:
> fixed in current implementation. It will be published in 4.1.0

thanks! Good that you could find the cause.

I still have problems with the stability of digikam (in fact, this is
a continuous problem). Every now and then it crashes (yesterday four
times), often when there is no really heavy task is at hand, like when
I click on an image to see a larger version of it, or when I want to
open the editor.

Now I was wondering if this could be because of the size of my
collection. I'm using sqlite, that seemed sufficient when I started.
Now I read that it's good for collections with up to 100.000 images,
beyond that it would be better to use mySQL.
I have about 280.000 files in my collection, while I'm not sure how
many sidecar files are in this collection. I don't know if this would
be relevant, but let's estimate some 20.000 images have sidecar files,
so it still comes to more than double as many images as recommended
for sqlite. So I would like to change to mySQL as database in the hope
this will improve things. But how to go about it without losing any
date like tags, descriptions etc.?

Regards

Martin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iEYEARECAAYFAlOALXMACgkQUmmuY48ByEgRQACeIUPBH4su1CgJMU7W3UihgOd3
tzEAoLSjY1FxGE6RnoInfsLc/3+J8Umw
=i9y4
-----END PGP SIGNATURE-----

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-4]

Sqlite code has introduced recently an hazardous instability. It's a
UPSTREAM problem reported a lots of time in bugzilla here :

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

THe solution is to update sqlite3 AND QtSqlite plugin. This last one
is used in fact. digiKam do not use Sqlite3 library directly.

Sound like Sqlite3 have been updated without to update Qt plugin,
which has introduced a binary incompatibility.

Mysql is not the right solution. Mysql still experimental and alots of
problem need to be solved.

Here i updated SQlite3 and QTSlite plugin, ands digiKam do not crash.
Look well bug #329697 contents for details.

Gilles Caulier

2014-05-24 7:26 GMT+02:00 Dr. Martin Senftleben <[hidden email]>:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi Gilles and all others,
>
> Am 23.05.2014 22:30, schrieb Gilles Caulier:
>> fixed in current implementation. It will be published in 4.1.0
>
> thanks! Good that you could find the cause.
>
> I still have problems with the stability of digikam (in fact, this is
> a continuous problem). Every now and then it crashes (yesterday four
> times), often when there is no really heavy task is at hand, like when
> I click on an image to see a larger version of it, or when I want to
> open the editor.
>
> Now I was wondering if this could be because of the size of my
> collection. I'm using sqlite, that seemed sufficient when I started.
> Now I read that it's good for collections with up to 100.000 images,
> beyond that it would be better to use mySQL.
> I have about 280.000 files in my collection, while I'm not sure how
> many sidecar files are in this collection. I don't know if this would
> be relevant, but let's estimate some 20.000 images have sidecar files,
> so it still comes to more than double as many images as recommended
> for sqlite. So I would like to change to mySQL as database in the hope
> this will improve things. But how to go about it without losing any
> date like tags, descriptions etc.?
>
> Regards
>
> Martin
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
>
> iEYEARECAAYFAlOALXMACgkQUmmuY48ByEgRQACeIUPBH4su1CgJMU7W3UihgOd3
> tzEAoLSjY1FxGE6RnoInfsLc/3+J8Umw
> =i9y4
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users
>

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[maderios]

On 05/24/2014 07:43 AM, Gilles Caulier wrote:
> Mysql is not the right solution. Mysql still experimental and alots of
> problem need to be solved.
Hi
I migrated from sqlite to Mysql external db because sqlite is too slow
for me.
DK-4.0 works fine, faster.
I didn't use db migration tool because it doesn't work (impossible to
connect to db).
Conditions:
Debian Jessie/testing system + DK.4.0 packages from Debian Sid
- about 15 000 files.
- no exif or iptc tags,
- only XMP sidecar metadata (read write to/from image and xmp sidecar)
- only image tags
- only keywords
--
Maderios


_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Dr. Martin Senftleben]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

Am 24.05.2014 07:43, schrieb Gilles Caulier:
> Sqlite code has introduced recently an hazardous instability. It's
> a UPSTREAM problem reported a lots of time in bugzilla here :
>
> https://bugs.kde.org/show_bug.cgi?id=329697
>
> THe solution is to update sqlite3 AND QtSqlite plugin. This last
> one is used in fact. digiKam do not use Sqlite3 library directly.

And how do I go about it? There's no update in the repository. Is
there a way to get the update without having to compile the stuff?

Still there is the question how to speed things up. When managing
files, it takes awfully long (moving, deleting or copying images for
instance), if it works. If mysql is no option, what then? With about
250.000 files to manage sqlite seems to reach its limits.

TIA

Martin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iEYEARECAAYFAlOBiYUACgkQUmmuY48ByEjZKACgzjg4mSQ0oSxgKwDntJzpEGYa
M5UAoJooAcsIErymztHi9N5ok/to80aD
=dnYR
-----END PGP SIGNATURE-----

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[maderios]

On 05/25/2014 08:11 AM, Dr. Martin Senftleben wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi,
>
> Am 24.05.2014 07:43, schrieb Gilles Caulier:
>> Sqlite code has introduced recently an hazardous instability. It's
>> a UPSTREAM problem reported a lots of time in bugzilla here :
>>
>> https://bugs.kde.org/show_bug.cgi?id=329697
>>
>> THe solution is to update sqlite3 AND QtSqlite plugin. This last
>> one is used in fact. digiKam do not use Sqlite3 library directly.
>
> And how do I go about it? There's no update in the repository. Is
> there a way to get the update without having to compile the stuff?
>
> Still there is the question how to speed things up. When managing
> files, it takes awfully long (moving, deleting or copying images for
> instance), if it works. If mysql is no option, what then? With about
> 250.000 files to manage sqlite seems to reach its limits.

Hi
You may use Mysql but it's considered as experimental.
Mysql works for me with xmp tags. Be careful, experiment first in a
special account/user only used for testing. If you dot it, always sync
from images tags to database and never from database to images (you may
loose yours tags). If it doesn't work, you can return to sqlite.

--
Maderios


_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Dr. Martin Senftleben]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 25.05.2014 14:57, schrieb maderios:
> On 05/25/2014 08:11 AM, Dr. Martin Senftleben wrote: Hi You may
> use Mysql but it's considered as experimental. Mysql works for me
> with xmp tags. Be careful, experiment first in a special
> account/user only used for testing. If you dot it, always sync from
> images tags to database and never from database to images (you may
> loose yours tags). If it doesn't work, you can return to sqlite.

Testing with an environment that is similar to the existing one would
require another hard disk drive, which is not feasible at the moment.
Testing with just a few images wouldn't be helpful in my view, since
it's important to know if problems occur when handling some 250.000 or
so images.

I don't want to lose any of what I've done so far, so I better stick to
the current setting and hope it gets stabilized or mysql becomes reliable.

Regards

Martin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iEYEARECAAYFAlOCA7YACgkQUmmuY48ByEgxdACg2hOaDN61S7H3ttAAhYCkSp3p
9dMAoNCpj55Wc7lQIER8MUJ7Qe0nWU2G
=3RLH
-----END PGP SIGNATURE-----

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

Le 25/05/2014 16:52, Dr. Martin Senftleben a écrit :

> I don't want to lose any of what I've done so far, so I better stick to
> the current setting and hope it gets stabilized or mysql becomes reliable.

mysql is much harder to backup and restore than sqlite.

I do not have as many files as you have... only approx 40.000

what I coiuld do is create xml sidecar files for tags. It's pretty easy to
backup these files only (text, small) before testing I guess it may also be
faster to write.

depending to sqlite database size it should be possible to store it in ram (or
cache it to ram)

jdd


--
http://www.dodin.org
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[maderios]

On 05/25/2014 04:52 PM, Dr. Martin Senftleben wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Am 25.05.2014 14:57, schrieb maderios:
>> On 05/25/2014 08:11 AM, Dr. Martin Senftleben wrote: Hi You may
>> use Mysql but it's considered as experimental. Mysql works for me
>> with xmp tags. Be careful, experiment first in a special
>> account/user only used for testing. If you dot it, always sync from
>> images tags to database and never from database to images (you may
>> loose yours tags). If it doesn't work, you can return to sqlite.
>
> Testing with an environment that is similar to the existing one would
> require another hard disk drive, which is not feasible at the moment.

It depends on your system.
On a linux or bsd system, you just have to create an other user on your
system and launch DK-4.0. You don't need another hd or partition.

> Testing with just a few images wouldn't be helpful in my view, since
> it's important to know if problems occur when handling some 250.000 or
> so images.
>
You may copy only 2000 files or 4000 files and experiment with it. It's
sufficient to see if a problem occurs.

--
Maderios


_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Andy Gleeson]

Hi

I am trying to move from  sqlite to mysql. The environment is digikam
4.0.0 on Ubuntu 14.04

I can connect to the mysql server through other applications but when I
try pointing digicam at it I get a message saying "Database connection
was not successful" "driver not loaded"
Has anyone got any ideas I can try?
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[maderios]

On 05/26/2014 05:20 PM, Andy Gleeson wrote:
> Hi
>
> I am trying to move from  sqlite to mysql. The environment is digikam
> 4.0.0 on Ubuntu 14.04
>
> I can connect to the mysql server through other applications but when I
> try pointing digicam at it I get a message saying "Database connection
> was not successful" "driver not loaded"
> Has anyone got any ideas I can try?
Hi
External or internal mysql DK config ?
Did you use tool migration ?

--
Maderios


_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-4]

2014-05-26 17:20 GMT+02:00 Andy Gleeson <[hidden email]>:
> Hi
>
> I am trying to move from  sqlite to mysql. The environment is digikam 4.0.0
> on Ubuntu 14.04
>
> I can connect to the mysql server through other applications but when I try
> pointing digicam at it I get a message saying "Database connection was not
> successful" "driver not loaded"
> Has anyone got any ideas I can try?

by driver, this want certainly mean QtMysql plugin... Check if this
one is properlly installed...

Gilles Caulier

>
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Andy Gleeson]

I used the external config. I cannot connect using the migration tool either.

Andy Gleeson
Rookery Forge

> On 26 May 2014, at 17:29, maderios <[hidden email]> wrote:
>
>> On 05/26/2014 05:20 PM, Andy Gleeson wrote:
>> Hi
>>
>> I am trying to move from  sqlite to mysql. The environment is digikam
>> 4.0.0 on Ubuntu 14.04
>>
>> I can connect to the mysql server through other applications but when I
>> try pointing digicam at it I get a message saying "Database connection
>> was not successful" "driver not loaded"
>> Has anyone got any ideas I can try?
> Hi
> External or internal mysql DK config ?
> Did you use tool migration ?
>
> --
> Maderios
>
>
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Andy Gleeson]

I will check that in the morning, thanks

Andy Gleeson
Rookery Forge

> On 26 May 2014, at 17:30, Gilles Caulier <[hidden email]> wrote:
>
> 2014-05-26 17:20 GMT+02:00 Andy Gleeson <[hidden email]>:
>> Hi
>>
>> I am trying to move from  sqlite to mysql. The environment is digikam 4.0.0
>> on Ubuntu 14.04
>>
>> I can connect to the mysql server through other applications but when I try
>> pointing digicam at it I get a message saying "Database connection was not
>> successful" "driver not loaded"
>> Has anyone got any ideas I can try?
>
> by driver, this want certainly mean QtMysql plugin... Check if this
> one is properlly installed...
>
> Gilles Caulier
>
>>
>> _______________________________________________
>> Digikam-users mailing list
>> [hidden email]
>> https://mail.kde.org/mailman/listinfo/digikam-users
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users