Postgres Pro
Downloads
Home   >   mailing lists

Re: [pgAdmin][RM-6460]: Need a mechanism to detect a corrupt/broken config DB file. - Mailing list pgadmin-hackers

From Dave Page
Subject Re: [pgAdmin][RM-6460]: Need a mechanism to detect a corrupt/broken config DB file.
Date
Msg-id CA+OCxoz-Qr9ubPZ-1wBrHkF+0B=cC72rEHURyLQfFF4dHSDbhg@mail.gmail.com
Whole thread Raw
In response to [pgAdmin][RM-6460]: Need a mechanism to detect a corrupt/broken config DB file.  (Nikhil Mohite <nikhil.mohite@enterprisedb.com>)
Responses Re: [pgAdmin][RM-6460]: Need a mechanism to detect a corrupt/broken config DB file.  (Nikhil Mohite <nikhil.mohite@enterprisedb.com>)
List pgadmin-hackers
Tree view
Hi

On Thu, Jun 3, 2021 at 7:39 AM Nikhil Mohite <nikhil.mohite@enterprisedb.com> wrote:
Hi Hackers,

Please find the attached patch for RM-6460:  Need a mechanism to detect a corrupt/broken config DB file.

1. Added checks if all tables added in the model are present in SQLite DB or not.
2. If migrations fail it will backup older file and try migrations with the newly created file. 
(User will get notification on UI for the location of the backup file and newly created.)
3. If the user deleted any table from SQLite DB pgAdmin will not run on the next restart and it will add the missing table list in the logs.

Surely if any tables have been deleted, it'll fail the check in point 1?
 
--

pgadmin-hackers by date:

Previous
From: Nikhil Mohite
Date:
Subject: [pgAdmin][RM-6460]: Need a mechanism to detect a corrupt/broken config DB file.
Next
From: Dave Page
Date:
Subject: Re: [pgAdmin][RM-2341]: Add menu option for starting PSQL