[jira] [Commented] (AIRFLOW-3041) Migration scripts not compatible with Oracle

["Heather B (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AIRFLOW-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17154433#comment-17154433 ] 

Heather B commented on AIRFLOW-3041:
------------------------------------

Any recommended workaround for this? Running into the same error, what would happen if we remove unique constraint or convert "with time zone" to "with local time zone".

Would appreciate some guidance, thank you.

> Migration scripts not compatible with Oracle
> --------------------------------------------
>
>                 Key: AIRFLOW-3041
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-3041
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: database
>    Affects Versions: 1.10.0
>            Reporter: David Allan
>            Priority: Major
>
> The scripts to create the Airflow repository below
> 1. [bdaa763e6c56_make_xcom_value_column_a_large_binary.py|https://github.com/apache/incubator-airflow/blob/master/airflow/migrations/versions/bdaa763e6c56_make_xcom_value_column_a_large_binary.py] and
> 2. [0e2a74e0fc9f_add_time_zone_awareness.py|https://github.com/apache/incubator-airflow/blob/master/airflow/migrations/versions/0e2a74e0fc9f_add_time_zone_awareness.py]
> fail on systems like Oracle, with errors such as ;
>  # ORA-22858: invalid alteration of datatype 
>  # ORA-02329: column of datatype TIME/TIMESTAMP WITH TIME ZONE cannot be unique or a primary key [SQL: 'ALTER TABLE dag_run MODIFY execution_date TIMESTAMP WITH TIME ZONE’]
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)