DataGrip 2023.3 Migration Rollback Safety: Automatic vs Manual Inverse Scripts

The goal is to define the default behavior for rollback script generation in DataGrip’s migration tool when handling straightforward DDL changes such as adding a column or altering a data type. The decision must preserve the existing safety guarantee that only reversible changes are marked safe, while avoiding accidental data loss from automatically produced inverses that may not match the user’s intent.

Constraints include the version‑specific rollback safety checks introduced in DataGrip 2023.3, the need to keep the feature usable for teams that rely on explicit rollback scripts, and the requirement to maintain compatibility with older migration histories that lack automatic generation.

Should DataGrip automatically generate an inverse script for simple DDL operations, or should it require users to supply their own rollback? If automatic generation is adopted, what criteria should determine which changes are considered simple enough for safe auto‑generation?