Laurence Isla
Laurence Isla
@thomasdohyunkim AFAIK this is already implemented on a pre-release, but there's an issue with the clarity of the queries as Steve mentioned [above](#issuecomment-1361775232). Here's an example on [how to use...
> you would tell me to use this sentence i suppose : `GET /table1?select=*,table2(*)&table2.or=(fieldD.eq.thing,fieldE.eq.thing)` @Etwenn Yes, and if you need to exclude the null embeddings ([top level filtering](https://postgrest.org/en/stable/references/api/resource_embedding.html#top-level-filtering)), add `!inner`...
This PR changes the logic used for bulk deletes that was specified in https://github.com/PostgREST/postgrest/pull/2355#issue-1291906948. As it is mentioned in https://github.com/PostgREST/postgrest/issues/2314#issuecomment-1428792805, bulk deletes could also use the same header as bulk...
Maybe this is related and should be added to the docs too. From this discussion https://github.com/PostgREST/postgrest/discussions/3466#discussion-6588261: > ```bash > curl --globoff 'http://example.com/table?select=*&and=(column->jsonlist.cs.["foo=()"]' > ``` > > results in > >...
It looks like it comes from the `LibPQ` library. It can be traced first in [the `hasql-notifications` code](https://github.com/diogob/hasql-notifications/blob/8bf5ba4b9d475cb99d4876901961c46b18d1270a/src/Hasql/Notifications.hs#L174). I used `Debug.Trace` to check exactly where this happened: ```haskell import Debug.Trace...
> I don't understand what that means. You are proposing to merge this into v12, which was exactly the plan, right? What am I missing? No, no, there shouldn't be...
> I'm not sure what you mean by force pushing the main branch - but I don't ever want to do that. Maybe there is a mis-understanding. Ah cool, I...
@wolfgangwalther Great job on the new release workflow, it's looking great! > We can merge this into v12 when pipelines pass - this should then kick off the new release,...
> But GHC_VERSION is not $GHC_VERSION - and thus ghcup was always throwing errors when trying to install that literal GHC_VERSION string. Ooph, nice catch. > If you happen to...
It was GHCup itself that had GBs of tmp files while installing, I think both CI jobs for `main` and `v12.0.3` collided in installing their GHC versions. Anyways, I nuked...