unstale

pypi / pymonetdb

pymonetdb

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

1 breaking2 new APIs and options1 behavior and defaults1 tooling6 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

pymonetdb 111 changes

Breaking changes 1

  • Fetching OID columns now returns a string representation of the OID, such as 10@0, instead of function objects.

    1.9.1release notes

New APIs and options 2

  • Adds support for the inet4 type introduced in the upcoming MonetDB Dec2025 release.

    1.9.0release notes

  • Adds support for the inet6 type introduced in the upcoming MonetDB Dec2025 release.

    1.9.0release notes

Behavior and default changes 1

  • INFO-level log messages are now DEBUG, except for info messages sent by the server.

    1.9.0release notes

Tooling 1

  • Includes py.typed to silence mypy warnings in Python code that depends on pymonetdb.

    1.9.0release notes

Fixes and other changes 6

  • The field now correctly reflects autocommit status changes caused by SQL statements such as START TRANSACTION, COMMIT, or ROLLBACK.

    1.9.1release notes

  • The value is now set correctly: it is None when a Cursor is created and is reset when the Cursor switches to a new result set.

    1.9.1release notes

  • Cursor.execute() now supports the ipaddress type, which was already supported by Cursor.fetch* methods.

    1.9.1release notes

  • No-such-database errors encountered while scanning /tmp for the right server socket are no longer logged at level ERROR.

    1.9.1release notes

  • Adds support for Python 3.14.

    1.9.0release notes

  • Version numbers now follow Semantic Versioning: patch releases are bug fixes, minor releases are backward compatible, and major releases are backward incompatible.

    1.9.0release notes