-
Notifications
You must be signed in to change notification settings - Fork 29
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
Feature Request: LISTEN support (ie. NotificationResponse) #62
Comments
Thanks for the feedback. I'm happy to take patches - but I am not planning on adding this at the moment. Good point about the connection pools and listen. I guess you'd always want to have a separate connection (not from a pool) open to handle listen responses. |
Thank you for the package, it's very helpfull, |
Yet another +1 for this feature request. |
I've forked and added support for retrieving Notifications. |
Wouldn't a Stream based API be more suiteable for Dart? |
It would, but I haven't found a way to have the PostgreSQL connection just give you the received pending notifications without "asking" for it. |
the _MSG_NOTIFICATION_RESPONSE is defined in the code, but the message type is not implemented.
There are a few ways to implement this, but simply providing a conn.listen("channel") that returns a stream seems the most obvious and idiomatic to me. the postgres listen command operates 'per-connection' and doesn't block, so I'm not sure how this would interact with pools (if at all).
The text was updated successfully, but these errors were encountered: