From 35c7fa9e9e591b120b5d20cf4125f46a3f23a251 Mon Sep 17 00:00:00 2001 From: Ross Patterson Date: Tue, 29 Apr 2025 13:14:09 -0700 Subject: [PATCH] Fix simple typo (#12555) --- doc/build/core/custom_types.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/build/core/custom_types.rst b/doc/build/core/custom_types.rst index 5390824dda..4b27f2f18a 100644 --- a/doc/build/core/custom_types.rst +++ b/doc/build/core/custom_types.rst @@ -15,7 +15,7 @@ A frequent need is to force the "string" version of a type, that is the one rendered in a CREATE TABLE statement or other SQL function like CAST, to be changed. For example, an application may want to force the rendering of ``BINARY`` for all platforms -except for one, in which is wants ``BLOB`` to be rendered. Usage +except for one, in which it wants ``BLOB`` to be rendered. Usage of an existing generic type, in this case :class:`.LargeBinary`, is preferred for most use cases. But to control types more accurately, a compilation directive that is per-dialect -- 2.47.2