From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Surinder Kumar <surinder(dot)kumar(at)enterprisedb(dot)com> |
Cc: | 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-29 14:03:19 |
Message-ID: | CA+OCxoxqv5SZvNLw3rEiohw62TT1XQtCeichGCAc3qjhO9Bf8Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Thanks, patch applied.
On Fri, Aug 25, 2017 at 3:12 PM, Surinder Kumar <
surinder(dot)kumar(at)enterprisedb(dot)com> wrote:
> 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
>>
>
>
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2017-08-29 14:21:22 | Re: [pgAdmin4][Patch]: Allow user to provide custom SSL certificates and provide .pgpass file |
Previous Message | Dave Page | 2017-08-29 14:03:10 | pgAdmin 4 commit: Allow pgAdmin to run with config database versions fr |