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

QgsProject Notify/Listen #29208

Open
qgib opened this issue Feb 26, 2019 · 0 comments
Open

QgsProject Notify/Listen #29208

qgib opened this issue Feb 26, 2019 · 0 comments
Labels
Data Provider Related to specific vector, raster or mesh data providers Feature Request

Comments

@qgib
Copy link
Contributor

qgib commented Feb 26, 2019

Author Name: Raul Sangonzalo (Raul Sangonzalo)
Original Redmine Issue: 21391

Redmine category:data_provider/postgis


At the moment, the only way to "LISTEN" to postgres database is through QgsProvider or QgsMapLayer. This inevitably needs to target a layer. It would be nice if the project itself (QgsProject) could be set up to listen to postgres and its respective signals.

The reason behind is that I have several plugins with different tables (task allocation, chat, notifications) with loaded layers (with set notify, refresh and repaintRequested) and signals, that leaves me with 3 permanent established connections to postgres.

The only solution I can think of at the moment is to create a single table that stores my notify signals in postgres and use it to spread the signals in Qgis. However, this is a dodgy solution, so having the project to listen would open up a new world of possibilities, in my opinion.


Also, the class QgsMapLayer contains 3 typos("Nofify"? -> setRefreshOnNofifyMessage, mIsRefreshOnNofifyEnabled, mRefreshOnNofifyMessage

Many thanks.

@qgib qgib added Feature Request Data Provider Related to specific vector, raster or mesh data providers labels May 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Data Provider Related to specific vector, raster or mesh data providers Feature Request
Projects
None yet
Development

No branches or pull requests

1 participant