You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
by default doesn't include SELECT. Adding SELECT (in two places) makes it so it at least returns results.
Problem code is here, where they note it as seemingly an anomaly.
IRC says:
erichanson | I'm trying to create a read-only user, but that user is unable to see primary
| keys via information_schema.table_constraints. tracked down the reason here:
| shorturl.at/fjET0 . SQL Standard requires the user has_table_privilege() of
| something *other than* select. Anybody know the rationale behind this?
erichanson | I can just dig it out of pg_catalog but it's not going to be pretty and is a lot
| more fragile to version changes etc.
erichanson | They even note it in the comments, as if it were an oddity, which it seems to be
RhodiumToad | the thinking (as far as I can tell) behind the access restrictions in
| information_schema is that you're supposed to be able to see stuff that might
| affect you, and not otherwise
erichanson | Ah. As in if I can't insert, there's no point in knowing about constraints
RhodiumToad | so you don't see constraints unless you have permissions that you might violate
| them with
RhodiumToad | or something.
erichanson | Gotcha. Well, disagree, but thanks for the explaination :)
* | RhodiumToad has a fairly low opinion of the spec
erichanson | ^^
Going to have to work around this somehow.
The text was updated successfully, but these errors were encountered:
is always empty. Which means
meta.untracked_rows
is always empty.Tracked this down to information_schema.table_constraints, which is empty because
by default doesn't include SELECT. Adding SELECT (in two places) makes it so it at least returns results.
Problem code is here, where they note it as seemingly an anomaly.
IRC says:
Going to have to work around this somehow.
The text was updated successfully, but these errors were encountered: