Crate

What's Changed

- Fixed SQLAlchemy 2.0 incompatibility with ``CrateDialect.{has_schema,has_table}``

**Full Changelog**: https://github.com/crate/crate-python/compare/0.30.0...0.30.1

What's Changed

- Added deprecation warning about dropping support for SQLAlchemy 1.3 soon, it is effectively EOL.
- Added support for SQLAlchemy 2.0. See also [What's New in SQLAlchemy 2.0](https://docs.sqlalchemy.org/en/20/changelog/whatsnew_20.html) and [SQLAlchemy 2.0 migration guide](https://docs.sqlalchemy.org/en/20/changelog/migration_20.html).
- Updated to geojson 3.0.0.


**Full Changelog**: https://github.com/crate/crate-python/compare/0.29.0...0.30.0

What's Changed
- SQLAlchemy: Added support for `crate_index` and `nullable` attributes in ORM column definitions.

- Added support for converting `TIMESTAMP` columns to timezone-aware `datetime` objects, using the new `time_zone` keyword argument.

**Full Changelog**: https://github.com/crate/crate-python/compare/0.28.0...0.29.0

What's Changed
- Added a generic data type converter to the ``Cursor`` object, for converting
fetched data from CrateDB data types to Python data types.

- Fixed generating appropriate syntax for OFFSET/LIMIT clauses. It was possible
that SQL statement clauses like ``LIMIT -1`` could have been generated. Both
PostgreSQL and CrateDB only accept ``LIMIT ALL`` instead.

- Added support for computed columns in the SQLAlchemy ORM.

**Full Changelog**: https://github.com/crate/crate-python/compare/0.27.2...0.28.0

What's Changed
- Improved SQLAlchemy's ``CrateDialect.get_pk_constraint`` to be compatible with breaking changes in CrateDB >=5.1.0.

**Full Changelog**: https://github.com/crate/crate-python/compare/0.27.1...0.27.2

What's Changed
- Fixed regression introduced by ``0.27.0`` resulting in unavailable servers if
all configured servers aren't reachable once.

**Full Changelog**: https://github.com/crate/crate-python/compare/0.27.0...0.27.1