You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
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.
The text was updated successfully, but these errors were encountered: