| From: | Yogesh Mahajan <yogesh(dot)mahajan(at)enterprisedb(dot)com> |
|---|---|
| To: | Dave Page <dpage(at)pgadmin(dot)org> |
| Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
| Subject: | Re: Regarding feature #3319 |
| Date: | 2025-03-13 11:20:10 |
| Message-ID: | CAMa=N=PmMgwfu034PK3ggxuzPKp_J=p5rPR9x+Xo=qYAW2XabQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
Hi Dave,
Couple of follow up questions -
Thanks,
Yogesh Mahajan
EnterpriseDB
On Thu, Mar 13, 2025 at 4:37 PM Dave Page <dpage(at)pgadmin(dot)org> wrote:
>
>
> 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.
>
So, should we open the psql without data and schema diff without comparison
results?
Also for the query tools open with an ad-hoc server, should we just open a
query tool with data without connections?
>
>> 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.
>
Currently we are storing this data with json encoding done by the
request module.
> --
> Dave Page
> pgAdmin: https://www.pgadmin.org
> PostgreSQL: https://stream.boxwatch.ru
> pgEdge: https://www.pgedge.com
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2025-03-13 11:24:37 | Re: Role based access control discussion |
| Previous Message | Aditya Toshniwal | 2025-03-13 11:07:07 | Re: Role based access control discussion |