Alembic-postgresql-enum

Bugs

- [Inconsistent enum value order](31)

Bugs

- [get_defined_enums returned enum names with unexpected prefix](26).
This caused enums in different schemas to be dropped and created each migration

Docs

- pull_request_template.md created
- readme.md internal links on Pypi fixed

Bugs

- [Autogenerate crashes because metadata is a list ([Metadata()]) instead of Metadata()](23).

Features

- [Different schemas support](20). create/drop enum operations now respect schema of Enum
- [native_enum=False support](19). Enums that have native_enum=False are ignored

Features

- [ARRAY support](12). Library now work with enums wrapped inside postgresql arrays
- [Logging](17). Detected changes are being displayed in the console

Bugs

- [Type "..." already exists during table creation](14).
Enum types generated by alembic are now being converted to postgresql.ENUM(..., create_type=False) to avoid conflicts with lines generated by our library
- [op.sync_enum_values does not work on columns that have constraints](11).
Explicit definition of SQL operators added to keep constraint checks consistent across the renaming