diff options
author | Mike Bayer <mike_mp@zzzcomputing.com> | 2021-11-08 12:20:23 -0500 |
---|---|---|
committer | Mike Bayer <mike_mp@zzzcomputing.com> | 2021-11-17 18:21:48 -0500 |
commit | 93fad8fb0c5421ad162064e0aa506cb1e70cbf2b (patch) | |
tree | 6566691a17686e206864856f30d46f6b0982be53 /lib/sqlalchemy/dialects/postgresql/base.py | |
parent | 958f902b1fc528fed0be550bc573545de47ed854 (diff) | |
download | sqlalchemy-93fad8fb0c5421ad162064e0aa506cb1e70cbf2b.tar.gz |
remove "native decimal" warning
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.
Fixes: #7299
Change-Id: Ic570f8107177dec3ddbe94c7b43f40057b03276a
Diffstat (limited to 'lib/sqlalchemy/dialects/postgresql/base.py')
0 files changed, 0 insertions, 0 deletions