Behavior of `bal persist pull` when database schema undergoes destructive changes
Goal: Understand the expected behavior of the bal persist pull command when the underlying relational database has experienced destructive changes such as dropped tables or columns after the persistence model was initially generated. Constraint: The persistence model produced by bal persist pull is treated as regenerable output and is overwritten on each inv
ballerina