When thinking about schema evolution and starting to plan changes while still in development, the "drop-create" strategy is common.
The cds deploy command will generate the appropriate SQL/DDL statements to effect schema changes. Most commonly this command is run in the planning stages with an option to allow the to-be-executed SQL/DDL statements to be checked, but not executed.
What is that option?
This is a question from the June Developer Challenge on CAP Knowledge. And don't forget: always submit your answer as a hash, on its own - read the Taking part section of the intro post for more info. At the end of today, this question will be updated with links to further reading on this topic.
Further info:
Bluesky
