Garry Hill

@timc3 actually this is currently working. It's a bit awkward and a little unreliable but it works. We're using it more at home at the moment so I'm currently working...

I just got it to run under OS X and it crashed with the following stack trace: ``` Process: node [66906] Path: /usr/local/bin/node Identifier: node Version: ??? (???) Code Type:...

I was just about to add the same bug. Perhaps a .peepopen file in the project root where we could add extra config values?

That would be ace. Would beg for RPi support before windows if it weren't unseemly.

> I'm a bit worried about red elixir tests tho... The next pr in the stack fixes the test failures. Haven't bothered to port those fixes down the stack...

@gorbak25 thanks for the bug report. could you include the sql of the migration please the error message mentions the use of do blocks... the proxy disallows these because the...

@gorbak25 glad you got it to work. The problem with do blocks is that, because they allow for full plpgsql programs, not just sql statements, it's nigh on impossible for...

@kevin-dp I wrote a proper parser for pg table names, including managing case if unquoted etc: https://github.com/electric-sql/electric-old/blob/main/components/electric/lib/electric/postgres/name_parser.ex might be useful. tests: https://github.com/electric-sql/electric-old/blob/main/components/electric/test/electric/postgres/name_parser_test.exs

@kevin-dp awesome regexing. If you've nailed it then no need for the parser, though I always feel safer with a parser personally.

Is there any way we could tag the replication slot with the electric deployment? that way if it sees a replication slot but no active shapes it will know that...