Sam Willis

I like this. There is another option in this situation (that we use in linearlite) that we need to document better. You can create the liveQuery in the React Route...

Hey @lucasgelfond As you have spotted best way to solve this import is using the `COPY` command with `/dev/blob/`, and constructing a CSV for Postgres to import from. You will...

@treetopdevs we have an example here where we copy to a css and back again: https://github.com/electric-sql/pglite/blob/main/packages/pglite/examples/copy.html

Thanks for finding this @AntonOfTheWoods!

I had a chat with @msfstef on this, It's one of those areas that React can have many foot guns... In general when an array or an object is passed...

I want to just clarify that Postgres *isn't* case insensitive, that would imply that a table created with: ```sql CREATE TABLE "MyTable" ( .... ) ``` was queryable with: ```sql...

Yes, I think we should be case sensitive. With the proposed fix, and the case from the top of this issue (CamelCase table name) the user would have to use...

The `live.query()` api excepts both optional arguments of a single options object arguments: https://github.com/electric-sql/pglite/blob/0c7454d1cef9725c6dc3f1e26352016c6145c3be/packages/pglite/src/live/interface.ts#L29-L51 `useLiveQuery` also has multiple call signatures: https://github.com/electric-sql/pglite/blob/0c7454d1cef9725c6dc3f1e26352016c6145c3be/packages/pglite-react/src/hooks.ts#L101-L112 although not a option arg one. Maybe we should...

I'm tempted to suggest the solution here would be to vendor pg-protocol into the pglite package. We may want to fork pg-protocol anyway and convert it to use ArrayBuffers, rather...

Hey, yes we 100% want to support pg_search, it's perfect for the embedded FTS use case. We've not yet tackled any pgrx (Rust API for Postgres extensions) based extensions, but...