Introduce Migration system for SQLite database

From: Joao Pedro De Almeida Pereira <jpereira(at)pivotal(dot)io>
To: pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>
Cc: Sarah McAlear <smcalear(at)pivotal(dot)io>
Subject: Introduce Migration system for SQLite database
Date: 2017-03-10 16:39:40
Message-ID: CAE+jjamL01hnr5zgjYztgFPR2WSSUoZDWsjeDUN1AQTGJ5csVg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

Hi Hackers,
We were looking at the migration pattern created for the SQLite database
and tried to look into the possibility of using a library that could handle
them for us.

- Migrations allow us to have a single path of creating the table instead
of creating tables using SQLAlchemy or hand rolled SQL. This pattern can
cause issues because updated databases might be different than the ones
created by SQLAlchemy
- The version numbering for the migrations is tedious and error prone.

After some research we found these 2 libraries(alembic, flask-migrate) that
can run migrations for us.

Alembic is a library written by the same person that wrote SQLAlchemy and
is used to manage and run the migrations.

Flask-migrate is the glue that joins Flask and Alembic allowing us to run
the migrations directly in the code.

What are your thoughts about this change?
Can we safely assume that everyone is in version 14 of the database?

--
Thanks
Joao & Sarah

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Catonano 2017-03-10 22:23:35 hello (and .git folder)
Previous Message Ashesh Vashi 2017-03-10 15:49:57 pgAdmin 4 commit: Resolved an issue finding the python interpreter on *