Re: [pgAdmin4][Patch]: Ensure any changes to the config database arebackward compatible - Mailing list pgadmin-hackers

From Dave Page
Subject Re: [pgAdmin4][Patch]: Ensure any changes to the config database arebackward compatible
Date
Msg-id CA+OCxoxqv5SZvNLw3rEiohw62TT1XQtCeichGCAc3qjhO9Bf8Q@mail.gmail.com
Whole thread Raw
In response to Re: [pgAdmin4][Patch]: Ensure any changes to the config database arebackward compatible  (Surinder Kumar <surinder.kumar@enterprisedb.com>)
List pgadmin-hackers
Thanks, patch applied.

On Fri, Aug 25, 2017 at 3:12 PM, Surinder Kumar <surinder.kumar@enterprisedb.com> wrote:
Created an RM to track this issue.

On Fri, Aug 25, 2017 at 7:19 PM, Surinder Kumar <surinder.kumar@enterprisedb.com> wrote:
​Hi,​

We will use config variable `SCHEMA_VERSION` to keep track of SQLite database changes. Whenever there is any change is performed in the database, the count of schema version will be incremented by 1 and the same will be updated in SQLite table `version`.

So, these changes make sure the database migration is not performed on the older version of pgAdmin4 and this way the same database will work irrespective of pgAdmin4 version.

Also, this will only work for future pgAdmin4 versions.

Please find attached patch and review.

Thanks,
Surinder




--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgadmin-hackers by date:

Previous
From: Dave Page
Date:
Subject: pgAdmin 4 commit: Allow pgAdmin to run with config database versionsfr
Next
From: Dave Page
Date:
Subject: Re: [pgAdmin4][Patch]: Allow user to provide custom SSL certificatesand provide .pgpass file