https://pfspipe.ipmu.jp/jira This file is an XML representation of an issue en-us 8.3.4 803005 13-09-2019 https://pfspipe.ipmu.jp/jira/browse/INSTRM-941 Instrument control development <p>opDB schema is defined by `model.py` and a new database can be created by using this definition. Currently, however, there is no mechanism to update the existing opDB with records when this schema definition is updated, which happens frequently. The procedure is (semi-) automated if possible. </p> <p>Database migration tools (such as <em>alembic</em>) are options, but we may like easier and simpler way. Anyway, we should start from finding out what kind of options we have for this purpose.</p> <p>Furthermore, we like to manage the installation of the opDB package through `eups`.</p> INSTRM-941

Create mechanism to manage the opDB update

Task Normal Done Done Kiyoto Yabe Kiyoto Yabe opDB Mon, 6 Apr 2020 03:34:14 +0000 Mon, 12 Oct 2020 04:24:52 +0000 Mon, 12 Oct 2020 04:24:52 +0000 spt_operational_database 0 2 <p>Just a copy from my slack comment about <em>alembic</em> --</p> <p>I took a look at <em>alembic</em> ( <em>sqlalchemy-migrate</em> exists but people recommend <em>alembic</em> because <em>sqlalchemy-migrate</em> seems to be no longer maintained). It is basically simple and easy to use. After some setups and initialization, only two commands are basically used:</p> <ul> <li>alembic revision --autogenerate -m "comment or version name" (to generate a migration script reading <tt>models.py</tt> and detecting diff)</li> <li>alembic upgrade head (to apply the change to DB using the generated script)</li> </ul> <p>I tested on my local opDB and found that some use-cases were good but some were not. I think we need to edit the script by hand for what we want. The generated scripts should be on the repository and tracked. I'm still not sure whether this covers all we want, but I feel this helps us for what we want to do to some extent. <br/>  </p> <p>I have pushed my first proposal on the branch.</p> Development Rank 0|zzs154: