David E. Wheeler
David E. Wheeler
Got it, thanks. Probably doesn't make much difference for selecting `jsonpath`, because it's encoded as text either way. But I would assume there could be some saved overhead by passing...
> The binary format for input is the same version prefixed text format as for output. So I don't think it would make any difference. Oh does it parse the...
> Oh does it parse the binary input? I thought uploading the binary would skip the parsing. Oh, maybe not, because it has to parse the binary version into its...
I've just found that Yugabyte uses different OIDs for its `jsonpath` types. Is this the best way to add them: ```go config.AfterConnect = func(ctx context.Context, c *pgx.Conn) error { //...
Fun reason to use `variadic pair[]` ([pair](https://pgxn.org/dist/pair/doc/pair.html))? ```sql SELECT function_settings_are( 'myfunc' , array['int','int'], 'search_path ~> 'pg_catalog', 'enable_indexscan' ~> 'off' ); ``` (Only half joking)
Yeah, that looks like other stuff we have now.
Sad to see this still in v0.12.1: ``` warning: unused import: `std::error::Error` --> src/lib.rs:303:9 | 303 | use std::error::Error; | ^^^^^^^^^^^^^^^^^ | help: if this is a test module, consider...
Oooh! So weird it didn't happen in v0.11.x… I'll take look, thanks.
Okay, that worked, but it took some fiddling. Looks like `#[pg_schema]` _only_ works for a module named `tests`, is that right?
Fixed in tembo-io/pg-jsonschema-boon#5.