You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
insert([]) now inserts a row of database defaults on PostgreSQL, SQLite and MS SQL too, not only on MySQL, so saving an empty form works on every engine
🐛 Bug Fixes
Floats keep their full value, both as bound parameters and inlined in SQL; 1/3 or 1e-11 reach the database exactly as they are in PHP
Selection::insert() with a list of rows returns the number of inserted rows, as documented; code that used the returned ActiveRow now gets an int (#330)
transaction() rethrows the original exception even when the final ROLLBACK fails, e.g. after a deadlock
GroupedSelection::limit() respects the offset when the selection belongs to multiple parent rows, and a Selection over a table without a primary key can be re-queried
Conditions skipped by a short-circuited ?and / ?or no longer leave their parameters behind
A where() identical to an existing JOIN condition is no longer dropped, and binary parameters no longer make distinct conditions collide
Row: isset() and offsetExists() give correct answers, including for falsy values
Reflection is more accurate across drivers: column order of composite foreign keys and indexes (MySQL, PostgreSQL), column defaults (PostgreSQL, #329), primary key and identity columns (MS SQL), tables without an explicit schema (MS SQL), autoincrement detection (SQLite) and table resolution along search_path (PostgreSQL)
MS SQL: identifiers containing [ or ] are escaped correctly, and offset-only or zero-limit queries generate valid SQL
The Tracy panel no longer shows duplicate BlueScreen SQL sections with multiple connections
🛡️ Robustness
Constraint violations on SQL Server, CHECK violations on SQLite and more connection-loss codes on PostgreSQL and MySQL now map to the specific exception classes
Misuse reports a clear exception instead of a PHP error: an unknown PDO driver, page() with less than one item per page, related() on a composite primary key, getInsertId() on a failed lazy connection, an unknown table in Reflection on SQLite, an unknown constant in the DI options; the ambiguous-reference message names the table, key and candidates
The DI extension detects a single connection by the presence of dsn, so key order in the config no longer matters