Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for Laravel 11 #215

Open
jangaraev opened this issue Sep 26, 2024 · 2 comments
Open

Support for Laravel 11 #215

jangaraev opened this issue Sep 26, 2024 · 2 comments

Comments

@jangaraev
Copy link

jangaraev commented Sep 26, 2024

hi guys,

once observed that the package doesn't support Laravel v11, I quickly tried to align that by forking the package and modifying it's dependencies like follows:

composer.json

    "require": {
        ...
        "illuminate/database": "^8.0|^9.0|^10.0|^11.0",
        ...
    },

this made me possible to install my fork into my Laravel application.

{
    "repositories": [
        {
            "type": "vcs",
            "url": "https://github.com/jangaraev/laravel-mysql-spatial.git"
        }
    ]
}
{
    "require": {
        "grimzy/laravel-mysql-spatial": "@dev",
    }
}

next, I faced the fatal error during package auto-discover of composer update command:

Method Grimzy\LaravelMysqlSpatial\MysqlConnection::getDoctrineSchemaManager does not exist.

the thing is L11 removed several DBAL methods: https://laravel.com/docs/11.x/upgrade#doctrine-dbal-removal

under the hood, the package tries to detect the DB platform here and register geo specific types:

$dbPlatform = $this->getDoctrineSchemaManager()->getDatabasePlatform();

this method doesn't exist in L11. unfortunately, this was a breaking change for the package.

I'll try to look for a workaround.

please feel free to share your experience if you also tried to make it work in L11.

@stefanrakicfaxi
Copy link

@grimzy It would be great if you could check this PRs and make a new release with support for Laravel 11

@Shailesh-Kala
Copy link

Shailesh-Kala commented Nov 14, 2024

@jangaraev @stefanrakicfaxi have you guys found any workaround for this error:

Method Grimzy\LaravelMysqlSpatial\MysqlConnection::getDoctrineSchemaManager does not exist.

I am facing same issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants