Adjust JSON verbiage about "implied" datatype

SQLite and MariaDB (not MySQL) has an "implied" JSON,
MySQL has it directly

Change-Id: I2e1744de96ac4e241dc647ae2214b63cdad33428
(cherry picked from commit 1abbdf0d5233f2aa96805544381a5c14151525e4)

diff --git a/doc/build/core/tutorial.rst b/doc/build/core/tutorial.rst
index 69499d7ed1e3d0b5f5ea66315da868239e0cadac..da359a06f4d42ba52bab35f9ebf288cc596078d1 100644 (file)
--- a/doc/build/core/tutorial.rst
+++ b/doc/build/core/tutorial.rst
@@ -1520,8 +1520,10 @@ another function :func:`.type_coerce` which is closely related to
 :func:`.cast`, in that it sets up a Python expression as having a specific SQL
 database type, but does not render the ``CAST`` keyword or datatype on the
 database side.    :func:`.type_coerce` is particularly important when dealing
-with the :class:`.types.JSON` datatype, which on a database like SQLite is
-an "implied" datatype. Below, we use :func:`.type_coerce` to deliver a Python
+with the :class:`.types.JSON` datatype, which typicaly has an intricate
+relationship with string-oriented datatypes on different platforms and
+may not even be an explicit datatype, such as on SQLite and MariaDB.
+Below, we use :func:`.type_coerce` to deliver a Python
 structure as a JSON string into one of SQLite's JSON functions:
 
 .. sourcecode:: pycon+sql