postgrest-docs issues

Add note about not lowercasing on configuration

Feedback on https://gitter.im/begriffs/postgrest?at=5da44295dbf676673458f655. Most pg users would expect we lowercase I think. Add this as a note.

steve-chavez

references

Note about quoting on curl

3

In bash a request that includes `&` must be quoted: ```bash curl "http://localhost:3000/rpc/add_them?a=1&b=2" ``` Otherwise, on `&` it'll run curl as a background process. Related to https://github.com/PostgREST/postgrest/issues/1107.

steve-chavez

reserved characters section in docs could use some clarification

1

### Environment * PostgreSQL version: 10.10 * PostgREST version: 6.0.0 * Operating system: Linux ### Description of issue I find the [documentation on escaping reserved characters](http://postgrest.org/en/v6.0/api.html#reserved-characters) to be quite confusing....

robx

references

Use more realistic example of custom validation

1

Most people will want to use it for logging users out before their JWT has expired. The current example doesn't correspond to any use case. https://postgrest.com/en/v0.4/auth.html#custom-validation

begriffs

Update "JWT security" section

1

https://postgrest.com/en/v4.4/auth.html#jwt-security It still talks as if asymmetric keys are not supported.

begriffs

references

document how to insert "weird" data types, that are not just numbers or strings.

5

The documentation doesn't cover how to insert data types that are "weird", things like point() for example, where you have to insert point(lat,long). It would be great if pgrest could...

zieone