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

A table with a space in the name will not work with realtime with no errors. #595

Open
GaryAustin1 opened this issue May 18, 2023 · 2 comments
Labels
bug Something isn't working

Comments

@GaryAustin1
Copy link

Bug report

  • [x ] I confirm this is a bug with Supabase, not with my own application.
  • [x ] I confirm I have searched the Docs, GitHub Discussions, and Discord.

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

image
image

System information

Latest everything.

@GaryAustin1 GaryAustin1 added the bug Something isn't working label May 18, 2023
@ghenry
Copy link

ghenry commented Jun 16, 2023

Is this still outstanding?

@GaryAustin1
Copy link
Author

Yes, just had a user hit now in Discord.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants