unstale

pypi / sqlalchemy-risingwave

sqlalchemy-risingwave

What changed in sqlalchemy-risingwave 2, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-25.

8 breaking3 new APIs and options1 behavior and defaults3 fixes and other

See which of these apply to your code, ranked, in your agent:

npx @unstale/cli init

@unstale/cli 0.2.6 on npm

sqlalchemy-risingwave 215 changes

Breaking changes 8

  • Async SQLAlchemy drivers such as asyncpg are not supported by this release.

    2.0.0release notes

  • Native ENUM support is disabled; SQLAlchemy enum values use a VARCHAR fallback.

    2.0.0release notes

  • Foreign-key support and foreign-key reflection are declared unsupported.

    2.0.0release notes

  • Reflection now returns real primary-key metadata where available; inspect constrained_columns rather than treating an empty result as no primary key.

    2.0.0release notes

  • Python 3.8 and 3.9 are dropped; the package now requires Python 3.10+.

    2.0.0release notes

  • SQLAlchemy SERIAL, BIGSERIAL, and SMALLSERIAL DDL is rewritten to INTEGER, BIGINT, and SMALLINT; applications should provide explicit IDs because RisingWave lacks PostgreSQL autoincrement semantics.

    2.0.0release notes

  • SQLAlchemy 1.4 support is dropped; the package now requires SQLAlchemy>=2.0,<2.1.

    2.0.0release notes

  • Native UUID support is disabled; SQLAlchemy UUID values use a VARCHAR fallback.

    2.0.0release notes

New APIs and options 3

  • Adds psycopg3 sync and async driver support through this URL; async engines can use SQLAlchemy create_async_engine.

    2.1.0release notes

  • Adds an optional psycopg3 extra for installing the driver support.

    2.1.0release notes

  • Adds a compatibility shim for Superset SQL Lab cancel-query probes using pg_backend_pid() and pg_terminate_backend(...).

    2.0.0release notes

Behavior and default changes 1

  • An INSERT is not guaranteed to be immediately visible to a following SELECT until a checkpoint/barrier has passed or the user explicitly runs FLUSH;.

    2.0.0release notes

Fixes and other changes 3

  • CHECK, UNIQUE, and FOREIGN KEY constraints should not be relied on for runtime enforcement; the dialect does not strip, emulate, or pretend to enforce them.

    2.0.0release notes

  • Parameterized CHAR, VARCHAR, NUMERIC, and DECIMAL DDL is rendered as unparameterized RisingWave-accepted types.

    2.0.0release notes

  • Reflection and connection metadata paths gain SQLAlchemy 2.0 dialect API compatibility.

    2.0.0release notes