Chase Granberry

@mlanza this looks to be more walrus related so I'm going to close it. If you have any more related issues please feel free to re-open.

Hey all ... I've been changing the system messages. Sorry! I didn't realize people were matching on that and assumed if you were you'd match on the `status`. It's in...

Update: this should be much better in 99% of connections! Just pushed to prod. If zero users are listening for db changes it will take a couple seconds, as the...

> we're running into a situation where the subscription isn't truly returning events until the second message containing the message "Subscribed to PostgreSQL" comes in Yes, this is by design...

@GaryAustin1 hmm, I don't think it should be doing that. Can you [check your Realtime logs](https://app.supabase.com/project/_/logs/realtime-logs) or dm me your project id?

Actually, double checked that's all fine, although it feels like it should really send just one when it connects.

Closing. Working on Workflows somewhere else now. To be announced!

Yeah we should do this.

Feel free to take a look at our parser: https://github.com/Logflare/logflare/blob/master/lib/logflare/logs/lql/lql_parser.ex We actually compare the path with a schema and alert if the path is not found ... what you're talking...

We have this now, and will expand on it in the docs shortly. Added two new issues for the warnings you suggested which we should definitely do.