Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

External resource: being able to store more than one file (photo) in the same field (with possible preview) #23842

Closed
qgib opened this issue Dec 1, 2016 · 3 comments

Comments

@qgib
Copy link
Contributor

qgib commented Dec 1, 2016

Author Name: Harrissou Santanna (@DelazJ)
Original Redmine Issue: 15925

Redmine category:edit_widget


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.

@qgib
Copy link
Contributor Author

qgib commented Dec 1, 2016

Author Name: Nyall Dawson (@nyalldawson)


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.

@qgib
Copy link
Contributor Author

qgib commented Dec 1, 2016

Author Name: Harrissou Santanna (@DelazJ)


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?

@qgib
Copy link
Contributor Author

qgib commented Dec 1, 2016

Author Name: Nyall Dawson (@nyalldawson)


I don't think so


  • resolution was changed from to wontfix
  • status_id was changed from Open to Closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant