Julien Goux
Julien Goux
@lfittl libpg-query-node seems to rely on [pg_query_parse](https://github.com/pyramation/libpg-query-node/blob/v15/src/sync.cc#L8). Reading the [tests](https://github.com/pganalyze/libpg_query/blob/15-latest/test/deparse.c#L51) of libpg_query it doesn't seem possible to pass the result of pg_query_parse to `pg_query_deparse_protobuf` right? So I'm wondering why is...
I guess what I want is the equivalent of `pg_query_parse` for `pg_query_deparse`, working with json instead of protobuf to pass the parsetree: https://github.com/pganalyze/libpg_query/blob/1ada550d901ed4edbfb6bce2163d21f4b948ab2d/src/pg_query_parse.c#L101
Just so I'm sure I'm understanding how the protobuf work impacts the consumption of libpg_query. Is it an implementation detail? For example, if I would like to expose `pg_query_parse_protobuf` and...
Excellent, exactly what I was looking for, thanks for the pointer @lfittl! 😄
> this feature will be very useful, I have users list in a remote source ( restful api ) I can create query action to get the data to hasura...
It's to help the developer get a unique entity efficiently without errors as all these columns are indexed. You don't have to know by heart the unique columns, the types...
Seems like it's not blocked anymore! https://github.com/microsoft/playwright/issues/7121#issuecomment-1009140849 🎊
@privatenumber is there anything I can do to move this forward? 🙏
> Sorry, I work on tsx on my spare time and I haven't had much lately. Hope to find some time to catch up on the issue and PRs in...