cads-catalogue

CADS catalogue manager

Quick Start

>>> import cads_catalogue

Workflow for developers/contributors

For best experience create a new conda environment (e.g. DEVELOP) with Python 3.11:

conda create -n DEVELOP -c conda-forge python=3.11
conda activate DEVELOP

Before pushing to GitHub, run the following commands:

1. Update conda environment: make conda-env-update
2. Install this package: pip install -e .
3. Sync with the latest template (optional): make template-update
4. Run quality assurance checks: make qa
5. Run tests: make unit-tests
6. Run the static type checker: make type-check
7. Build the documentation (see Sphinx tutorial): make docs-build

Instructions for creating a new database version

The package cads-catalogue comes with its 'catalogue' database. In case of database structure upgrade, developers must follow these steps:

1. Update the new database structure modifying /cads_catalogue/database.py, using SQLAlchemy ORM technologies
2. Execute from the cads-catalogue work folder:

   alembic revision -m "message about the db modification"
   

3. The last command will create a new python file inside /alembic/versions. Fill the upgrade function with the operations that must be executed to migrate the database from the old structure to the new one. Keep in mind both DDL (structure modification) and DML (data modification) instructions. For reference, use https://alembic.sqlalchemy.org/en/latest/ops.html#ops. Similarly, do the same with the downgrade function.
4. Commit and push the modifications and the new file.

Instructions for moving between different database versions

The package comes with its own 'alembic-cli' script in order to move between different database versions. This script is a slight modified version of the 'alembic' script, overriding default config path used (/alembic.ini) and the sqlalchemy.url used, that is automatically computed by the environment and not read from any ini file.

All the database releases where you can migrate up and down must be defined by files contained inside the folder /alembic/versions. All these files are in a version queue: each file has link to its revision hash (variable 'revision', the prefix of the file name) and to the next older one (variable 'down_revision'), and contains code to step up and down that database version.
Some useful commands are listed below.

• To migrate to the newest version, type:
  alembic-cli upgrade head
• To upgrade to a specific version hash, for example 8ccbe515155c, type:
  alembic-cli upgrade 8ccbe515155c
• To downgrade to a specific version hash, for example 8ccbe515155c, type:
  alembic-cli downgrade 8ccbe515155c
• To get the current version hash of the database, type:
  alembic-cli current

Other details are the same of the standard alembic migration tool, see the Alembic tutorial.

License

Copyright 2022, European Union.

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.