sqlite-utils 4.2 enhances table.transform() to preserve check, unique constraints and column comments

The release introduces enhancements to the table.transform() method that enable complex ALTER TABLE operations by creating a fresh table, copying existing data, and then dropping the original. This approach allows schema changes that SQLite does not support directly through ALTER TABLE. During the rebuild, transform() now retains a broader set of edge-case definitions, including check constraints, unique constraints, and column comments. These additions reduce the need for manual schema preservation when altering tables.

Adopting sqlite-utils 4.2 requires upgrading the Python package to the latest release. Users should verify that their workflows do not rely on the previous transform() behavior, especially for tables with check or unique constraints. The initial 4.2 release contained a crashing bug that was addressed in the subsequent 4.2.1 patch, so upgrading to the patched version is recommended. Testing the transform() function on a copy of the database before applying changes to production helps avoid unexpected failures.

The release notes highlight preservation of check constraints, unique constraints, and column comments, implying that other schema features may not be automatically retained. Engineers should verify that any additional constraints or objects they rely on remain intact after using transform(). The initial 4.2 release contained a crashing bug that was fixed in 4.2.1, so using the patched version avoids runtime failures. Testing the transform() operation on a staging copy of the database helps confirm that the expected schema is preserved before applying changes to production.