Repository navigation
Remove hacks for some SQlite features #134
Description
Activity
PR #174 selects native SQLite rename/drop operations when supported and eligible, with tested reconstruction retained for other operations. Rebuilds preserve supported dependencies and reject unsupported table properties before dropping the original table. This does not remove every reconstruction path; the issue remains open for the broader request.
Rechecked against merged master c257125: the requested native RenameColumn/DropColumn paths are implemented in merged PR #174 (4749f5d).
RenameColumn uses native ALTER TABLE RENAME COLUMN on SQLite >= 3.26. RemoveColumn uses native ALTER TABLE DROP COLUMN on SQLite >= 3.35 when dependency checks allow it. Native failures are surfaced rather than retried through a potentially lossy reconstruction. Source: https://github.com/dotnetprojects/Migrator.NET/blob/c257125/src/Migrator/Providers/Impl/SQLite/SQLiteTransformationProvider.cs .
The existing unit + SQLite selection passed locally on unchanged master: 284 tests, no failures or skips. This includes NativeDropPreservesTriggerAndForeignKeySetting, NativeDropRejectsDependentTriggerWithoutLosingData, and the SQLite rename-column fixture.
Closing the reported native rename/drop request as completed. Reconstruction remains necessary for unsupported alterations (such as adding/removing foreign-key constraints) and older engines. The previous broader interpretation of this issue should not require removing functionality for which no native equivalent exists.
Sqlite supports more DDL features natively:
RenameColumn, DropColumn, ...