Limitations

Schemage is intentionally conservative around operations that are difficult to execute safely or portably.

Current limitations:

• PostgreSQL support is not implemented yet.
• Primary-key changes should be handled manually.
• Table recreation should be reviewed carefully when existing data is important.
• Views, triggers, stored procedures, and functions are not managed.
• Online schema-change strategies for very large production tables are not included.
• Schemage is not an ORM and does not provide a query builder.

Primary keys

Changing a primary key can affect foreign keys, identity generation, physical table organization, and application-level identifiers. Schemage does not automatically modify existing primary keys in version 1.0.

SQLite recreation

SQLite uses table recreation for alterations such as modifying columns and changing foreign keys. Schemage copies columns that can be mapped from the current table to the desired table, including explicitly renamed columns.

Always review recreation plans when removing columns or changing incompatible types.