This isn't the issue in the case of sqlite db while using persistent storage. Issue appears only if external database is used as pgadmin configuration db. Just having different way of persistent storage( in this case backend database) behaviour should not be different.
Also, on restart admin user specified while container is not recreated. Can't we fix on similar lines?
I am working on issue #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.
What if the container needs to be restarted? In that case it will again import the server making a duplicate entry.
Not if the servers are manually imported rather than through servers.json.
