Schema synchronization script failure during target environment update

When utilizing the schema comparison tool in DataGrip to synchronize a source database with a target environment, the IDE generates DDL scripts based on detected differences. While the tool identifies structural discrepancies, it does not inherently account for data transformation logic required to maintain data integrity during non-destructive schema changes.

In scenarios where a column modification is required without losing existing records, the automatically generated script may attempt a direct alteration that conflicts with existing data constraints or types, potentially leading to execution failures in the SQL console.

• Does DataGrip provide a mechanism to inject custom data transformation logic into the generated migration scripts before execution?
• How can the tool be configured to prioritize non-destructive migration paths over direct structural alterations?