[Shotwell] mysql/postgresql as backend?
jim at yorba.org
Wed Apr 28 10:41:16 PDT 2010
We've thought down these lines, but it's not as simple as it seems.
The database is not used by Shotwell in a traditional sense, a la a
web application. If we hit the database every time we needed
information about a photo or a tag or an event, Shotwell would be slow
indeed. This is not a limitation of SQLite; using MySQL or PostgreSQL
would not make things different.
Much of the database is loaded into memory at startup and maintained
there. When a field is changed, it's written out to disk, but kept in
memory as well. If another application were to write to the database
while Shotwell was running, Shotwell would have no idea the change has
been made, and now things are messed up.
Some of this thinking is reflected in this ticket:
http://trac.yorba.org/ticket/1699 There's a lot to think about there,
On Wed, Apr 28, 2010 at 7:39 AM, Bengt Thuree <bengt.thuree at gmail.com> wrote:
> Any thoughts/plans on coming up with a proper backend, so the database
> can be accessed by different persons at the same time.
> I saw GnuCASH is using libdbi. Would this be of interest in Shotwell?
> In my case, I have a number of desktops/laptops/thin clients, and one
> fileserver. I am having the photos and photo db on the file server, and
> would like to be able to access my photos from which ever computer I
> want, as well as from multiple computers at the same time.
> Fingers crossed for this has been thought of :)
> Shotwell mailing list
> Shotwell at lists.yorba.org
More information about the Shotwell