Skip running in shadow database

I have a table where end users can insert records, and development needs to insert records via scripts.
If we add them as a migration script, then they fail on the shadow database due to FK constraints.
Our developers use SQL Clone, so everyone would have the FK related records.
Is there a way to mark migration scripts so they don't get run in the shadow database?
Tagged:

Answers

Sign In or Register to comment.