A user had created a table with a space in the name (I did not even know that was valid SQL) and realtime did not work. Took a while to figure out as this table works in the UI and appears to be valid Postgres. There are no reported realtime errors.
To Reproduce
I reproduced this with just the dashboard UI.
Created a table "My Table" with the table UI. Turn RLS off add to replication.
Use the inspector to connect.
There are no errors and a subscription gets added to the realtime.subscription table.
Insert to table and nothing happens.
Change name to MyTable and reconnect inspector.
Works.
Bug report
Describe the bug
A user had created a table with a space in the name (I did not even know that was valid SQL) and realtime did not work. Took a while to figure out as this table works in the UI and appears to be valid Postgres. There are no reported realtime errors.
To Reproduce
I reproduced this with just the dashboard UI.
Created a table "My Table" with the table UI. Turn RLS off add to replication. Use the inspector to connect.
There are no errors and a subscription gets added to the realtime.subscription table. Insert to table and nothing happens.
Change name to MyTable and reconnect inspector. Works.
Link to help discussion: https://discord.com/channels/839993398554656828/1108567125934735422
Expected behavior
Since it appears table names with spaces are valid Postgres SQL this should work and a minimum it should error if it can't.
Screenshots
System information
Latest everything.