From 03348f13723e5d0a0f817aedf8b7fcbf72d322b9 Mon Sep 17 00:00:00 2001 From: Hafez Divandari Date: Thu, 8 Feb 2024 19:07:40 +0330 Subject: [PATCH 1/2] inspecting databases --- upgrade.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/upgrade.md b/upgrade.md index 2c0203f990c..2ae23e6c69f 100644 --- a/upgrade.md +++ b/upgrade.md @@ -187,6 +187,8 @@ The following list of Doctrine DBAL related classes and methods have been remove In addition, registering custom Doctrine types via `dbal.types` in your application's `database` configuration file is no longer required. +If you were using Doctrine DBAL to inspect your database and its associated tables, you may use new schema methods (e.g. `Schema::getTables()`, `Schema::getColumns()`, `Schema::getIndexes()`, `Schema::getForeignKeys()`, etc.) instead. + #### Deprecated Schema Methods @@ -194,7 +196,7 @@ In addition, registering custom Doctrine types via `dbal.types` in your applicat The deprecated `Schema::getAllTables()`, `Schema::getAllViews()`, and `Schema::getAllTypes()` methods have been removed in favor of new `Schema::getTables()`, `Schema::getViews()`, and `Schema::getTypes()` methods. -When using PostgreSQL, none of the new schema methods will accept a three-part reference (e.g. `database.schema.table`). Therefore, you should use `connection()` to declare the database instead: +When using PostgreSQL and SQL Server, none of the new schema methods will accept a three-part reference (e.g. `database.schema.table`). Therefore, you should use `connection()` to declare the database instead: ```php Schema::connection('database')->hasTable('schema.table'); From e12b7b67a1b82d72f691238977a78dec05f78720 Mon Sep 17 00:00:00 2001 From: Taylor Otwell Date: Thu, 8 Feb 2024 09:56:12 -0600 Subject: [PATCH 2/2] Update upgrade.md --- upgrade.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/upgrade.md b/upgrade.md index 2ae23e6c69f..3291b785367 100644 --- a/upgrade.md +++ b/upgrade.md @@ -187,14 +187,14 @@ The following list of Doctrine DBAL related classes and methods have been remove In addition, registering custom Doctrine types via `dbal.types` in your application's `database` configuration file is no longer required. -If you were using Doctrine DBAL to inspect your database and its associated tables, you may use new schema methods (e.g. `Schema::getTables()`, `Schema::getColumns()`, `Schema::getIndexes()`, `Schema::getForeignKeys()`, etc.) instead. +If you were previously using Doctrine DBAL to inspect your database and its associated tables, you may use Laravel's new native schema methods (`Schema::getTables()`, `Schema::getColumns()`, `Schema::getIndexes()`, `Schema::getForeignKeys()`, etc.) instead. #### Deprecated Schema Methods **Likelihood Of Impact: Very Low** -The deprecated `Schema::getAllTables()`, `Schema::getAllViews()`, and `Schema::getAllTypes()` methods have been removed in favor of new `Schema::getTables()`, `Schema::getViews()`, and `Schema::getTypes()` methods. +The deprecated, Doctrine based `Schema::getAllTables()`, `Schema::getAllViews()`, and `Schema::getAllTypes()` methods have been removed in favor of new Laravel native `Schema::getTables()`, `Schema::getViews()`, and `Schema::getTypes()` methods. When using PostgreSQL and SQL Server, none of the new schema methods will accept a three-part reference (e.g. `database.schema.table`). Therefore, you should use `connection()` to declare the database instead: