Limit the Connections Pane to only what the end-user has access to

[edgararuiz]

Passing on a request to have the Connections Pane to only show the schemas and tables that the user has access to. This is more likely not something that the package can do. The idea is to use this Issue to track the discussion and its resolution. This will allow us to come back to this Issue when other users request this same feature.

[sendakil]

We've this issue and are looking for solution. Appreciate if we can get some update on the progress of this issue.

[ThomasSoeiro]

I missed this issue when I created #605 a few month ago... @ronblum then created rstudio/rstudio#13672 for RStudio.

[hadley]

@ThomasSoeiro just to be clear, you're saying that in Oracle, each user gets a schema, and that's where you can find all the tables that you can access? Do you ever use another schema? Do you ever use catalogs? Can you point to some docs that we can link to remind ourselves of this structure in the future?

[ThomasSoeiro]

@hadley

I am far from an Oracle expert, but AFAIK:

• yes, each user gets a schema
• users can be granted access to tables outside of their schema (probably the tricky part to design the ideal interface...)

From the Introduction to Oracle Database:

In Oracle Database, a database schema is a collection of logical data structures, or schema objects. A database user owns a database schema, which has the same name as the user name.

See also Difference between database vs user vs schema and Difference between a user and a schema in Oracle?.

[hadley]

@ThomasSoeiro how about catalogs? How common is it to use a database in a different catalog?

[ThomasSoeiro]

@hadley Oops, sorry, I missed this one.

AFAIK, there is no catalog in Oracle. See, e.g., Relationship between catalog, schema, user, and database instance.

[hadley]

Thanks, that's very useful.