| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Yogesh Mahajan <yogesh(dot)mahajan(at)enterprisedb(dot)com> |
| Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
| Subject: | Re: Regarding feature #3319 |
| Date: | 2025-03-13 11:07:05 |
| Message-ID: | CA+OCxoz8Yn3AkZ-OjX3==-qwiazZDdpvwUuh6_TFNuxeov3yhQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
On Tue, 11 Mar 2025 at 08:31, Yogesh Mahajan <
yogesh(dot)mahajan(at)enterprisedb(dot)com> wrote:
> Hello Team,
>
> Couple of more questions arose during discussion -
>
> 1.What all tools should we reopen while restoration? It could be Query
> tool, ERD, Psql, Schema diff as of now may get additional in future.
>
Yes :-). Ideally, as much of the original state as possible should be
restored.
> 2.Can we use an existing crypt key to encrypt the query data or simply
> json encoding should be enough?
>
We're already storing the query history, so we should follow the precedent
there.
--
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://www.postgresql.org
pgEdge: https://www.pgedge.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aditya Toshniwal | 2025-03-13 11:07:07 | Re: Role based access control discussion |
| Previous Message | Dave Page | 2025-03-13 10:57:23 | Re: Role based access control discussion |