unstale

pypi / sqlalchemy-exasol

sqlalchemy-exasol

What changed in sqlalchemy-exasol 7, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-25.

3 breaking1 behavior and defaults3 fixes and other

See which of these apply to your code, ranked, in your agent:

npx @unstale/cli init

@unstale/cli on npm

sqlalchemy-exasol 77 changes

Breaking changes 3

  • Values are converted to Python types as early as possible. With PyExasol 3.0.0, INTERVAL DAY TO SECOND and TIMESTAMP WITH LOCAL TIME ZONE return ExaTimeDelta and datetime.datetime, respectively; older PyExasol versions receive improved datetime conversion.

    7.2.0release notes

  • ExaAuthError and ExaRequestError map to DatabaseError instead of OperationalError, while ExaConcurrencyError maps to InterfaceError.

    7.1.4release notes

  • Supported fields now compile to SQL date parts; unsupported fields raise CompileError at compile time.

    7.1.4release notes

Behavior and default changes 1

  • The supported PyExasol version range now includes 3.0.0.

    7.2.0release notes

Fixes and other changes 3

  • Wrapped PyExasol communication errors are recognized as disconnects, allowing pool pre-ping to replace stale connections on first checkout.

    7.1.4release notes

  • Websocket TIMESTAMP results now preserve fractional seconds and naive wall time.

    7.1.4release notes

  • The bare SQLAlchemy entry point now loads the default websocket dialect class directly, preserving support for both exa:// and exa+websocket:// engine URLs.

    7.1.3release notes