[Bug] Column data must be provided as an instance of yii\db\ColumnSchemaBuilder. about yii2-migration

[bizley]

Great! Glad I could help. Can we close this then or should we do more here?

[bizley]

Your migration looks good. Unfortunately I cannot repeat the bug with simple applying the above (I removed FK because I don't have the info about the related tables), changing something, and running migration/update. Could you provide the exact steps to reproduce your issue? With migrations for related tables and info about the database engine as well.

[sourabh-openinfotech]

Using InnoDB Version 5.6.39-83.1. I have just migrated up, I think there is difference is some migrations $tableOptions = 'CHARACTER SET utf8 COLLATE utf8_unicode_ci ENGINE=InnoDB'; which differs from current migration $tableOptions = 'CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci ENGINE=InnoDB'; . Would this lead to error?

[bizley]

I don't think so. That should not be a subject of comparison. Maybe there is something with that MySQL 5.6 version that causes the problem (it's 8 years old) - I'm testing this package on 5.7 and 8.0 only.

[sourabh-openinfotech]

will try upgrading mysql version and see if it removes error

[sourabh-openinfotech]

Upgrading mysql version did not solve the issue

[bizley]

Ok, so my request stands. Exact steps to reproduce the issue with migrations for related tables.

[sourabh-openinfotech]

Have included related table migrations

Steps to reproduce are:-
Through console (am on a windows machine),

1. running ./yii migrate/up(on production) or ./yii migrate/fresh(for development). ✔️
2. running ./yii migration/update client_invoice_item_table (after making width and height nullable in the actual database table, want this to be reflected in migration). ❌

[bizley]

I run the steps (except the customer_company_details table which definition is missing but it should not be a problem) and everything works. I ended with migration

<?php

use yii\db\Migration;

class m210415_105710_update_table_client_invoice_item_table extends Migration
{
    public function up()
    {
        $this->alterColumn('{{%client_invoice_item_table}}', 'width', $this->double());
        $this->alterColumn('{{%client_invoice_item_table}}', 'height', $this->double());
    }

    public function down()
    {
        $this->alterColumn('{{%client_invoice_item_table}}', 'width', $this->double()->notNull());
        $this->alterColumn('{{%client_invoice_item_table}}', 'height', $this->double()->notNull());
    }
}

Error message Column data must be provided as an instance of yii\db\ColumnSchemaBuilder pops up when you provide column definition as a string (like 'name' => 'varchar(255)') instead of an object (like 'name' => $this->string(255)) and you don't set experimental (or ex) mode on.

But I don't see it in your files here. I'm afraid I need to ask you to dig into this more in order to help.
$columnData info before it hits that line would be helpful.

[sourabh-openinfotech]

I run the steps (except the customer_company_details table which definition is missing but it should not be a problem) and everything works. I ended with migration

<?php

use yii\db\Migration;

class m210415_105710_update_table_client_invoice_item_table extends Migration
{
    public function up()
    {
        $this->alterColumn('{{%client_invoice_item_table}}', 'width', $this->double());
        $this->alterColumn('{{%client_invoice_item_table}}', 'height', $this->double());
    }

    public function down()
    {
        $this->alterColumn('{{%client_invoice_item_table}}', 'width', $this->double()->notNull());
        $this->alterColumn('{{%client_invoice_item_table}}', 'height', $this->double()->notNull());
    }
}

Error message Column data must be provided as an instance of yii\db\ColumnSchemaBuilder pops up when you provide column definition as a string (like 'name' => 'varchar(255)') instead of an object (like 'name' => $this->string(255)) and you don't set experimental (or ex) mode on.

But I don't see it in your files here. I'm afraid I need to ask you to dig into this more in order to help.
$columnData info before it hits that line would be helpful.

Thank you found the issue, one of the migrations had 'status' => "ENUM('Scheduled', 'Completed')" which was resulting in error. The error was so vague could't find anything on it.