| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Neeraj M R <neerajmr12219(at)gmail(dot)com> |
| Cc: | Bryn Llewellyn <bryn(at)yugabyte(dot)com>, Tom Lane PostgreSQL <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general list <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Restricting user to see schema structure |
| Date: | 2022-05-13 05:08:51 |
| Message-ID: | CAKFQuwa+6RUXGfmEvX6Cc+-8QSXcgEG5Guku3URwtDXeRDCuWg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thursday, May 12, 2022, Neeraj M R <neerajmr12219(at)gmail(dot)com> wrote:
>
> Thanks for your suggestions, I would like to define my problem a little
> more.
>
> I am using pgAdmin
>
> Is there any way I can completely hide schema1 from the new user.
>
pgAdmin is a separate project. You may get a response here but they do
have their own list as well as documentation. It would be a purely UX
thing though, a user who wants to see the object in schema1 can choose to
do so manually.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bryn Llewellyn | 2022-05-13 05:13:40 | Re: Restricting user to see schema structure |
| Previous Message | Bryn Llewellyn | 2022-05-13 05:06:21 | Re: Deferred constraint trigger semantics |