Skip to content
This repository has been archived by the owner on Feb 24, 2024. It is now read-only.

Latest docs for 7.0.0 #315

Merged
merged 18 commits into from
Apr 21, 2020
Merged

Conversation

steve-chavez
Copy link
Member

Only the latest feature regarding multiple schemas is missing: PostgREST/postgrest#1450

Ideally a "schema design" section should be added to the best practices page. That way we ensure multiple schemas are not misused. It should be made clear that the use cases are "api versioning with schemas" and "schema-based multitenancy".

@steve-chavez
Copy link
Member Author

For fixing #317, I've omitted talking about pg minimum version in the tutorial(after all we use docker latest version) and instead put a link to the installation page.

Also, I'm kind of discouraging the use of the Prefer: params=multiple-objects because it was discovered that it had bad performance PostgREST/postgrest#1385. I'm advising users to instead use json or array parameters in functions for bulk processing.

@steve-chavez
Copy link
Member Author

I've added a "schema structure" diagram: https://postgrest.org/en/preview/best_practices.html.

Doing a "schema design" section is more of a tutorial, which takes longer. So I'm going to leave it as an explanation.

@steve-chavez
Copy link
Member Author

Ok. This is finished. Merging..

@steve-chavez steve-chavez merged commit 469e01f into PostgREST:master Apr 21, 2020
@steve-chavez
Copy link
Member Author

Left a warning for not misusing the switching schemas feature: http://postgrest.org/en/v7.0.0/configuration.html#db-schema.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant