From 5ed20f8ae745cfcb378c924563f8feee331c45e3 Mon Sep 17 00:00:00 2001 From: Mike Bayer Date: Fri, 30 Sep 2022 14:53:02 -0400 Subject: [PATCH] this is python code, we can format Change-Id: I01aee8b50afe84b8df6154fa73a4375d746cbc02 --- doc/build/core/connections.rst | 21 ++++++++------------- 1 file changed, 8 insertions(+), 13 deletions(-) diff --git a/doc/build/core/connections.rst b/doc/build/core/connections.rst index 4f77e1ada9..ae4f67de4e 100644 --- a/doc/build/core/connections.rst +++ b/doc/build/core/connections.rst @@ -2196,9 +2196,6 @@ Multiple result set support is available from a raw DBAPI cursor using the Registering New Dialects ======================== -.. highlight:: ini -.. format:off - The :func:`_sa.create_engine` function call locates the given dialect using setuptools entrypoints. These entry points can be established for third party dialects within the setup.py script. For example, @@ -2211,25 +2208,23 @@ to create a new dialect "foodialect://", the steps are as follows: via ``foodialect.dialect``. 3. The entry point can be established in setup.py as follows:: - entry_points=""" - [sqlalchemy.dialects] - foodialect = foodialect.dialect:FooDialect - """ + entry_points = """ + [sqlalchemy.dialects] + foodialect = foodialect.dialect:FooDialect + """ If the dialect is providing support for a particular DBAPI on top of an existing SQLAlchemy-supported database, the name can be given including a database-qualification. For example, if ``FooDialect`` were in fact a MySQL dialect, the entry point could be established like this:: - entry_points=""" - [sqlalchemy.dialects] - mysql.foodialect = foodialect.dialect:FooDialect - """ + entry_points = """ + [sqlalchemy.dialects] + mysql.foodialect = foodialect.dialect:FooDialect + """ The above entrypoint would then be accessed as ``create_engine("mysql+foodialect://")``. -.. format:on -.. highlight:: python Registering Dialects In-Process ------------------------------- -- 2.47.3