-
-
Notifications
You must be signed in to change notification settings - Fork 120
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
No notifications received with Postgres as backend #53
Comments
Is this tool still under development? Hope to get some response. |
@wkamer, it's worse than that, the maintainers don't even have the respect to put a message in the readme saying that it is no longer under development, in spite of lots of people submitting issues and PRs... |
Hi folks - if you've a PR that you'd like to see merged that's currently blocked then let me know and I can add you to the maintainers team. @wkamer - Don't know - I'm not currently using broadcaster myself, so depends if anyone in the community who's currently using broadcaster w/ postgres is able to chime in on the thread? (Or else whatever you're able to dig into yourself and fill in on, here.) |
I'm using broadcaster with Redis backend and it works fine, but AFAIR that's only backend that does. Something is very wrong with our tests suite IMHO. It's supposed to test other backends like memory, Kafka and PostgreSQL and tests for those pass, but in real world suddenly they don't. |
Closing as stale. |
I'm trying to get broadcaster work with FastAPI and a PostgreSQL database with notifications enabled.
Here is the code I use
FastAPI (test_broadcaster.py)
FastAPI (router.py)
PostgreSQL (trigger name) # on the table account
account
PostgreSQL (trigger_function)
When making the websocket connection connection and update the table to trigger a notification, nothing happends. Also not when using
When changing to Redis it is working flawless, from Redis to websocket and websocket to Redis.
Is this a bug? Or I'm missing something in the code?
The text was updated successfully, but these errors were encountered: