feat: move MariaDB to clientless validation (#126)

## Summary
- remove pytest-databases runtime/test dependency on the MariaDB Python client
- keep `pytest-databases[mariadb]` as an empty compatibility extra
- validate MariaDB availability and tests with the container-bundled `mariadb` CLI
- update MariaDB docs to describe user-owned clients and service-only fixtures

This also includes the previously stacked PRs for #127 #128

Author: cofin

docs/conf.py

@@ -62,6 +62,9 @@
     "undoc-members": True,
     "exclude-members": "__weakref__",
 }
+autodoc_type_aliases = {
+    "Container": "docker.models.containers.Container",
+}
 
 # Mock imports for modules not needed during doc generation
 autodoc_mock_imports = ["OpenSSL"]

docs/supported-databases/mariadb.rst

@@ -6,7 +6,8 @@ Integration with `MariaDB <https://mariadb.org>`_, a community-developed, commer
 Installation
 ------------
 
-MariaDB support is built-in and does not require any additional Python client libraries for basic service management. However, to connect to the database from your tests, you should install your preferred MariaDB client (e.g., `mariadb`).
+The fixture provides a running MariaDB service and validates availability with the container's bundled tools. Use the
+service attributes with the MariaDB client, ORM, or application configuration you normally use.
 
 Usage Example
 -------------
@@ -20,7 +21,6 @@ Usage Example
     pytest_plugins = ["pytest_databases.docker.mariadb"]
 
     def test(mariadb_service: MariaDBService) -> None:
-        # Create your own connection using the service fixture attributes
         with mariadb.connect(
             host=mariadb_service.host,
             port=mariadb_service.port,
@@ -36,16 +36,17 @@ Available Fixtures
 ------------------
 
 * ``mariadb_service``: A fixture that provides a MariaDB service (11.4 LTS).
+* ``mariadb_user``: The application user configured in the container.
+* ``mariadb_password``: The application user password configured in the container.
+* ``mariadb_root_password``: The root password configured in the container.
+* ``mariadb_database``: The initial database configured in the container.
 
 The following version-specific fixtures are also available:
 
 * ``mariadb_113_service``: MariaDB 11.3
 * ``mariadb_114_service``: MariaDB 11.4 LTS
 * ``mariadb_122_service``: MariaDB 12.2 Rolling
 
-.. note::
-   The connection fixtures (e.g., ``mariadb_connection``, ``mariadb_114_connection``) are deprecated and will be removed in a future release. Users are encouraged to create their own connections as shown in the example above.
-
 Service API
 -----------
 

docs/supported-databases/mysql.rst

@@ -6,7 +6,8 @@ Integration with `MySQL <https://www.mysql.com/>`_
 Installation
 ------------
 
-MySQL support is built-in and does not require any additional Python client libraries for basic service management. However, to connect to the database from your tests, you should install your preferred MySQL client (e.g., `mysql-connector-python`).
+The fixture provides a running MySQL service and validates availability with the container's bundled tools. Use the
+service attributes with the MySQL client, ORM, or application configuration you normally use.
 
 Usage Example
 -------------
@@ -20,7 +21,6 @@ Usage Example
     pytest_plugins = ["pytest_databases.docker.mysql"]
 
     def test(mysql_service: MySQLService) -> None:
-        # Create your own connection using the service fixture attributes
         with mysql.connector.connect(
             host=mysql_service.host,
             port=mysql_service.port,
@@ -36,6 +36,10 @@ Available Fixtures
 ------------------
 
 * ``mysql_service``: A fixture that provides a MySQL service (8.4 LTS).
+* ``mysql_user``: The application user configured in the container.
+* ``mysql_password``: The application user password configured in the container.
+* ``mysql_root_password``: The root password configured in the container.
+* ``mysql_database``: The initial database configured in the container.
 
 The following version-specific fixtures are also available:
 
@@ -45,9 +49,6 @@ The following version-specific fixtures are also available:
 * ``mysql_84_service``: MySQL 8.4 LTS
 * ``mysql_96_service``: MySQL 9.6 Innovation
 
-.. note::
-   The connection fixtures (e.g., ``mysql_connection``, ``mysql_84_connection``) are deprecated and will be removed in a future release. Users are encouraged to create their own connections as shown in the example above.
-
 Service API
 -----------
 

docs/supported-databases/yugabyte.rst

@@ -10,6 +10,9 @@ Installation
 
    pip install pytest-databases[yugabyte]
 
+The fixture provides a running Yugabyte service and validates availability with Yugabyte's bundled tools. Use the
+service attributes with the PostgreSQL-compatible client, ORM, or application configuration you normally use.
+
 Usage Example
 -------------
 
@@ -23,26 +26,24 @@ Usage Example
 
     @pytest.fixture(scope="session")
     def yugabyte_uri(yugabyte_service: YugabyteService) -> str:
-        opts = "&".join(f"{k}={v}" for k, v in yugabyte_service.driver_opts.items())
-        return f"postgresql://yugabyte:yugabyte@{yugabyte_service.host}:{yugabyte_service.port}/{yugabyte_service.database}?{opts}"
+        return (
+            f"postgresql://{yugabyte_service.user}:{yugabyte_service.password}"
+            f"@{yugabyte_service.host}:{yugabyte_service.port}/{yugabyte_service.database}?sslmode=disable"
+        )
 
     def test_yugabyte_service(yugabyte_uri: str) -> None:
         with psycopg.connect(yugabyte_uri) as conn:
             db_open = conn.execute("SELECT 1").fetchone()
             assert db_open is not None and db_open[0] == 1
 
-    def test_yugabyte_connection(yugabyte_connection: psycopg.Connection) -> None:
-        yugabyte_connection.execute("CREATE TABLE if not exists simple_table as SELECT 1")
-        result = yugabyte_connection.execute("select * from simple_table").fetchone()
-        assert result is not None and result[0] == 1
-
 Available Fixtures
 ------------------
 
 * ``yugabyte_image``: The Docker image to use for Yugabyte DB.
+* ``yugabyte_user``: The Yugabyte user exposed on ``yugabyte_service``.
+* ``yugabyte_password``: The Yugabyte password exposed on ``yugabyte_service``.
+* ``yugabyte_database``: The database created for ``yugabyte_service``.
 * ``yugabyte_service``: A fixture that provides a Yugabyte DB service.
-* ``yugabyte_connection``: A fixture that provides a Yugabyte DB connection.
-* ``yugabyte_driver_opts``: A fixture that provides driver options for Yugabyte DB.
 
 Service API
 -----------

pyproject.toml

@@ -67,14 +67,16 @@ elasticsearch7 = ["elasticsearch7"]
 elasticsearch8 = ["elasticsearch8"]
 gizmosql = ["adbc-driver-flightsql", "pyarrow"]
 keydb = ["redis"]
+mariadb = []
 mongodb = ["pymongo"]
 mssql = ["pymssql"]
+mysql = []
 oracle = ["oracledb"]
 postgres = ["psycopg>=3"]
 redis = ["redis"]
 spanner = ["google-cloud-spanner"]
 valkey = ["valkey"]
-yugabyte = ["psycopg2-yugabytedb"]
+yugabyte = []
 
 [dependency-groups]
 build = ["bump-my-version"]
@@ -102,7 +104,7 @@ doc = [
   "sphinx-autodoc-typehints",
   "sphinx-rtd-theme",
 ]
-extra = ["psycopg2-binary", "psycopg[binary,pool]", "psycopg2-yugabytedb-binary"]
+extra = ["psycopg[binary,pool]"]
 lint = [
   "mypy",
   "ruff",
@@ -126,15 +128,6 @@ test = [
   "pytest-click",
   "pytest-xdist",
   "pytest-sugar",
-  # mysql-connector-python's wheel coverage degrades unpredictably each release:
-  #   3.9:    9.4.x is the last release with cp39 wheels
-  #   3.10+:  9.6.x is the latest release with full Linux/macOS/Windows coverage
-  #           (9.7.0 dropped Linux/Windows for cp311 and dropped cp312/cp313 entirely)
-  # Lower bounds force uv to fork the resolution per-interpreter - without them
-  # a single 9.4.0 satisfies every marker and gets locked universally.
-  "mysql-connector-python<9.5; python_version < '3.10'",
-  "mysql-connector-python>=9.6,<9.7; python_version >= '3.10'",
-  "mariadb",
 ]
 
 ##################