SQLAlchemy Deprecated features

[whatnick]

Expected behaviour

Parity with new SQL Alchemy features / deprecations is maintained in the new Index drivers for Postgres/ PostGIS. Perhaps a SQLAlchemy version check if / case statement is applicable for these queries.

Actual behaviour

SQLAlchemy warns of deprecations.

  /env/lib/python3.12/site-packages/datacube/drivers/postgres/_api.py:1107: RemovedIn20Warning: Deprecated API features detected! These feature(s) are not compatible with SQLAlchemy 2.0. To prevent incompatible upgrades prior to updating applications, ensure requirements files are pinned to "sqlalchemy<2.0". Set environment variable SQLALCHEMY_WARN_20=1 to show all deprecation warnings.  Set environment variable SQLALCHEMY_SILENCE_UBER_WARNING=1 to silence this message. (Background on SQLAlchemy 2.0 at: https://sqlalche.me/e/b8d9)
    select([

Steps to reproduce the behaviour

Run datacube code with sqlalchemy 1.4.54

Environment information

• Which datacube --version are you using? - 1.8.19
• What datacube deployment/enviornment are you running against? - CSIRO EASI

Note: Stale issues will be automatically closed after a period of six months with no activity.
To ensure critical issues are not closed, tag them with the Github pinned tag.
If you are a community member and not a maintainer please escalate this issue to maintainers via
GIS StackExchange or Discord.

[SpacemanPaul]

1.9 branch is fully SQLAlchemy2 compatible. I think the resolution of this issue is retiring 1.8