Activity overview
Latest activity by jspedick
Hi, I am running into a similar issue. We are adding a new default constraint to a table. The addition of the new column with the constraint is detected and included in the deployment as part of the table creation, however there is no if exists statement to check for its existence of the constraint and drop it if it exists. This means our generated deployment script is not re-runnable. Is this a known issue? It does check for existence of the primary key and other index on the table and drops them if they exist, but no check on the newly created default constraint. / comments
Hi, I am running into a similar issue. We are adding a new default constraint to a table. The addition of the new column with the constraint is detected and included in the deployment as part of th...