SQL Developer Cart deployment script dependency ordering

The Cart feature in SQL Developer 21.2 allows for the bundling of schema modifications, such as table alterations and constraint updates, into a single exportable SQL script for deployment.

When staging changes for an application migration, the generated script preserves the order in which objects were added to the Cart. However, there is no built-in mechanism to automatically reorder these statements based on object dependencies, such as foreign-key relationships or trigger requirements.

In scenarios requiring zero-downtime schema updates, executing a script with incorrect statement ordering can lead to integrity constraint violations during the migration process.

Technical Uncertainties

• Does SQL Developer provide a configuration setting to enable automated dependency resolution during Cart script generation?
• What is the recommended approach for ensuring correct DDL execution order when utilizing the Cart for complex schema migrations?