Migrations not working "Cannot declare class Table, because the name is already in use" after Laravel ^8.38 update

[yoramdelangen]

Hi, this is just a heads up for when Laravel-zero will be updated to later version of Laravel Framework >= 8.38.0 or higher.

They introduced "Allow anonymous and class based migration coexisting" and they're using realpath to check if the filename is equally the class filename (not sure why though).

Currently it breaks Laravel-zero project(s) when updating, so fixed it for now to "downgrade/static" version to 8.37.*.

References:
laravel/framework@ee78372

I will try to fix it within the framework and make a pull request.

For future references; I don't think PHP will ever gonna support realpath for different file streams than file://:

• https://bugs.php.net/bug.php?id=52769
• https://www.php.net/manual/en/function.realpath.php#refsect1-function.realpath-returnvalues

[mathewparet]

@yoramdelangen I changed laravel/framework entry in composer.lock to 8.37 but it still didn't help.

Either that's not the fix, or I am doing it wrong.

[yoramdelangen]

@yoramdelangen I changed laravel/framework entry in composer.lock to 8.37 but it still didn't help.

Either that's not the fix, or I am doing it wrong.

You have to set it fixed in your composer.json file. Otherwise it will be discarded at composer update

[mathewparet]

The composer.json doesn't have an entry for Laravel/framework

…

-- Best Regards, Mathew Paret Sent using OnePlus

On Fri, 25 Jun 2021, 4:07 pm Yoram, ***@***.***> wrote: @yoramdelangen <https://github.com/yoramdelangen> I changed laravel/framework entry in composer.lock to 8.37 but it still didn't help. Either that's not the fix, or I am doing it wrong. You have to set it fixed in your composer.json file. Otherwise it will be discarded at composer update — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#343 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AASGB2X5T3H3JHLHXV5C5I3TUQMITANCNFSM444NCH5A> .

[yoramdelangen]

Just add it in, it will make it fixed

[mathewparet]

You are talking about adding it to composer.json in my project's root folder, right? It didn't work for me.

[tobytwigger]

@mathewparet I tried adding the following to composer.json under require, and it lets me work around this issue

"require": {
    ...,
    "illuminate/database": "8.37.*"
}

[tobytwigger]

@yoramdelangen Do you have ideas as to how to fix the issue in the framework? I'd be very happy to do it, just not sure of the right direction!

[mathewparet]

@mathewparet I tried adding the following to composer.json under require, and it lets me work around this issue

"require": {
    ...,
    "illuminate/database": "8.37.*"
}

This worked after I deleted the composer.lock file