Feature request #15925
External resource: being able to store more than one file (photo) in the same field (with possible preview)
| Status: | Closed | ||
|---|---|---|---|
| Priority: | Normal | ||
| Assignee: | - | ||
| Category: | Edit widget | ||
| Pull Request or Patch supplied: | No | Resolution: | wontfix |
| Easy fix?: | No | Copied to github as #: | 23842 |
Description
I'm exploring the external resource widget in order to store photos in a field. Very handy! Thanks for this.
Sometimes, I find that I have more than one photos that sound interesting to keep for a given feature. But it doesn't make sense to create another field.
What about a new feature that helps to store in the same field many resources (not always the same number per features): a kind of comma-separated list of photos path that could however be previewed in the feature form.
History
#1
Updated by Nyall Dawson almost 8 years ago
Harrissou,
I believe this use case is better addressed by creating a separate child table for photos and setting up a 1 to many relation between the layers. This setup is already fully supported in QGIS.
#2
Updated by Harrissou Santanna almost 8 years ago
Good point, Nyall. I need to rethink my DB structure if I really want to store more than one file.
Btw, I was planning to test and update 1-n (or n-m) relation documentation but didn't have data. It seems that i have a good case now.
Is it worth keeping this request opened?
#3
Updated by Nyall Dawson almost 8 years ago
- Resolution set to wontfix
- Status changed from Open to Closed
I don't think so