ExportToDatabase doesn't respect metadata when specifying file output location

[bethac07]

In ExportToDatabase, at least with the 'SQLite' option, if you use a piece of metadata in the 'Ouput file location' box (either as 'Elsewhere' or one of the subfolder options), it doesn't actually use the metadata that you give it- ie if all of the images in my image set have an extracted piece of metadata called 'SubfolderName' with a value of 'Subfolder1' , and I set my 'Output file location' as Default Output Subfolder -> 'SubfolderName', the .db is created in the Default Output Folder, not Default Output Folder/Subfolder1. Subfolders DO otherwise work fine as long as it's just a text value and not a piece of metadata.

I can pretty easily understand why this might be (CP isn't going to assume all images have the same metadata, so it wants a universal place to put the images), but if the metadata isn't used we shouldn't let it be specified.

[braymp]

Duplicate of #1276?

[bethac07]

Related but not sure if duplicate- this is for SQLite, which should be being written at the beginning not in post_run (I think). I think just removing Metadata based specification from that module entirely is probably the best solution.

[bethac07]

Ability to specify locations based on metadata will be removed in 3.0

[mcquin]

Closing in favor of #2702