I stumbled across a weird behavior where I could not use a filter with eq to filter by an IP-Address (e.g. 10.0.0.1).
The generated url for From("Foo").Select("*").Eq("ip", "10.0.0.1").Execute() is /rest/v1/Foo?select=*&vpn_ip=eq."10.0.0.1". As the PostgrestAPI states, when using reserved characters we have to use percent encoded double quotes " for correct processing (Source).
This library correctly identifies the reserved characters and does as the documentation states. Unfortunately the result is always empty.
Using the generated URL in a curl request confirms that an empty result is returned.

Interestingly it is possible to perform following curl request and receiving the expected single result:

/rest/v1/Foo?select=*&vpn_ip=eq.10.0.0.1

Note the missing " or " in the request above.

With some further research I could identify a different behaviour in the official postgrest-js. It appears that not all filters must recognize reserved chars. On first glance it mainly is the in filter.

If you could confirm this @nedpals I could prepare a pull request until next week.

Edit: I would open this issue in the corresponding repository if issues were possible (nedpals/postgrest-go)