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: Tom Joseph (Tom Joseph)
Original Redmine Issue: 6143
Affected QGIS version: master
Redmine category:vectors
There is no update existing field option available for a postgis vector layer when not logged on as the table owner.
After a quick scan of qgsfieldcalculator.cpp (line 46-51) I see that if the data provider does not support field addition it disallows existing field edits with mUpdateExistingGroupBox->setCheckable( false );. Should that not read mNewFieldGroupBox->setCheckable( false ); ?
Expected result - Limit some users to only update data and not the ability to create new fields. Editing data for these users works as expected using the attribute form on an individual features but not multiple row updates in the Field Calculator.
Related issue(s): #15459 (duplicates)
Redmine related issue(s): 6120
The text was updated successfully, but these errors were encountered:
qgib
added
Bug
Either a bug report, or a bug fix. Let's hope for the latter!
Vectors
Related to general vector layer handling (not specific data formats)
labels
May 24, 2019
Author Name: Tom Joseph (Tom Joseph)
Original Redmine Issue: 6143
Affected QGIS version: master
Redmine category:vectors
There is no update existing field option available for a postgis vector layer when not logged on as the table owner.
After a quick scan of qgsfieldcalculator.cpp (line 46-51) I see that if the data provider does not support field addition it disallows existing field edits with mUpdateExistingGroupBox->setCheckable( false );. Should that not read mNewFieldGroupBox->setCheckable( false ); ?
Expected result - Limit some users to only update data and not the ability to create new fields. Editing data for these users works as expected using the attribute form on an individual features but not multiple row updates in the Field Calculator.
Related issue(s): #15459 (duplicates)
Redmine related issue(s): 6120
The text was updated successfully, but these errors were encountered: