The Postgresql varient caused MySQL migrations to throw the following:
```
sqlalchemy.exc.UnsupportedCompilationError: Compiler <sqlalchemy.dialects.mysql.base.MySQLDDLCompiler object at 0x7f47b1a89220> can't render element of type <class 'sqlalchemy.dialects.postgresql.base.CreateEnumType'> (Background on this error at: https://sqlalche.me/e/14/l7de)
```

Issue #562

Issue #562

This reverts commit c42c9d9b.

Issue #562

Issue #562

Issue #562

Issue #562

fix: Fix sql query, where table is being selected, which treats first argument as a where clause, resulting in the column being added to "WHERE" without an operator.

This resulted in:
```
sqlalchemy.exc.ProgrammingError: (psycopg2.errors.DatatypeMismatch) argument of AND must be type boolean, not type character varying
```

Issue #562

Ensure all appropriate environment variables are mocked

Issue #562

This ensures that the ordering of data is consistent between all database engines.
Update expected results to in tests to match new ordering.

Issue #562

Issue #562

fix: Include all selected fields that are grouped by in analytics base and module usage count queries

This avoids Postgres errors, similar to:
```
sqlalchemy.exc.ProgrammingError: (psycopg2.errors.GroupingError) column "namespace.namespace" must appear in the GROUP BY clause or be used in an aggregate function
```

Issue #562

test: Reset ID column sequences during test setup for tables that insert data with the ID column manually specified.

Postgres uses sequences that are not incremented when the field is manually set, causing primary key validation errors

Issue #562

fix: Include ID column in analytics query, as this is used in the group_by, meaning it must be included in the selected fields, otherwise Postgres will throw an error

Issue #562

Add method to perform enum migrations and create temporary type as enums cannot be changed in Postgres (or at least the values cannot be completely arbitrarily changed)

Issue #562

fix: Replace use of `lastrowid` with `inserted_primary_key` when obtaining primary key values of inserted rows.

The previous method did not appear to work with Postgres

Issue #562

Issue #562

Issue #562

Re-added package after move to poetry

Issue #562

Issue #562

# [4.0.0](v3.13.5...v4.0.0) (2025-04-19)

* feat(build)!: Switch to Poetry for dependency management ([4365ac1a](4365ac1a)), closes [#565](#565)

### BREAKING CHANGES

* Moving package management to poetry, meaning that binaries/scripts must be executed with `poetry run`.
This may break integrations where scripts are being run within the container.
Ensure any pre-existing configuration that executes scripts within the container are prepended with `poetry run`.
NOTE: The use of requirements-*.txt files is now **deprecated** and will be removed in future minor/patch versions.

Merge branch '565-move-from-pip-file-to-alternative-depdency-locking' into 'main'

Resolve "Move from pip file to alternative dependency locking"

BREAKING CHANGE: Moving package management to poetry, meaning that binaries/scripts must be executed with `poetry run`.
This may break integrations where scripts are being run within the container.
Ensure any pre-existing configuration that executes scripts within the container are prepended with `poetry run`.
NOTE: The use of requirements-*.txt files is now **deprecated** and will be removed in future minor/patch versions.

Merge branch '565-move-from-pip-file-to-alternative-depdency-locking' into 'main'

Resolve "Move from pip file to alternative dependency locking"

Closes #565

See merge request !445

Issue #565

build: Simplify installation of python packages and docker args for pypi index and install concurrency

Issue #565

Issue #565

Issue #565

Issue #565

It is actually the build agent has a _really_ bad upstream (powerline ethernet) and it's causing the DNS server to mark the upstream as failed and DNS just fails... for everything :(

Issue #565

Issue #565

Issue #565

Revert adding venv bin to PATH (as, although this will work, the remainder of the venv won't work) and instead symlink /app's venv to the CWD's venv

Issue #565

build: Update poetry to use venvs, but store in project (e.g. in /app) and add the poetry bin path of the project to PATH to allow it to execute scripts (e.g. alembic)

Issue #565

Issue #565

Issue #565

ci: Disable creation of poetry virtualenv as this does not work well when the application directory is added/removed/changed

Issue #565

Issue #565

Issue #565

Issue #565

Issue #565

Issue #565