Re: [pgAdmin4][Patch]: Ensure any changes to the config database are backward compatible

From: Surinder Kumar <surinder(dot)kumar(at)enterprisedb(dot)com>
To: pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: [pgAdmin4][Patch]: Ensure any changes to the config database are backward compatible
Date: 2017-08-25 14:12:30
Message-ID: CAM5-9D9vFgxJ3hD3qdYs5yQXWOEtv-SwFLm2DYAiFBEhPfFNoA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

Created an RM <https://redmine.postgresql.org/issues/2664> to track this
issue.

On Fri, Aug 25, 2017 at 7:19 PM, Surinder Kumar <
surinder(dot)kumar(at)enterprisedb(dot)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
>

In response to

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message pgAdmin 4 Jenkins 2017-08-25 14:41:07 Build failed in Jenkins: pgadmin4-master-python27-feature #10
Previous Message Surinder Kumar 2017-08-25 13:49:58 [pgAdmin4][Patch]: Ensure any changes to the config database are backward compatible