Author Topic: can you combine databases?  (Read 3831 times)

0 Members and 1 Guest are viewing this topic.

cthiesen

  • Member
  • **
  • Posts: 2
    • View Profile
can you combine databases?
« on: 2015-12-31 14:05:19 »
I'd like to combine two databases adding their galleries together. Is this possible?

Daan van Rooijen

  • Administrator
  • Sr. Member
  • *****
  • Posts: 938
    • View Profile
can you combine databases?
« Reply #1 on: 2015-12-31 14:55:35 »
> I'd like to combine two databases adding their galleries together. Is this possible?

No, I'm afraid not. Theoratically, if you could manipulate the databases directly (using Access or another tool) and the thumbnails have the same ThumbnailID values, it might be possible - but not from within ThumbsPlus.

If it's important enough to justify the work, you could add a specific keyword to the XMP (IPTC) keywords of the files in a gallery. For instance, if your gallery holds landscape pictures, you give all those images the keyword 'Landscape' (using Image | Batch Edit Metadata). Then you open the database to which you want to move the gallery. You tell ThumbsPlus to copy XMP-keywords into the database when it thumbnails images (Options | Preferences | Keywords). Then you (re)thumbnail the images and you perform a database search for all images with the keyword 'Landscape'. Add all the found images to a new gallery named Landscape and voila, you have moved your gallery to the other database :)
I'm volunteering as a moderator - I do not work for Cerious Software, Inc.

cthiesen

  • Member
  • **
  • Posts: 2
    • View Profile
can you combine databases?
« Reply #2 on: 2015-12-31 15:29:01 »
Thanks very much. That's really helpful.

mschnell

  • Full Member
  • ***
  • Posts: 98
    • View Profile
can you combine databases?
« Reply #3 on: 2016-01-01 06:54:13 »
> Theoratically, if you could manipulate the databases directly (using Access or another tool)

An even nicer way would be to use the possibility to TP's to let the user create and run Python scrips that allow a TP-specific (and hence database engine agnostic) access to the data base.

-Michael