Hi!
I'm new to Jooq and have been playing around with the Jooq code-generation 
for a while now. My initial attempts with the code-genration worked just 
fine, using the Postgres role owning the database in question. 
Since the code-generation eventually will end up in source code, I did not 
like the idea of exposing the credentials of a Postgres role having 
privileges to modify the database (or even the rights to look at table 
contents) though. I'd like to run the code-generation with a role 
restricted to read-only access to Postgres table meta-data only.

This sounds like a natural and basic requirement to me, but I have a really 
hard time finding any kind of information "in the right direction". I found 
nothing in the Jooq documentation. I tried to run the code-generation using 
a Postgres role having no access to the database in question (yes, such a 
role can see the table meta-data but not the table contents -- you can try 
it with psql), but the code-generation acted like there was nothing in the 
database at all (no "access denied" message or similar).

How do you all handle this? Are you happy exposing fully privileged roles?

-- 
You received this message because you are subscribed to the Google Groups "jOOQ 
User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jooq-user/addb9716-6373-4ed4-81d6-a9ab225f5e3en%40googlegroups.com.

Reply via email to