You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by "Aizhamal Nurmamat kyzy (JIRA)" <ji...@apache.org> on 2019/05/17 20:03:03 UTC

[jira] [Updated] (AIRFLOW-18) Alembic's constraints and indexes are unnamed thus hard to drop or change

     [ https://issues.apache.org/jira/browse/AIRFLOW-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aizhamal Nurmamat kyzy updated AIRFLOW-18:
------------------------------------------
    Component/s:     (was: db)
                 database

> Alembic's constraints and indexes are unnamed thus hard to drop or change
> -------------------------------------------------------------------------
>
>                 Key: AIRFLOW-18
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-18
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: database
>            Reporter: Bolke de Bruin
>            Assignee: zgl
>            Priority: Critical
>              Labels: database
>
> Eg. in XXX_add_dagrun.py the constraint is added without a name:
> sa.UniqueConstraint('dag_id', 'execution_date'),
> This makes constraint naming database specific, ie. postgres' name for the constraint be different than mysql's and sqllite's.
> Best practice per http://alembic.readthedocs.io/en/latest/naming.html is to have naming conventions that are being applied. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)