Introduce sqlalchemy 2.0 compatibility

[kurtmckee]

This patch introduces the following changes:

• Enable sqlalchemy 2.0 compatibility warnings during unit testing.
• Update the code, docstrings, and unit tests to support sqlalchemy 2.0 behavior and syntax.

Most of the warnings revolved around the following incompatibilities:

• sqlalchemy 2.0 no longer auto-adds objects across backref relationships.
• sqlalchemy 2.0 no longer auto-commits objects.
• Raw SQL strings must always be wrapped in calls to sqlalchemy.text().
• Query.get() calls must migrate to Session.get().
• select() calls must use positional parameters and must use generative method calls instead of keyword arguments (e.g. select(..., fromobj=...) must become select(...).select_from(...)).

Closes #513.

[kurtmckee]

Resolved merge conflicts

[whwright]

thank you for adding this! any plans to release a new version of sqlalchemy-utils to capture these changes?

[kurtmckee]

Tagging @kvesteri to review this question. 👀

@whwright you're welcome! It was definitely a learning experience! 😀

[kvesteri]

I uploaded new version to PyPi

[kurtmckee]

Thanks @kvesteri!

[mrlonis]

I am unable to use this package with the beta releases of SQL Alchemy 2.0.

from sqlalchemy_utils import Ltree, LtreeType, force_auto_coercion
../../../../venvs/pkg-py-postgres-crud/lib/python3.10/site-packages/sqlalchemy_utils/__init__.py:59: in <module>
    from .types import (  # noqa
../../../../venvs/pkg-py-postgres-crud/lib/python3.10/site-packages/sqlalchemy_utils/types/__init__.py:42: in <module>
    from .uuid import UUIDType  # noqa
../../../../venvs/pkg-py-postgres-crud/lib/python3.10/site-packages/sqlalchemy_utils/types/uuid.py:8: in <module>
    sqlalchemy_version = tuple([int(v) for v in __version__.split(".")])
../../../../venvs/pkg-py-postgres-crud/lib/python3.10/site-packages/sqlalchemy_utils/types/uuid.py:8: in <listcomp>
    sqlalchemy_version = tuple([int(v) for v in __version__.split(".")])
E   ValueError: invalid literal for int() with base 10: '0b3'

Seems to be just a minor version check. I assume this is intentional? I was hoping to see how many things would break with the beta version and I can't tell because SQLAlchemy-Utils fails out

[kurtmckee]

@mrlonis This was fixed in #644 but there hasn't been a sqlalchemy-utils release that includes that fix yet.

I've received permissions to publish new sqlalchemy-utils releases but haven't had a chance to try publishing a new release. I'll try to get that done soon.

Thanks for reporting this!