Remove reference to `DatabaseMiddleware` in the documentation (#1845)

diff --git a/docs/config.md b/docs/config.md
index 52a801568d8847ca3e2dc6631c00ab3a83b5c043..a879374dc38fff5aec192290b7343f34cce8d523 100644 (file)
--- a/docs/config.md
+++ b/docs/config.md
@@ -224,9 +224,6 @@ def client():
     """
     # Our fixture is created within a context manager. This ensures that
     # application startup and shutdown run for every test case.
-    #
-    # Because we've configured the DatabaseMiddleware with `rollback_on_shutdown`
-    # we'll get a complete rollback to the initial state after each test case runs.
     with TestClient(app) as test_client:
         yield test_client
 ```

diff --git a/docs/database.md b/docs/database.md
index aa6cb74edfd66c41768cd9f14ae35211a85da8f4..2b5d3c099dea2a9129682e937f48dfa4093438ac 100644 (file)
--- a/docs/database.md
+++ b/docs/database.md
@@ -6,10 +6,6 @@ or use regular non-async endpoints, and integrate with [SQLAlchemy](https://www.
 In this documentation we'll demonstrate how to integrate against [the `databases` package](https://github.com/encode/databases),
 which provides SQLAlchemy core support against a range of different database drivers.
 
-**Note**: Previous versions of Starlette included a built-in `DatabaseMiddleware`.
-This option is currently still available but should be considered as pending deprecation.
-It will be removed in a future release. The legacy documentation [is available here](https://github.com/encode/starlette/blob/0.10.2/docs/database.md).
-
 Here's a complete example, that includes table definitions, configuring a `database.Database`
 instance, and a couple of endpoints that interact with the database.