Bug report #11932
update selected features via field calculator doesn't work properly
Status: | Closed | ||
---|---|---|---|
Priority: | Severe/Regression | ||
Assignee: | - | ||
Category: | Data Provider/PostGIS | ||
Affected QGIS version: | master | Regression?: | No |
Operating System: | Easy fix?: | No | |
Pull Request or Patch supplied: | No | Resolution: | |
Crashes QGIS or corrupts data: | No | Copied to github as #: | 20140 |
Description
Hi there!
I have a problem on QGIS 2.6 (Windows/Ubuntu) with updating selected features via field calculator on PostgreSQL 9.3 (Postgis 2.1) tables/layers when I logon as other that 'postgres' account. If I log into PostgreSQL database as another user (but superuser) QGIS doesn't apply changes made in field calculator (update existing field for selected features). If I logon as postgres user everything works fine. I thought that is problem with privileges on my database but in QGIS 2.2 it works properly. Can you check this and let us know if something change in QGIS or it is something wrong on my configuration.
Happy New Year!
Cheers.
Related issues
Associated revisions
fix field calculator when update are allowed and add attribute is not (fixes #11932)
History
#1 Updated by Seb Radzimski almost 10 years ago
- Target version set to Version 2.8
OK, I figured out that is the same bug that was found in QGIS 1.8 (confirmed with Borys Jurgiel), where only owner of a table in postgresql database was able to do any changes using field calculator. It was fixed in QGIS 2.0 but now it is back.
Will it be fixed (again) in next QGIS? Please :)
Thanks!
#2 Updated by Giovanni Manghi almost 10 years ago
- Affected QGIS version changed from 2.6.0 to master
- OS version deleted (
7,8/12.04) - Priority changed from Normal to Severe/Regression
- Category changed from Attribute table to Data Provider/PostGIS
- Operating System deleted (
Windows/Ubuntu)
Confirmed here, the not owner (but with "GRANT ALL") was certainly allowed to update columns in qgis 2.0.1/2.2 but in later releases stopped to work correctly.
#3 Updated by Jürgen Fischer almost 10 years ago
- Status changed from Open to Closed
Fixed in changeset 3294505861afae594c4d19b9a876c10067c71944.