NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
pub.dev
pub.dev
Runtime support for Angel3 ORM. Includes base classes for queries.
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 27 of 27 stable releases
Nothing withdrawn
no release was ever pulled
6 years old
31 releases · first in 2021
Drag across the ruler to compare, or tap a release to open it.
Breaking: An update or an insert returns each row it wrote, whatever it joins: with the columns of a join that does not match as NULL, where it return
NULL, where it returned no row. A row is returned once with a crossJoin, where it was once for each row of that table, but once for each match of a joinLEFT JOIN updates only the rows of the join, which are those it returns, where it updated every row that matched where, and returned only those. A row without a match is no longer updated. On MySQL, a query that selects no id throws a StateError for such a joinasDateTime uses pg_input_is_valid: it fails with an error on an earlier versiongroupBy, crossJoin, join, leftJoin, rightJoin, fullOuterJoin and selfJoin throw an ArgumentError for a name that is not an identifier, which may be quoted ("order", `order`) and qualified (table.column), and has no leading $, as $$ starts a string and $1 is a parameter on PostgreSQL, as orderBy does when compiled, where it was written into the SQL as given, so a value from a request could add SQL to a query. This covers table names, keys, aliases and additionalFields. The keys, aliases and additionalFields of a join have one part, as the SQL adds their table, and those of a join of a Query are not quoted, as they name its columns (a0_name); groupBy also accepts several columns separated by commas. An expression, or SQL given as a table name, is no longer accepted, and a quoted name has only letters, digits, _ and $: join a Query in place of a subqueryop of a join must be one of =, !=, <>, <, <=, > and >=skipLocked makes an update or a delete skip the rows that another transaction has locked, rather than wait for them, as for a queue that several workers take from at once. It needs a query that selects an id on MySQL 8 or MariaDB 10.6 or later, and an index on its conditions and order thereorderBy accepts a quoted name, as a reserved word must be. Use the quote of the database: on MySQL and MariaDB, by default, "order" is a string, so sorting or grouping by it does nothingfields keeps its joins, which were dropped without an error, so an INNER JOIN filtered nothing. It selects table.*, only the columns of its own tableisIn and isNotIn of a number, an enum or a string with no values are FALSE and TRUE, where they were IN (), which is not valid SQLoffset without a limit has a LIMIT of the greatest value, as MySQL and MariaDB have no OFFSET without one, where it was a syntax errorisIn and isNotIn of no values on a part of a date (year, month, ...) are FALSE and TRUE, where they were a syntax errorINNER JOIN of the table by an alias, where it was SELF JOIN, which is not valid SQLAND to those of its parts (year, month, ...), which it discardedgetByKeys, and is left out of a RETURNING, where it may name a join that is not in scope, as the select around it computes it. A RETURNING has every column of the table, as that select may name any of them, in its order, joins or expressions, as select left out some that it namedlimit are the first in the order of orderBy, which was ignored, so that other rows could be updatedlimit on PostgreSQL are picked by table and ctid, which is unique only within a table, where a partitioned or inherited table had a row of each table updatedlimit on PostgreSQL, of an update or a delete, are locked and read once, as their subquery could otherwise run again and pick others, which would write more than the limit. A connection that waited for a row may still return none: use skipLocked for a queuelimit or a join are picked with the joins of the query, so that an orderBy or a where.raw may name a join, and an orderBy an expression, an alias or a column that a join has too, as in a selectRIGHT JOIN or a FULL OUTER JOIN returns only the rows it wrote, as does a delete, where they returned others of NULL columns, and a limit counts only the rows of its tableselfJoin, reads the table, where it read only the rows it wrote, so that it returned no row. A join sees the table as it was before the statementcrossJoin counts as a join in an update and a delete, which an empty table leaves no row of: they updated or deleted every row that matched where, and returned none. A select qualifies its columns with it, as they may be ambiguousStateError for a limit or an offset, as it could not tell the rows it selected, where a limit could update other rows than those it returned, and an offset was a syntax errorwhere. It updates many rows in parts, as a database binds a limited number of parametersfields, where each was emptygroupBy throws a StateError, where it was written and then failed or returned too few rowscompileForUpdate leaves the values it is given as they are, is empty where it was a bare SET with only a null created_at, and throws an ArgumentError for a key that is not a plain column name, as a key of MapQueryValues was written into the SQL as givenlimit and an offset apply, in the order of orderBy, where they were a syntax error on PostgreSQL, and on MySQL with both. An orderBy without a limit orders the rows returnedlimit, which it selects first, deletes the rows it selected by id, where an INNER JOIN left rows out of those returned but not of those deletedlimit or join deleted by its conditions, and a row another connection added was deleted but not returned. It returns a row that a join repeats once, where a crossJoin returned it once for each row of that tableRIGHT JOIN or a FULL OUTER JOIN cannot be lockedgroupBy throws a StateError where it was a syntax error. So does a delete of a query that selects no id with a limit or an offset on MySQL, or on PostgreSQL with a join or a relation, or with a join other than a LEFT JOIN, as it could not tell the rows it selectedlimit and offset of its query, where its row was filtered out on PostgreSQL, and its row was not selected on MySQLwhere.raw. An executor whose driver rejects those must leave them out, as angel3_orm_postgres 10.1.0 doesasInt or asDouble is compared as a number, where greaterThan compared text, so that 10 was less than 5, and isBetween and isIn were an error. A property that is no number matches no comparisonasDateTime is compared as a date, with a parameter of a valid name and the table name of the query, where its parameter was invalidasDateTime that is no date, or asMap or asList that is no JSON, matches no comparison, so that one such value does not fail the query for every rowisNull and isNotNull of a property asInt, asDouble or asDateTime check the value, so that a value of another type is not nullasMap or asList has predicates of its own, where they named the column twice, and isIn of a property asString has a parameter of a valid name' in the key of a property is escaped, where it was written into the SQL as given, so a key from a request could add SQL to a query' followed: its parameters could keep the value of another query in a union, or be left out of an insertget and getOne load the relations of the rows with those of the left query, as Query does; parseRows of a QueryBase gives them.StateError where a value of its right query that it renamed is still named in its SQL, as it misread a string or a comment of where.raw, or it is in a string, where it would have run with the value of its left query, without an errormapToBool reads the strings f and false, in any case, as falsedefaultDate, and the mapToDateTime of a null, is 1970-01-01 in UTC as documented, where it was in the local time zoneYour coding agent can read these notes before it upgrades. Set up the MCP server →
Logging: debugMode, whether assertions are enabled, and logValues, which logs the values of a query in debug mode only, for executors to log as Query
debugMode, whether assertions are enabled, and logValues, which logs the values of a query in debug mode only, for executors to log as Query doesdart test or dart run --enable-asserts), where they were logged at FINE whenever it was logged; those of an insert without an id and of an update on MySQL are logged too. Log messages are built only when FINE is loggedreturningFields, as its SQL has its RETURNING already, in a WITH clause: an executor that added one, as PostgreSqlPoolExecutor of angel3_orm_postgres 10.0.1 does, failed with a syntax error. QueryExecutor.query documents that its query is completeBreaking: A DateTime in a where clause with its time, such as of lessThan, equals, isBetween or isIn, is bound as a parameter, so the executor sends i
DateTime in a where clause with its time, such as of lessThan, equals, isBetween or isIn, is bound as a parameter, so the executor sends it as it stores a DateTime, where it was written into the SQL as its wall-clock time, whatever its time zone. A local DateTime now matches the rows written with it on PostgreSQL and with MariaDbExecutor, which store a DateTime as UTC, and no longer matches rows they stored as local time before. A QueryExecutor of your own must accept a DateTime parameterDateTime comparison without its time (includeTime: false) compares the date of the DateTime as given, as beforeisIn and isNotIn of a DateTime column with no values are FALSE and TRUE, where they were IN (), which is not valid SQLUnion gives the right query's values names of their own where both queries use one, where the right query used the left one's value. It takes the values of its queries when it is compiled, so it also has those given after it was madeQueryValues.compileInsertSelect is deprecated
get, update, delete and insert return records with the relations loadRelations loads, each with a query of its own after the records: a record is one row, so a limit or offset counts records, and getOne fetches one rowreturningQuery selects the inserted row by the id given, or by @angel3_insert_id (insertIdParameter), which the executor binds to the driver's insert id, instead of the last row by id, which may be another connection'sColumn.precision and Column.scale are int?, and null unless given (were 17 and 3). A numeric or decimal without them is unbounded on PostgreSQLreplacePlaceholders, which swaps @name placeholders for a driver's (e.g. ?)QueryValues.parameterNameOf, and Column.defaultLength, defaultPrecision and defaultScaleQuery.loadRelations, which loads the relations of records that are not joined, such as a has-many, with a query each for all the records, and loadsRelations, getByKeys, pivotKeys, valueOf and joinedRow for it; JoinBuilder.query and JoinBuilder.columnNameFor@HasMany nested in a @HasMany, is no longer dropped; a join that cannot be compiled selects NULLs named as its columns, including those of its own joins, so the columns after it keep their placeStringSqlExpressionBuilder.like passes its pattern as a parameter, where a pattern from user input allowed SQL injection; sanitize is applied to the patternQuery.reserveName never returns the same name twice, so two values of one column no longer overwrite each other (an update with a condition and a new value on one column changed the wrong rows). replacePlaceholders leaves @ in string literals, quoted identifiers and @@variablesupdate and delete select their rows first, in a transaction, and return them. QueryValues.compileInsertSelect is deprecatedupdate(): Returns the rows it updated even when their new values no longer match its conditions, and supports limit() and offset() on PostgreSQLnotWhere is joined with AND NOT, a WHERE no longer starts with AND/OR, and nested and JSON conditions are joined and qualified correctly. Date parts use EXTRACT; DateTime isIn/isNotIn quote the dates; a double is written as a plain numbermapToDouble and mapToInt convert numbers of the other type, BigInts and numeric strings, and throw FormatException for a value that cannot be convertedgetOne: Fetches one row (LIMIT 1) when the query has no joins and no limit of its ownFix analyzer warnings and errors
- Require Dart >= 3.13
- Require Dart >= 3.12.0
Updated dependencies to the latest release
lints to 6.0.0* Updated intl to 0.20.0
intl to 0.20.0Added support for string to bool conversion in the query results
Set createdAt and updatedAt default to CURRENT_TIMESTAMP
createdAt and updatedAt default to CURRENT_TIMESTAMP* Require Dart >= 3.3 * Updated lints to 4.0.0
lints to 4.0.0* Updated repository link
* Updated lints to 3.0.0 * Fixed linter warnings
lints to 3.0.0Updated: angel3_container_generator
* Reduced debugging verbosity
- Require Dart >= 2.17
Fixed issue #68: Support for non-nullable type
defaultValue to @Column annotation* Added mapToDateTime
mapToDateTime- Require Dart >= 2.16 - Added ORM MySQL
* Fixed multiple orderBy error
orderBy error* Added where.raw() * Added select(List fields)
where.raw()select(List fields)Changed default varchar size to 255
* Removed debugging messages
Updated linter to package:lints
package:lintscreatedAt and updatedAt to current datetime as defaultFixed expressions parsing error
Published all packages with angel3_ prefix
angel3_ prefix* Added hasSize to ColumnType
hasSize to ColumnType* Updated README * Fixed NNBD issues
* Fixed static analysis warning
Migrated to support Dart >= 2.12 NNBD
One column per quarter.