I know, you should care about permissions in postgres directly. But introducing blacklists can prevent some issues with conflicts. It should be good to report this in log as notice level in development but definitely this can workaround some human talks.
It can open next level-mapping of generated name to customized one. This can be used as transition thing too.
langpavel
All 8 comments
Hi @langpavel, what is it you wish to blacklist - is it the role?
benjie
on 27 Mar 2017
Hi @benjie
I want blacklist (or whitelist) every object which can be reflected by postgraphql.
There are some hardly resolvable issues with name clashing which can be resolved only by changing database.
For example, if you try fresh (empty) PostGIS database, reflection will fail..
langpavel
on 30 Mar 2017
I'd recommend using schemas to avoid that issue, however you could do it by hacking the introspection query:
Alternatively you could doctor the PgCatalog and feed it back in, based on the work in this PR:
benjie
on 30 Mar 2017
I didn’t think about manually mutating PgCatalog, or creating your own with a custom introspection query. That’s an interesting and powerful idea.
@langpavel if you try that please let us know how it turns out 👍
calebmer
on 1 Apr 2017
Actually I tried something similar some weeks ago but it is easier to filter out introspection query because of too tight internal logic.
langpavel
on 2 Apr 2017
Does modifying the introspection query and/or its results work for you?
calebmer
on 3 Apr 2017
In PostGraphQL v4 you'll be able to replace the introspection plugin with your own:
benjie
on 9 Jul 2017
You can now use the @omit smart comment to blacklist tables / columns / functions / etc: https://www.graphile.org/postgraphile/smart-comments/
benjie
on 24 Jun 2018
Related issues
angelosarto
·
3Comments
ssomnoremac
·
5Comments
jayp
·
3Comments
jwdotjs
·
5Comments
calebmer
·
3Comments