NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
pub.dev
pub.dev
PostgreSQL support for Angel3 ORM. Includes functionality for querying and transactions.
Latest stable
10.1.0
Last release 15 days ago
07 Nov 2026
Release timing varies
gaps range from 1 weeks to 10 months
Nearly every release is documented
notes for 26 of 26 stable releases
Nothing withdrawn
no release was ever pulled
6 years old
28 releases · first in 2021
Drag across the ruler to compare, or tap a release to open it.
Breaking: PostgreSQL 16 or later is required, where it was 14
PostgreSqlExecutor and PostgreSqlPoolExecutor leave out a value a query does not use, which the driver names as it rejects it, so that one set by hand and named only in a comment of where.raw does not fail the query`PostgreSqlPoolExecutor`: Runs its queries as PostgreSqlExecutor does, so it logs them, and the errors of the database, at FINE
PostgreSqlPoolExecutor: Runs its queries as PostgreSqlExecutor does, so it logs them, and the errors of the database, at FINEPostgreSqlExecutor and PostgreSqlPoolExecutor log the values of a query, which may be passwords or personal data, in debug mode only, with assertions enabled, as angel3_orm does, where PostgreSqlExecutor logged them at FINE whenever it was logged. It no longer logs the returning query, which only MySQL uses. Their log messages, and the errors they log, are built only when they are logged. Requires angel3_orm 10.0.2Key (email)=(alice@example.com) already exists), and with the quoted text of its message left out (as the value of invalid input syntax for type uuid: "alice@example.com"), but with its code, message, and the schema, table, column and constraint it concerns; in debug mode, it is logged in fullFINE, with its stack trace, where it was logged at WARNING without it, as it is thrown to the caller, who may expect it, as a unique violation. A broken connection is still logged at WARNINGPostgreSqlExecutor: Queries that fail on a broken connection at the same time share one new session, where each opened one, and all but one were left open; the broken connection is closed, forced, and a failure to close it is logged, where it was an unhandled errorPostgreSqlExecutor: With an endpoint, a connection that broke, as during a query, is replaced before the next query runs; a query that was sent when it broke is thrown, not sent again, as it may have run, and only one that was not sent is sent again, on the new connectionPostgreSqlExecutor: After close, no new connection is opened, and one being opened to replace a broken connection is closed once opened, where it was left openPostgreSqlExecutor: With an endpoint, transaction runs on a new connection when the one it has broke, as when the database restarted, where it failed until a query replaced it; it shares the new connection with the queries that replace it at the same timePostgreSqlExecutor: Without an endpoint, a query on a broken connection throws the error of the connection, where it tried to open a new connection, logged that it was doing so, and threw Unable to create new connection. It warns once that the connection cannot be replaced, not for each query The constructor tells that its endpoint and settings are what lets it replace a broken connectionPostgreSqlPoolExecutor in 10.0.2 made a delete work too, which failed with the same syntax error at or near "RETURNING" as an insert; its entry names inserts onlyYour coding agent can read these notes before it upgrades. Set up the MCP server →
`PostgreSqlPoolExecutor`: An insert works, where it failed with syntax error at or near "RETURNING", as the executor added a RETURNING clause after th
PostgreSqlPoolExecutor: An insert works, where it failed with syntax error at or near "RETURNING", as the executor added a RETURNING clause after the one angel3_orm 10 puts in the insert's WITH clause. Its queries are run as given, as by PostgreSqlExecutorBreaking: A local DateTime is stored as UTC, and read back as the same moment, as UTC. It was read back shifted by its time-zone offset, as a timestam
DateTime is stored as UTC, and read back as the same moment, as UTC. It was read back shifted by its time-zone offset, as a timestamp column kept its wall-clock time and dropped its offset. Rows written by an app outside UTC before this release hold its local time: they are still read back shifted, and a where clause on them no longer matches. To fix them, run an UPDATE such as SET created_at = created_at AT TIME ZONE '<the app's time zone>' AT TIME ZONE 'UTC' on each timestamp columnDateTime written to a date column is the date of its UTC time, so a local midnight east of UTC is the day before. Write a date as DateTime.utc(year, month, day)where clause on a local DateTime matches the rows written with it. Requires angel3_orm 10.0.1Breaking: An error of a transaction, such as a PgException of the database or one its callback throws, is thrown as it is, where it was a StateError('
transaction, such as a PgException of the database or one its callback throws, is thrown as it is, where it was a StateError('The transaction was cancelled.') without the error or its stack traceangel3_orm 10, and postgres 3.5.20, which throws the error of a transaction rather than that of its rollback, recovers a transaction after a rollback to a savepoint, returns the rows of the statement after a failed one, and fails a transaction started from inside its own callback rather than deadlocktransaction on the executor its callback is given runs in a savepoint of that transaction, as PostgreSQL does not nest transactions: what it does is rolled back if it throws, even when the outer callback catches its error, and committed with the outer transaction otherwise. Savepoints at one level of nesting run one at a time, as they form a stack, whichever executor of the transaction they are made with, and one made inside another runs at the next level, so it does not wait for it; a savepoint that waits for another at its level that it did not start inside itself waits forever; a savepoint whose callback leaves the transaction aborted, by catching an error of the database, is rolled back to as if the callback threw; and one that cannot be rolled back to throws the error of its rollback. Each savepoint has a name of its own, and a transaction or savepoint waits for the savepoints started inside it, even ones its callback does not await, before it is committed, released or rolled back, as that would end them too; a call made after its savepoint ended, such as from a timer, runs in the one around it. A query on the transaction's executor while a savepoint of it is open is part of that savepoint. It threw a TypeError. Calling transaction on the executor of the connection from inside the callback still throws, as the connection is in usePostgreSqlPoolExecutor.transaction behaves as that of PostgreSqlExecutor, with savepoints for a transaction nested through the executor its callback is givenfine rather than as a warning, as its error is thrown to the caller; query still logs an error of the database as a warning- Require Dart >= 3.13
- Require Dart >= 3.12.0
Updated dependencies to the latest release
lints to 5.0.0lints to 6.0.0Added support for Entity and Entity as data model
<Class>Entity and Entity<Class> as data model_<Class> to <Class>EntityFixed issues due to breaking changes in analyzer 7.3.0
analyzer 7.3.0Updated dependencies to the latest release
lints to 5.0.0Query.parseRow (#98)angel3_orm_testangel3_orm_test* Fixed analyzer warnings
* Updated dependencies
* Require Dart >= 3.3 * Updated lints to 4.0.0
lints to 4.0.0[BREAKING] Updated postgres to 3.0.0
lints to 3.0.0postgres to 3.0.0Updated: angel3_container_generator
* Reduced debugging verbosity
- Require Dart >= 2.17
Fixed #71. Restablish broken connection automatically.
- Require Dart >= 2.16 - Added ORM MySQL
Fixed test cases failing on terminaless stdout
stdout* Fixed null safety errors
Added package:postgres_pool for connection pooling
package:postgres_pool for connection poolingUpdated linter to package:lints
package:lints* Fixed json data issue
Changed Dart SDK requirements for all packages to ">=2.10.0 <3.0.0"
* Updated README
Migrated to support Dart >= 2.12 NNBD
One column per quarter.