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

From Nikhil Mohite
Subject Re: [pgAdmin][RM-6460]: Need a mechanism to detect a corrupt/broken config DB file.
Date
Msg-id CAOBg0ANKd=_H+P6v7Pp9mLE1uVdrWtSqfn_gWdLowVsyYWTS+Q@mail.gmail.com
Whole thread Raw
In response to Re: [pgAdmin][RM-6460]: Need a mechanism to detect a corrupt/broken config DB file.  (Dave Page <dpage@pgadmin.org>)
Responses Re: [pgAdmin][RM-6460]: Need a mechanism to detect a corrupt/broken config DB file.  (Dave Page <dpage@pgadmin.org>)
List pgadmin-hackers
Hi Dave,

On Thu, Jun 3, 2021 at 1:47 PM Dave Page <dpage@pgadmin.org> wrote:
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?
Yes, but if the user deletes any table while pgAdmin is running then it will fail when the user tries to run pgAdmin next time.
(If we remove the table from the model it will not check particular table is present in DB or not. )
 
--
Regards,
Nikhil Mohite. 

pgadmin-hackers by date:

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