Releases: exasol/sqlalchemy-exasol
Releases · exasol/sqlalchemy-exasol
3.1.1
3.1.1
- Fixed CI/CD build and publish target
- Fixed CI/CD to run tests against all configured databases
- Updated databases for testing to 7.1.9 and 7.0.18
- Updated pyodbc dependency from 4.0.32 to 4.0.34
- Added new exasol odbc driver 7.1.11
- Added additional badges for to improve project status overview
3.0.0
-
Change build- and config- system
⚠️ ATTENTION⚠️
The support of the turbodbc feature is suspended, until the following issues have been addressed🗒️ If you depend on turbodbc we suggest you to use the latest version supporting it (2.4.0)
-
Update dependencies
-
Remove python 3.7 support
(:spiral_notepad: If you still depend on python 3.7 use the 2.x version line) -
Drop conda forge support
2.4.0
2.4.0
- Fixed bug when accessing underlying odbc connection while using NullPool based engine
(Note: this addresses the superset issue-20105) - Remove odbc specific functionality from base dialect
- Removed remaining python2 compatibility artifacts and switches
- Bump support of base python version to 3.7
2.3.0
- Update supported versions of EXASOL DB to 7.1.6 and 7.0.16
- Update supported python versions to 3.6, 3.7, 3.8, 3.9
- bumped SQLAlchemy dependency to 1.3.24
- bumped pyodbc dependency to 4.0.32
- Fixed bug regarding maximum identifier length
- Fixed bug with custom translate maps
- Fixed bug regarding non existent error code mappings for EXASOL specific odbc error codes
- Updated documentation to reflect the latest version changes etc.
- Updated maintainer and contact information
- Removed outdated documentation and resources
Release 2.0.1
- dropped EXASOL 5 from integration tests
- bumped to SQLAlchemy 1.2.8
- Support the turbodbc parameters
varchar_max_character_limit
,prefer_unicode
,
large_decimals_as_64_bit_types
, andlimit_varchar_results_to_max
.
1.0.0
Release version 0.9.3
See CHANGES.md