OroCommerce Forums

Covering OroCommerce topics, including community updates and company announcements.

Forums Forums OroCommerce Oro (3.1.17) installation: Mysql (8.0.16) fails due to SQL-error

This topic contains 2 replies, has 2 voices, and was last updated by  Frank 1 year, 2 months ago.

Starting from March 1, 2020 the forum has been switched to the read-only mode. Please head to StackOverflow for support.

  • Creator
  • #38942


    Hi oro-Team,


    php ./bin/console oro:install –env=prod –timeout=900

    with MYSQL-Server > 8.0 installed

    creates an SQL-error:

    > Oro\Bundle\WorkflowBundle\Migrations\Schema\OroWorkflowBundleInstaller

    ERROR: An exception occurred while executing ‘CREATE TABLE oro_workflow_definition (name VARCHAR(255) NOT NULL, start_step_id INT DEFAULT NULL, label VARCHAR(255) NOT NULL, related_entity VARCHAR(255) NOT NULL, entity_attribute_name VARCHAR(255) NOT NULL, steps_display_ordered TINYINT(1) NOT NULL, system TINYINT(1) NOT NULL, active TINYINT(1) DEFAULT ‘0’ NOT NULL, priority INT DEFAULT 0 NOT NULL, configuration LONGTEXT NOT NULL COMMENT ‘(DC2Type:array)(DC2Type:array)’, exclusive_active_groups LONGTEXT DEFAULT NULL COMMENT ‘(DC2Type:simple_array)(DC2Type:simple_array)’, exclusive_record_groups LONGTEXT DEFAULT NULL COMMENT ‘(DC2Type:simple_array)(DC2Type:simple_array)’, created_at DATETIME NOT NULL COMMENT ‘(DC2Type:datetime)’, updated_at DATETIME NOT NULL COMMENT ‘(DC2Type:datetime)’, applications LONGTEXT NOT NULL COMMENT ‘(DC2Type:simple_array)(DC2Type:simple_array)’, INDEX idx_6f737c368377424f (start_step_id), PRIMARY KEY(name)) DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci ENGINE = InnoDB’:

    SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘system TINYINT(1) NOT NULL, active TINYINT(1) DEFAULT ‘0’ NOT NULL, priority INT’ at line 1

    In Mysql 8, a column must not be named ‘system’:

    Could you be so kind, and fix this!

    Thanks a lot.

    PS: I am a little bit suprised, that it seems that nobody from the development-team has checked the app with respect to MYSQL 8 concerns … :-)

Viewing 2 replies - 1 through 2 (of 2 total)
  • Author
  • #38945
    Andrey Yatsenko
    Andrey Yatsenko

    Thanks for the report, Frank.

    As a workaround, you can use MySQL 5.7 for now. We’ll fix it in further releases.

    Internal ticket id #BAP-18909



    Hi Andrey,

    thankls for reply.

    Yes, indeed, I switched to Mysql-Server 5.7, and oro 3.1.7 installs like a charm … !

    Kind regards

Viewing 2 replies - 1 through 2 (of 2 total)

The forum ‘OroCommerce’ is closed to new topics and replies.

You will be redirected to [title]. Would you like to continue?

Yes No