On Fri, Feb 17, 2012 at 04:36:19PM +0200, Abe Pazos wrote: > I was thinking that probably it's not that hard to merge the databases > with a Python script. I've done that in the past with two MySQL databases. > > Of course one risks messing up the db, but if you keep copies it should > be ok. It's just matter of reading both tables, ignoring common rows, > and then asking in which direction to copy/merge/delete. Beyond Compare > does this merging very well and can serve as an example. [...]
If the shotwell db itself would be able to include many sources, as I proposed a while ago, then an external solution would not be necessary. It would solve the problem of ressources on USB-sticks, external drives and more-than-one db on the same computer (e.g. keep photos of different topics or persons seperated, but browse them together, if asked for it). > > This could serve as an external merging tool to find the best workflow, and > later parts of it could be rewritten in Shotwell if people are interested. Merging databases (wiuthout necessarily merging the directories with all files) as one ability of shotwell would be fine. > > Actually, I can imagine using an external "Shotwell DB manager tool". > For example to move photos to a new location. I did that already using > SQLite Manager in Firefox. Such a tool would provide an easier interface > to move, rename, merge, etc. without having to know SQL. A completely tool-related approach (like unix toolbox) also would make sense to me. But then I think, shotwell should be reduced in functionality as just a GUI that uses those tools. But maybe there are no such tools available that cover all needed functionality. Ciao, Oliver _______________________________________________ Shotwell mailing list [email protected] http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
