Orsdxy

I'm getting following error "Cannot process definition to array for type tinytext" on Magento 2.3.0 when executing setup:upgrade command.

Thanks

You are getting this error because "data type" of any third party extension's table's column is tinytext.

So you need to find out column name using debug in following file.

Open this file /vendor/magento/framework/Setup/Declaration/Schema/Db/DefinitionAggregator.php and check this fromDefinition() method and then add debug code to find column name.

public function fromDefinition(array $data)

    {

        $type = $data['type'];

        if (!isset($this->definitionProcessors[$type])) {



            /* Add Code for Debug */



            echo "<pre>";

            print_r($data); exit();



            /* Code End */



            throw new InvalidArgumentException(

                sprintf("Cannot process definition to array for type %s", $type)

            );

        }



        $definitionProcessor = $this->definitionProcessors[$type];

        return $definitionProcessor->fromDefinition($data);

    }

After that please run setup:upgrade command and you will get array of column data in console. so from this array you will get the name of column from your third party extension table.

Now from that table please change column's data type "tinytext" to "text" and issue will be fixed.

SECOND METHOD

Please export the database and search for keywords tinytext, you will found a table which use this format, Now changed it to TEXT and the problem solved.

Note : You might also get issues from ENUM and MEDIUMINT data type as well, so do the same steps if get any other data type issue.

In my case, Wordpress was being used with the Fishpig integration. In wp_comments, the comment_author was set to TINYTEXT. The problem was resolved by changing that column declaration.

A handy little SQL script if anyone wants to know which columns have tinytext types defined.

SELECT TABLE_NAME,

   `COLUMNS`.`COLUMN_NAME`                       AS `name`, `COLUMNS`.`COLUMN_DEFAULT` AS `default`,

   `COLUMNS`.`DATA_TYPE`                         AS `type`, IF(IS_NULLABLE = "YES", true, false) AS `nullable`,

   `COLUMNS`.`COLUMN_TYPE`                       AS `definition`, `COLUMNS`.`EXTRA` AS `extra`,

   IF(COLUMN_COMMENT = "", NULL, COLUMN_COMMENT) AS `comment`

FROM `information_schema`.`COLUMNS`

WHERE (TABLE_SCHEMA = '<table_schema>') AND (`COLUMNS`.`DATA_TYPE` = 'tinytext');

Helped me find the offending third-party module quickly.