From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Pravesh Sharma <pravesh(dot)sharma(at)enterprisedb(dot)com> |
Cc: | pgadmin-hackers(at)postgresql(dot)org |
Subject: | Re: Require suggestions on issue #7811 |
Date: | 2024-09-03 08:16:51 |
Message-ID: | CA+OCxowvD+kUSm19KijKTNzY9CNBPE=oRS1T84vCmSjqOX4y0Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Hi
On Tue, 3 Sept 2024 at 09:10, Pravesh Sharma <
pravesh(dot)sharma(at)enterprisedb(dot)com> wrote:
> Hi Hackers,
>
> I am working on issue #7811
> <https://github.com/pgadmin-org/pgadmin4/issues/7811>, where using an
> external database for storing pgAdmin configuration results in duplicate
> server entries when a container with a mapped servers.json file is
> restarted.
>
> The proposed solution is to implement a check when loading servers. We
> would verify the server’s name, host, port, and username to determine if
> the server already exists in the database. If it does, we would skip
> registering it again.
>
>
> Please share any suggestions or feedback on this approach.
>
I would say "Won't fix". If someone is using persistent storage for
settings, why launch containers to import the same servers over and over
again? Just load them once, manually.
--
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://www.postgresql.org
EDB: https://www.enterprisedb.com
PGDay UK 2024, 11th September, London: https://2024.pgday.uk/
From | Date | Subject | |
---|---|---|---|
Next Message | Pravesh Sharma | 2024-09-03 08:28:59 | Re: Require suggestions on issue #7811 |
Previous Message | Pravesh Sharma | 2024-09-03 08:10:19 | Require suggestions on issue #7811 |