Hi everyone,
Last week I have released version 1.0 for my project and deployed it on the production database. Today I have implemented new changes, but after staging these new changes with SQLcl (in /dist/releases/next), I have noticed that it also created new changeset files for all sequences that already existed in v1.0 before. I am using SQLcl Version 25.1.
/dist/releases/next/changes/ms-1/my_schema/sequences:
A drop and re-creation would be an issue here because the sequence is used on a PK column and data already exists on production.
Is this a bug or is it possible to disable this behaviour (eg. via .dbtools/project.config.json)?
Thanks for your help!
Kind regards,
Maurice