Add absolute path to Spiral/Database/Injection/Fragment in alterColumn function

[mrakolice]

Without leading slash composer try to find this class in Migration namespace instead of global.

[mrakolice]

I found monkey patching solution for this particular usecase, spiral/reactor/src/Serializer#117-119 need to be rewrite as

 if (is_object($value)) {
            return '\\' . var_export($value, true);
}

[mrakolice]

Or just add __set_state function to Spiral/Database/Injection/Fragment class

[wolfy-j]

Thank you for the report. Will be fixed today.

[wolfy-j]

Please check the v2.7.1 version of spiral/database. Let me know if you still need the Reactor change.

[mrakolice]

This problem is still in project. So I think, that Reactor need to change a little bit.

[wolfy-j]

I would greatly appreciate your PR to Reactor. If not I’ll check next week.

[vvval]

At least it would be great to have a failing test

[mrakolice]

Here example of failing entities.

https://github.com/mrakolice/migrations/tree/error-with-spiral-reactor

my composer.lock:

cycle/orm v1.1.18
spiral/database v2.6.10
spiral/reactor v2.2.2

[mrakolice]

If I try to do

if (is_object($value) && method_exists($value, '__set_state')) {
            return '\\' . var_export($value, true);
}

in spiral/reactor/Serializer.php, then function BaseTest->assertSameAsInDb start working unexpectedly

But in database I can see changes (column type change from integer to bigint)

[vvval]

@wolfy-j I assume that the second error in tests is related directly to the migrations package

[vvval]

The reactor has been fixed in the v2.2.3 release

[mrakolice]

The reactor has been fixed in the v2.2.3 release

Thanks! I am waiting for migrations package fix.