| From: | Surinder Kumar <surinder(dot)kumar(at)enterprisedb(dot)com> |
|---|---|
| To: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
| Subject: | [pgAdmin4][Patch]: Ensure any changes to the config database are backward compatible |
| Date: | 2017-08-25 13:49:58 |
| Message-ID: | CAM5-9D-kWS14uaYNc28qzu+XHesHsQXZiBjOb2pCRo23UpgiQw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
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
| Attachment | Content-Type | Size |
|---|---|---|
| db_migration_for_multiple_pgadmin_versions.patch | application/octet-stream | 2.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Surinder Kumar | 2017-08-25 14:12:30 | Re: [pgAdmin4][Patch]: Ensure any changes to the config database are backward compatible |
| Previous Message | Murtuza Zabuawala | 2017-08-25 13:45:12 | Re: [pgAdmin4][Patch]: Allow user to provide custom SSL certificates and provide .pgpass file |