[KPhotoAlbum] Optimization of index.xml

Shawn Willden shawn-kimdaba at willden.org
Mon Sep 4 15:49:10 BST 2006

On Monday 04 September 2006 01:18, William Holland wrote:
> A while ago, I looked into synchronisation with mysql, and MySQL definitely
> supports synchronisation between two databases, so your best option is to
> look into the MySQL native Synchronisation, rather than writing a custom
> Kphotoalbum one.

Perhaps that could be made to work, but I don't think it would be a good fit.  
Master/slave synchronization is designed for a different application and 
doesn't really support simultaneous changes to both databases.  MySQL's 
clustered synchronization requires that all of the databases be in constant 
communication and also limits you to in-memory databases.  Further, using the 
native tools would limit synchronization to a single database platform.  A 
purpose-built tool could easily synchronize across any of the supported SQL 

> There were some issues with multiple updates to the same 
> record in both databases, but this was 5 years ago, so it's probably
> improved.

I don't see how it could be, because this is a problem that doesn't have an 
automated solution.  If the DB synchronization did attempt to handle this, it 
would have to use some heuristic like "last change wins", but that wouldn't 
necessarily work.  Conflicts must, IMO, be resolved by a human.

Your suggestion is worth exploring, certainly, but I don't have high hopes 
that it will do the job.



More information about the Kphotoalbum mailing list