You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Migrated issue, originally created by Michael Bayer (@zzzeek)
right now floats are descending from Numeric. we need Float by itself, that takes only the precision as an argument, plus all the database-specific views of it.
The text was updated successfully, but these errors were encountered:
added in changeset:669. I do notice, running the engine test suite, that the float type Postgres converts it to a Real of precision 24, and MySQL converts it to precision 12. also, we dont have an explicit postgres 'bigint' type, should we add that ?
Fixed issue in mypy plugin where newly added support for
:func:`_orm.as_declarative` needed to more fully add the
``DeclarativeMeta`` class to the mypy interpreter's state so that it does
not result in a name not found error; additionally improves how global
names are setup for the plugin including the ``Mapped`` name.
Introduces directory oriented testing as well, where a full
set of files will be copied, mypy runs, then zero or more patches
are applied and mypy is run again, to fully test incremental
behaviors.
Fixes: sqlalchemy/sqlalchemy2-stubs/#14
Change-Id: Ide785c07e19ba0694e8cf6f91560094ecb182016
Migrated issue, originally created by Michael Bayer (@zzzeek)
right now floats are descending from Numeric. we need Float by itself, that takes only the precision as an argument, plus all the database-specific views of it.
The text was updated successfully, but these errors were encountered: