Initially PostgREST appears awesome. But then we see that the documentation is lacking and also missing a real world example repository. 1. I was not able to find a *recent* example repository with lots of migrations, views, functions. In GitHub discussions, the suggestion from owner for migrations was to package as PG EXTENSION. But again no example repository. 2. An example of how devops will look like is missing. 3. If the developer also needs to access DB, now [s]he needs ORM code which has to kept in sync with table schema created from migrations (sqitch sql scripts for row level security with policies). Or is it like the developer should always use the postgrest http client and never touch DB directly.
Thanks Ian, I'd looked at and liked the look of postgrest. Your video sells it to me !
I'm glad, it's awesome!
Initially PostgREST appears awesome. But then we see that the documentation is lacking and also missing a real world example repository.
1. I was not able to find a *recent* example repository with lots of migrations, views, functions. In GitHub discussions, the suggestion from owner for migrations was to package as PG EXTENSION. But again no example repository.
2. An example of how devops will look like is missing.
3. If the developer also needs to access DB, now [s]he needs ORM code which has to kept in sync with table schema created from migrations (sqitch sql scripts for row level security with policies). Or is it like the developer should always use the postgrest http client and never touch DB directly.
Interesting, is it exposing swagger ui like ?
Nope, no UI - just the OpenAPI spec if read access is enabled.