As mentioned in https://github.com/PostgREST/postgrest-docs/issues/249,
the embracing the relational model sectin would better fit in a
page about our REST style.
The shared improvements section no longer seems relevant since
we're already an established open source project.
Release notes are not removed but hidden from the index page.
* /index.rst:24: WARNING: Line block ends without a blank line.
* /install.rst:300: WARNING: Explicit markup ends without a blank line; unexpected unindent.
* /admin.rst:273: WARNING: Could not lex literal_block as "http". Highlighting skipped.
* /tutorials/tut1.rst:150: WARNING: Could not lex literal_block as "json". Highlighting skipped.
* Remove extra newline
* Use integer value as epoch in JSON snippet
Even though using a string value is convenient (due to the lack of JSON
comments), it is confusing since the value should actually be an
integer. A slightly more verbose documentation is therefore preferable.
we've been using PostgREST in internal production
infrastructure at Datrium for a few years now.
so, we're giving thanks in the form of a testimonial,
and providing a link to a python-based postgrest client
we developed and use.
* Updated full-text search
* Calling RPC with GET
* Customizing HTTP status codes and headers
* Move the admin section to bottom of TOC
* Revise JWT signing section of tutorial
* Selecting pkeys in embedding no longer required
Steve Chávez