[Digikam-devel] [Bug 134594] WISH: Independent database backend support for increased usability (MySQL/PostgreSQL etc)

[Halim I]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=134594         




------- Additional Comments From yallaone gmail com  2006-09-27 12:31 -------
Would it make sense to at least run this discussion by the developer of other 
software that digikam is likely to be cooperating and coexisting with?

I'm firstly thinking of mythTV / freevo. I assume (haven't done a poll - might 
be worth while) that most computer users prefer to manage/sort their pictures 
on their computer, but to share them with friends and family on the web and 
in the living-room TV. I don't know much about Myth/Freevo developers, but it 
seems clear to me that end-users would greatly benefit from some kind of 
interaction! Same would go for web-photoalbum projects such as for instance 
coppermine.

Realistically, a common database format for myth-photoalbum, freevo, digikam, 
coppermine and others might be difficult to achieve, but at least a well 
documented API so that other primary viewing-apps can benefit from the work 
done through digikam.

Thoughts?

On Tuesday 26 September 2006 13:57, Gilles Caulier wrote:
> Other point to talk is about the database structure : if we use new DB
> backends, we can change something in structure at the same time ?
>
> There are other files in B.K.o witch require database changes, especially
> to perform search about photograph informations, like aperture for example,
> or GPS coordinates.
>
> I think we can change database structure at the same time because in all
> cases, we will need an tool to migrate from sqlite to new DB backend. We
> just need to take a care about the new structure to be more flexible than
> the actual.