Bugs::DigiKam::Database cleanup and some RFC

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Bugs::DigiKam::Database cleanup and some RFC

Francesco Riosa
Request for comment:

Bug 267733 - Automatical initialisation of Internal MySQL database
doesn't work after digikam start
     Should we totally remove MySQL Internal server option?
     It's a pain with no gain, sqlite is the one that does
     "Internal server" part well

Bug 268204 - MySQL filenames are case-INsensitive
     Uhm I've missed this one before.
     Solution require a schema change and much testing, doable in -rc
     times?

Bug 267131 - Digikam config and data cannot be moved, absolute paths
embedded in database and digikamrc
     I want to have this fixed, at least for 2.1.0 suggestions?


To Be Closed?


Bug 265034 - Database corrupted after terminating frozen digikam
     1.8.0, no data

Bug 267190 - digiKam crashes when other applications rename files it is
loading.
     1.4.0, old, probably fixed

Bug 272332 - Moving a versioned file crashes digikam2
     tested Fixed

Bug 203196 - Multiple Albums for 1 Folder
     tested Fixed

Bug 229234 - thumbnail mismatch for images with same name
     1.2.0, old, possibly fixed, easy workaround

Bug 237037 - digikam sqlite convience copy [patch]
     sqlite2 is for digikam <= 0.7 right? What about to forget?
     i.e. to remove the 3rdparty lib?

Bug 267802 - Database connections not closed on exit
     1.4.0 not reproducible/fixed

Bug 163763 - digikam hangs during operation and startup
     old fixed and buried

Bug 195006 - national charaters not accepted in database file path
     0.10.0 not reproducible, ancient

Bug 145743 - only include displayable files in database
     0.10.0 long time fixed
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

Re: Bugs::DigiKam::Database cleanup and some RFC

Gilles Caulier-4


2011/6/29 Francesco Riosa <[hidden email]>
Request for comment:

Bug 267733 - Automatical initialisation of Internal MySQL database
doesn't work after digikam start
    Should we totally remove MySQL Internal server option?
    It's a pain with no gain, sqlite is the one that does
    "Internal server" part well

I'm not sure. We must have a discussion with Marcel about this subject. He will back from holidays in 2 weeks.
 

Bug 268204 - MySQL filenames are case-INsensitive
    Uhm I've missed this one before.
    Solution require a schema change and much testing, doable in -rc
    times?

It still one mount normally for stabilization. If you is sure that it's better to do it before fianl release, let's go, else report for 2.1, planed one or 2 month after 2.0
 

Bug 267131 - Digikam config and data cannot be moved, absolute paths
embedded in database and digikamrc
    I want to have this fixed, at least for 2.1.0 suggestions?


Same that previous point.
 

To Be Closed?


Bug 265034 - Database corrupted after terminating frozen digikam
    1.8.0, no data

close it and said to user to re-open it if problem occur again.
 

Bug 267190 - digiKam crashes when other applications rename files it is
loading.
    1.4.0, old, probably fixed

idem.
 

Bug 272332 - Moving a versioned file crashes digikam2
    tested Fixed


to close
 
Bug 203196 - Multiple Albums for 1 Folder
    tested Fixed

to close
 
Bug 229234 - thumbnail mismatch for images with same name
    1.2.0, old, possibly fixed, easy workaround

close it and said to user to re-open it if problem occur again.
 

Bug 237037 - digikam sqlite convience copy [patch]
    sqlite2 is for digikam <= 0.7 right? What about to forget?
    i.e. to remove the 3rdparty lib?

3rd party is not only for sqlite2. There is other lib in this folder. We cannot remove it as well.

About sqlite2, we must to talk with Marcel if it fine to drop support of digiKam DB < 0.9 with digiKam 2.0.0.

We can plan it for 2.1 anyway...
 

Bug 267802 - Database connections not closed on exit
    1.4.0 not reproducible/fixed


to close
 
Bug 163763 - digikam hangs during operation and startup
    old fixed and buried

 
to close
 
Bug 195006 - national charaters not accepted in database file path
    0.10.0 not reproducible, ancient

to close
 
Bug 145743 - only include displayable files in database
    0.10.0 long time fixed

to close
 
Great work Francesco ! Thanks a lots for your help...

Gilles

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

Re: Bugs::DigiKam::Database cleanup and some RFC

Francesco Riosa
On 06/29/11 13:40, Gilles Caulier wrote:

>
>
> 2011/6/29 Francesco Riosa <[hidden email]
> <mailto:[hidden email]>>
>
>     Request for comment:
>
>     Bug 267733 - Automatical initialisation of Internal MySQL database
>     doesn't work after digikam start
>          Should we totally remove MySQL Internal server option?
>          It's a pain with no gain, sqlite is the one that does
>     "Internal server" part well
>
>
> I'm not sure. We must have a discussion with Marcel about this subject.
> He will back from holidays in 2 weeks.
>
>
>     Bug 268204 - MySQL filenames are case-INsensitive
>          Uhm I've missed this one before.
>          Solution require a schema change and much testing, doable in -rc
>          times?
>
>
> It still one mount normally for stabilization. If you is sure that it's
> better to do it before fianl release, let's go, else report for 2.1,
> planed one or 2 month after 2.0
>
>
>     Bug 267131 - Digikam config and data cannot be moved, absolute paths
>     embedded in database and digikamrc
>          I want to have this fixed, at least for 2.1.0 suggestions?
>
>
> Same that previous point.
>

I'll do something in sql/2.0 branch about these in the meantime, revert
and cherry pick are cheapwith git ;)


>
>     To Be Closed?
[snip]

>
>     Bug 237037 - digikam sqlite convience copy [patch]
>          sqlite2 is for digikam <= 0.7 right? What about to forget?
>          i.e. to remove the 3rdparty lib?
>
>
> 3rd party is not only for sqlite2. There is other lib in this folder. We
> cannot remove it as well.
>
> About sqlite2, we must to talk with Marcel if it fine to drop support of
> digiKam DB < 0.9 with digiKam 2.0.0.
>
> We can plan it for 2.1 anyway...

sure, no hurry

[snip]

> Great work Francesco ! Thanks a lots for your help...
>
> Gilles
>

It's a pleasure,

Francesco
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

Re: Bugs::DigiKam::Database cleanup and some RFC

Marcel Wiesweg
In reply to this post by Gilles Caulier-4

> > Bug 267733 - Automatical initialisation of Internal MySQL database
> > doesn't work after digikam start
> >
> >     Should we totally remove MySQL Internal server option?
> >     It's a pain with no gain, sqlite is the one that does
> >     "Internal server" part well
>
> I'm not sure. We must have a discussion with Marcel about this subject. He
> will back from holidays in 2 weeks.

At the time, it worked impressively well with Akonadi, combining the ease of
use of SQLite with the features of MySQL.
If it's a real pain, broken anyway and the apparent MySQL maintainer (you)
says no, it's up to you.


> > Bug 237037 - digikam sqlite convience copy [patch]
> >
> >     sqlite2 is for digikam <= 0.7 right? What about to forget?
> >     i.e. to remove the 3rdparty lib?
>
> 3rd party is not only for sqlite2. There is other lib in this folder. We
> cannot remove it as well.
>
> About sqlite2, we must to talk with Marcel if it fine to drop support of
> digiKam DB < 0.9 with digiKam 2.0.0.

At one point, we should drop support. Any such decision is fine for me.



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