Laurence Isla

> The error message should come from postgresql and should be like: For this case I think the error should be returned by the parser. The one you mention about...

I tested adding `to_tsvector` to this line: https://github.com/PostgREST/postgrest/blob/115dae748463287ec4fff7da1cedc982411450d0/src/PostgREST/Query/SqlFragment.hs#L258 Result: ```haskell pgFmtFieldFts op = "to_tsvector(" pgFmtField table fld ")" " " SQL.sql (ftsOperator op) ``` This breaks all the `fts` tests...

> With the implementation in this PR, the ability to do column to column matches will be lost, right? Yes. It was one of the reasons I turned this into...

> I guess it's debatable whether this is a bug or not. [According to the docs](https://postgrest.org/en/v9.0/api.html#calling-functions-with-a-single-json-parameter), `Prefer: params=single-object` works with a function with a single json parameter, not with functions...

> I don't disagree, but do note even with the current behaviour you won't be "guaranteed" to call that function since the query will crash before the function is invoked!...

> but we should have something like: > > ``` > "/users": { > "get": { > "parameters": [ > { > "$ref": "#/parameters/rowFilter.users.lastname.eq" > }, > { > "$ref":...

Closed in favor of https://github.com/PostgREST/postgrest/pull/2724

> From a conceptual point of view (the REST one), those `items` you refer to should be different concepts. The correct db design for that is to have only one...

@taimoorzaeem [According to MDN]( https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Origin), you'll need to: > Limiting the possible Access-Control-Allow-Origin values to a set of allowed origins requires code on the server side to check the value...

An idea for `--example`: maybe adding parameters could get different configs, e.g. `--example CONFIGTYPE`, where `CONFIGTYPE` may be one of `'file', 'env', 'db'` or something like that.