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: Borys Jurgiel (@borysiasty)
Original Redmine Issue: 16432
Redmine category:data_provider
Once you load e.g. postgis table into QGIS, there is no way to reload its fields (e.g. after adding a column via psycopg or other concurrent connection), except reloading the whole project of course. The layer.dataProvider().forceReload() assumes the fields structure is constant and only reloads the records.
I noticed it when working with PostGIS, but I suspect it's a provider-independent issue.
The text was updated successfully, but these errors were encountered:
description was changed from Once you load e.g. postgis table into QGIS, there is no way to reload its fields (e.g. after adding a column via psycopg or other concurrent connection), except reloading the whole project of course. The layer.dataProvider().forceReload() assumes the fields structure is constant and only reloads the records.
I noticed it when working with PostGIS, but I suspect it's a provider-independent issue. to Once you load e.g. postgis table into QGIS, there is no way to reload its fields (e.g. after adding a column via psycopg or other concurrent connection), except reloading the whole project of course. The layer.dataProvider().forceReload() assumes the fields structure is constant and only reloads the records.
I noticed it when working with PostGIS, but I suspect it's a provider-independent issue.
Author Name: Borys Jurgiel (@borysiasty)
Original Redmine Issue: 16432
Redmine category:data_provider
Once you load e.g. postgis table into QGIS, there is no way to reload its fields (e.g. after adding a column via psycopg or other concurrent connection), except reloading the whole project of course. The layer.dataProvider().forceReload() assumes the fields structure is constant and only reloads the records.
I noticed it when working with PostGIS, but I suspect it's a provider-independent issue.
The text was updated successfully, but these errors were encountered: