Logo-amall

Hi, seems we hit a length limit on the `pipeline_deployment` table for v 0.35.1 , for column `pipeline_config` and or `step_configuration` : ```│ 2023-03-16T14:13:23.869746657Z sqlalchemy.exc.DataError: (pymysql.err.DataError) (1406, "Data too long for column 'step_configurations' at row 1") ││ 2023-03-16T14:13:23.869750897Z [SQL: INSERT INTO pipeline_deployment (stack_id, pipeline_id, build_id, schedule_id, user_id, workspace_id, pipeline_configurat ││ 2023-03-16T14:13:23.869763785Z [parameters: {'stack_id': 'faf848638e5845f2b132bfcdf1f5b787', 'pipeline_id': '0a751ece32a64573a83a002255d0532a', 'build_id': No``` seems to be related to the use of `TEXT` datatype (see ) , maybe a switch to `String(2**24)` will do the trick ?

Last active 8 days ago

4 replies

0 views

  • FR

    Hi, seems we hit a length limit on the pipeline_deployment table for v 0.35.1 , for column pipeline_config and or step_configuration :
    │ 2023-03-16T14:13:23.869746657Z sqlalchemy.exc.DataError: (pymysql.err.DataError) (1406, "Data too long for column 'step_configurations' at row 1") ││ 2023-03-16T14:13:23.869750897Z [SQL: INSERT INTO pipeline_deployment (stack_id, pipeline_id, build_id, schedule_id, user_id, workspace_id, pipeline_configurat ││ 2023-03-16T14:13:23.869763785Z [parameters: {'stack_id': 'faf848638e5845f2b132bfcdf1f5b787', 'pipeline_id': '0a751ece32a64573a83a002255d0532a', 'build_id': No
    seems to be related to the use of TEXT datatype (see ) , maybe a switch to String(2**24) will do the trick ?

  • FR

    I've created an issue

  • AL

    Good catch, we'll try to fix this asap. Thanks @francois.serra

  • AL

    We have a PR cooking that fixes this.

Last active 8 days ago

4 replies

0 views

Join conversation on slack