Replies: 1 comment 4 replies
-
Hi! The table might stay empty, if you don't emit packets whose size is above 8000 bytes or with binary data. Please check https://socket.io/docs/v4/postgres-adapter/#how-it-works |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi guys ^^
I have been swimming across the official SocketIO documentation but... I do not get it. I am working with two separated machines, both connected to another machine with a PostgreSQL DB. When I run SocketIO on the same machine, everything is fine, it works as it has to. I add the adapter and the table creation that the documentation says is all ok. I am using sequelize sooo fine, the table is created and a periodical DELETE and NOTIFY are launched to that table. Oooook. But that table, the place where magic should happen is... dry. There is no data input. NEVER. So the table is always empty and, as I can assume, this is why when I launch the other machine, SocketIO from machine 1 does not link with SocketIO from machine2, each of the machines creates their separate rooms and are never related because the data that has to do it, is not being stored in the DB. Where I am messing up?
Apart from this, I think that it would be appreciated to add more documentation to that PostgreSQL adapter. Such as the one we have with the Redis Adapter. I suppose that the working behind is similar, but for newbies with SocketIO it could help us ^^
Beta Was this translation helpful? Give feedback.
All reactions