Raminder Singh
Raminder Singh
I tried with curl with the same result. If PostgREST is not stripping custom headers then it could be some other proxy or gateway along the route.
I sent the request using GraphiQL and then from the browser dev tools copied it as a curl command using the "Copy as cURL" context menu option. Here's the command...
That is a valid approach to follow as per the spec. See [Field Selection Merging](https://spec.graphql.org/October2021/#sec-Field-Selection-Merging) and [Field Collection](https://spec.graphql.org/October2021/#sec-Field-Collection) for details.
I tried the same example above so see what other tools do. PostGraphile emits the following type: ```graphql type DomainTest { id: Int! intField: Int arrayField: [Int] posInt: PosInt nonEmptyArray:...
@pawarren this hasn't been implemented yet.
Hi @ncrmro, Computed field functions written in SQL should be marked volatile to avoid stale results from mutations. This is a direct consequence of Postgres volatility category behaviour. Quoting from...
Thanks @PhilippS93 for reporting, I'm looking into this to pinpoint which commit introduced the performance problem.
Hey @PhilippS93 we have tracked the cause of the slowdown to PR #472 which we have reverted for now. This PR implemented a feature to merge duplicate fields in queries...
@bryanmylee could you please raise a ticket for this. v1.5.1 is already released on GH but is not yet part of our Postgres image so I'll manually upgrade your project...
@bryanmylee was the upgrade done for you? If not, can you please share the ticket id and I'll take a look.