[Digikam-devel] Getting Started For GSOC

[Varun Gupta]

I have started looking at the code from the given link [1] . I still have
doubts what do you mean by the last stage , in the doc do i have to list
all the main problems that need to be fixed for MYSQL types?


https://projects.kde.org/projects/extragear/graphics/
digikam/repository/revisions/master/show/libs/database

On Wed, Feb 24, 2016 at 11:58 AM, Gilles Caulier <caulier.gilles at gmail.com>
wrote:

> Varun,
>
> * Qt is important to understand all the code. The digiKam database, that
> is review and reorganized during Qt5 port is large and complex. I recommend
> to take a look into the code before to start all investigations, to check
> If you will be fine with the implementations.
>
> This is the first stage of this project : to be able to understand quickly
> the current code.
>
>
> https://projects.kde.org/projects/extragear/graphics/digikam/repository/revisions/master/show/libs/database
>
> There are 3 database types :
>
> 1/ Sqlite
> 2/ Local Mysql server (working as Sqlite with a dedicated server
> implemented in digiKam core)
> 3/ Remote Mysql server
>
> 1/ work very well and is stable.
>
> 2/ work but schema need big improvement and hack.
>
> 3/ need requirement of 2 plus new code to be compatible with concurrent
> access by multiple digiKam session at the same case (Photo agency use case)
>
> * The second stage of this project is to look in databases schemas, that i
> s also review and re-organize while Qt5 port. The digiKam database
> interface as a XML wrapper tho handle schemas, written in different
> sections of a big XML file :
>
>
> https://projects.kde.org/projects/extragear/graphics/digikam/repository/revisions/master/show/data/database
>
> For each Database types, we have 3 database container :
>
> - Core (the big one for digiKam properties)
> - Thumbnails (to store wavelets thumbs of images)
> - Faces (to store faces finger prints for detection and recognition).
>
> In the database implementation, you will find sub sections dedicated for
> dedicated features.
>
> * The 3rd stage of this project is to review buzilla reports that i sorted
> for database and list all main problems to fix by priority order for Mysql
> types.
>
> https://bugs.kde.org/component-report.cgi?product=digikam
>
> * The last stage to complete this first pre-analyze of this project is to
> write a google doc to list all technical details listed below plus all your
> investigations, before to write the proposal for GSoC.
>
> I'm waiting questions now.
>
> Good luck
>
> Gilles Caulier
>
>
>
> 2016-02-24 2:38 GMT+01:00 Varun Gupta <varungupta1803 at gmail.com>:
>
>> Hi,
>> Gills I looked at the prerequisites for the project and I am comfortable
>> with them except for Qt. Qt I hope to learn soon. Well as for databases I
>> am comfortable with both MYSQL and SQLITE.
>>
>> Regards,
>> Varun
>>
>> On Wed, Feb 24, 2016 at 1:10 AM, Gilles Caulier <caulier.gilles at gmail.com
>> > wrote:
>>
>>> Hi,
>>>
>>> What's your skill exactly ? Did you have any experience in database ?
>>>
>>> Best
>>>
>>> Gilles Caulier
>>>
>>> 2016-02-23 19:28 GMT+01:00 Varun Gupta <varungupta1803 at gmail.com>:
>>>
>>>> Hi,
>>>> I am Varun and I want to participate for GSOC this year. I have been
>>>> looking at the project ideas on the Ideas Page. Well I wanted to work on
>>>> the idea  "digiKam MySQL / MariaDB Database support".
>>>> It would be helpful if someone could guide me to as where to get the
>>>> documentation related to the idea so I could get an early start and get
>>>> familiar with the code.
>>>>
>>>> Regards,
>>>> Varun
>>>>
>>>> _______________________________________________
>>>> Digikam-devel mailing list
>>>> Digikam-devel at kde.org
>>>> https://mail.kde.org/mailman/listinfo/digikam-devel
>>>>
>>>>
>>>
>>> _______________________________________________
>>> Digikam-devel mailing list
>>> Digikam-devel at kde.org
>>> https://mail.kde.org/mailman/listinfo/digikam-devel
>>>
>>>
>>
>> _______________________________________________
>> Digikam-devel mailing list
>> Digikam-devel at kde.org
>> https://mail.kde.org/mailman/listinfo/digikam-devel
>>
>>
>
> _______________________________________________
> Digikam-devel mailing list
> Digikam-devel at kde.org
> https://mail.kde.org/mailman/listinfo/digikam-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-devel/attachments/20160225/29dc8792/attachment.html>