postgrest-docs
postgrest-docs copied to clipboard
This repo is archived and will be merged into postgrest/postgrest soon.
As #393 recently got some traction, I'm adding support for translations to our build tools. The main features are: - `postgrest-docs-build` will now update `.po` files' msgids automatically. - `postgrest-docs-build`...
Reported to not be visible enough in https://github.com/PostgREST/postgrest/pull/1659#issuecomment-1056043108 Perhaps we need a more focused section about transactions, [this section](https://postgrest.org/en/latest/api.html#immutable-and-stable-functions) mentions transaction but it's mixed with functions.
https://postgrest.org/en/stable/development.html?highlight=alpine#build-from-source Do we know if this is still an issue? Is it referenced anywhere in another issue tracker? I'd be happy to try building it myself on alpine and run...
Since the introduction of [Multiple Schemas](https://postgrest.org/en/stable/api.html#switching-schemas) we no longer have a single schema cache, so the term "schema cache" is not apt anymore. Also, seems it can confuse users to...
We currently make a GET call thats works fine with small query, but the issue is when the query is too long its not able to handle. So i want...
Could include: - The old timescale doc https://postgrest.org/en/v5.2/integrations/timescaledb.html. - The pgbouncer section: https://postgrest.org/en/v8.0/admin.html#using-external-connection-poolers - Greenplum: https://github.com/PostgREST/postgrest/issues/2021#issuecomment-977693580
### Discussed in https://github.com/PostgREST/postgrest/discussions/2090 Originally posted by **skrick** November 18, 2021 What is the "best" way to configure swagger to work with postgrest. I have tried to use docker to...
Follow up on #375. Background: We had a semi-finished translation for chinese in the past. However, this was in a different repo and therefore hard to keep up to date....
While hacking on https://github.com/PostgREST/postgrest/pull/2112 I noticed the following: Our IO tests expect `SIGUSR1` to reload the schema, but not the config files - and therefore not reload the `@/external_file` for...
Having VOLATILE functions can have performance impacts. See https://github.com/PostgREST/postgrest/issues/1378#issuecomment-532354989. Not sure for now where would this go, perhaps a best practices explanation. (Recommend to use STABLE/IMMUTABLE where possible)