Wolfgang Walther
Wolfgang Walther
That looks cool, I agree. I skimmed through the article and am I confused by the conclusion: > The noinherit setting prevents the authenticator user from automatically assuming all permissions...
Or even better, as mentioned in https://github.com/PostgREST/postgrest/pull/1659#discussion_r528245119 - can we create some kind of demo server that might be connected to the docs in a way, where you can run...
Sweet - it's building both the english and the chinese version for each PR now. Not quite perfect with the naming, yet: ``` docs/readthedocs.org:postgrest — Read the Docs build succeeded!...
> Not sure where we can change that. The second one definitely seems to be built in Chinese, though :) Turns out I had to recreate the project on readthedocs...
Ok, that works. Should be good to merge, but I'll keep this open until @cnyyk has maybe tested it a bit, too, and has something to put in a PR....
See #368, the "where is this located in the docs?" applies here as well. JSON columns can be used for more than vertical filtering, so they should be one level...
Just noticed #355. I missed that.
Also noted this comment: > Computed columns must be created under the exposed schema to be used in this way. This seems to be wrong - I use computed columns...
> I agree. Computed columns should have his own page. It shouldn't be part of API. Hm. Where do you suggest they should go? When I was just looking for...
Ah, I see where you're coming from. Looking at it this way, I feel like API is indeed a bit long. What do you think about a split across the...