summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authormike bayer <mike_mp@zzzcomputing.com>2021-11-18 16:16:01 +0000
committerGerrit Code Review <gerrit@ci3.zzzcomputing.com>2021-11-18 16:16:01 +0000
commit9141b6c15eac4827f0df2e3f87f331c821d13b5a (patch)
tree6f79ccdc19e9b80047496d86b404794e9e7525c0 /doc
parent5b6393fb7b4282da0301eb88da5b7f33a8614d3e (diff)
parent93fad8fb0c5421ad162064e0aa506cb1e70cbf2b (diff)
downloadsqlalchemy-9141b6c15eac4827f0df2e3f87f331c821d13b5a.tar.gz
Merge "remove "native decimal" warning" into main
Diffstat (limited to 'doc')
-rw-r--r--doc/build/changelog/unreleased_20/7299.rst17
1 files changed, 17 insertions, 0 deletions
diff --git a/doc/build/changelog/unreleased_20/7299.rst b/doc/build/changelog/unreleased_20/7299.rst
new file mode 100644
index 000000000..af2955e21
--- /dev/null
+++ b/doc/build/changelog/unreleased_20/7299.rst
@@ -0,0 +1,17 @@
+.. change::
+ :tags: bug, sqlite
+ :tickets: 7299
+
+ Removed the warning that emits from the :class:`_types.Numeric` type about
+ DBAPIs not supporting Decimal values natively. This warning was oriented
+ towards SQLite, which does not have any real way without additional
+ extensions or workarounds of handling precision numeric values more than 15
+ significant digits as it only uses floating point math to represent
+ numbers. As this is a known and documented limitation in SQLite itself, and
+ not a quirk of the pysqlite driver, there's no need for SQLAlchemy to warn
+ for this. The change does not otherwise modify how precision numerics are
+ handled. Values can continue to be handled as ``Decimal()`` or ``float()``
+ as configured with the :class:`_types.Numeric`, :class:`_types.Float` , and
+ related datatypes, just without the ability to maintain precision beyond 15
+ significant digits when using SQLite, unless alternate representations such
+ as strings are used. \ No newline at end of file