Skip to content

Releases: agronholm/sqlacodegen

3.2.0

29 Nov 20:33
615d79c

Choose a tag to compare

  • Dropped support for Python 3.9 (PR by @agronholm)
  • Fix Postgres DOMAIN adaptation regression introduced in SQLAlchemy 2.0.42 (PR by @sheinbergon)
  • Support disabling special naming logic for single column many-to-one and one-to-one relationships (PR by @Henkhogan, revised by @sheinbergon)
  • Add include_dialect_options option to render Table and Column dialect-specific kwargs and info in generated code. (PR by @jaogoy)
  • Add keep_dialect_types option to preserve dialect-specific column types instead of adapting to generic SQLAlchemy types. (PR by @jaogoy)

3.1.1

04 Sep 09:34
a1f22fc

Choose a tag to compare

  • Fallback NotImplemented errors encountered when accessing python_type for non-native types to typing.Any (PR by @sheinbergon, based on work by @danplischke)

3.1.0

10 Aug 20:45
4b37d5d

Choose a tag to compare

  • Type annotations for ARRAY column attributes now include the Python type of the array elements (PR by @@JoaquimEsteves)
  • Added support for specifying engine arguments via --engine-arg (PR by @LajosCseppento)
  • Fixed incorrect package name used in importlib.metadata.version for sqlalchemy-citext, resolving PackageNotFoundError (PR by @oaimtiaz)
  • Prevent double pluralization (PR by @dkratzert, remedied by @sheinbergon)
  • Fixes DOMAIN extending JSON/JSONB data types (PR by @sheinbergon)
  • Temporarily restrict SQLAlchemy version to 2.0.41 (PR by @sheinbergon)
  • Fixes add_import behavior when adding imports from sqlalchemy and overall better alignment of import behavior(s) across generators (PR by @EthanKim8683)
  • Fixes nullable column behavior for non-null columns for both sqlmodels and declarative generators (PR by @sheinbergon)

3.0.0

28 Feb 13:53

Choose a tag to compare

  • Dropped support for Python 3.8 @agronholm
  • Changed nullable relationships to include Optional in their type annotations @sheinbergon
  • Fixed SQLModel code generation @sheinbergon
  • Fixed two rendering issues in ENUM columns when a non-default schema is used: an unwarranted positional argument and missing the schema argument @agronholm
  • Fixed AttributeError when metadata contains user defined column types @agronholm
  • Fixed AssertionError when metadata contains a column type that is a type decorator with an all-uppercase name @agronholm
  • Fixed MySQL DOUBLE column types being rendered with the wrong arguments @agronholm

3.0.0rc5

22 Feb 08:54

Choose a tag to compare

  • Fixed pgvector support not working

3.0.0rc4

14 Feb 10:30

Choose a tag to compare

  • Dropped support for Python 3.7
  • Dropped support for SQLAlchemy 1.x
  • Added support for the pgvector extension (with help from KellyRousselHoomano)