Closed osama-98 closed 1 month ago
https://github.com/laravel/framework/pull/48864
Removes DB::getDoctrineSchemaManager() method
you can modify like this , it cause doctrine types not supported on laravel 11
@uacode This is explaining why the error is being thrown. But, how to solve it?
@osama-98 I commented in vendor (only for run DB migrations)
\Reliese\Meta\MySql\Schema::schemas
public static function schemas(Connection $connection)
{
// $schemas = $connection->getDoctrineSchemaManager()->listDatabases();
// Schema::getDatabases();
$schemas = [];
return array_diff($schemas, [
'information_schema',
'sys',
'mysql',
'performance_schema',
]);
}
@uacode This is explaining why the error is being thrown. But, how to solve it?
I resolved it on PR #208 you can direct edit your vendor folder
Could somebody please review and merge? New Laravel devs cannot use this as they start with Laravel 11 and will be forced to make their own Model files: 1 for each table.
@igun997 Your PR doesn't fix the issue completely. There are still calls to the getDoctrineSchemaManager (in ...Postgres/Schema.php) which was removed in v11.
@igun997 Your PR doesn't fix the issue completely. There are still calls to the getDoctrineSchemaManager (in ...Postgres/Schema.php) which was removed in v11.
ah , i forget about it. coz i use mysql & mariadb as primary databases
any update on this? as still I am getting the Method Illuminate\Database\MySqlConnection::getDoctrineSchemaManager does not exist.
error while runing the php artisan code:models
command
any update on this? as still I am getting the
Method Illuminate\Database\MySqlConnection::getDoctrineSchemaManager does not exist.
error while runing thephp artisan code:models
command
Look a couple of comments back, this workaround works.
https://github.com/reliese/laravel/issues/273#issuecomment-2016756918
any update on this? as still I am getting the
Method Illuminate\Database\MySqlConnection::getDoctrineSchemaManager does not exist.
error while runing thephp artisan code:models
command
same error here
This should be resolved by #208. Apologies on the delay in getting this merged.
I got an error when I did update to Laravel11, please find the error message