Simplifying the Compare DM DDL scripts

[Jonathan Fuerth]

Hi developers,

Thomas Kellerer brought up an interesting point on the forum about how we could make DDL scripts shorter on databases that support the "DROP [object] CASCADE" syntax.

This sounds like something interesting to explore. My first concern is, what do we do about cross-schema constraints? In the current implementation, which drops all constraints we know about before dropping the table/column they depend on, the script would fail at that point. However, by using CASCADE, we would unknowingly and somewhat silently drop those cross-schema constraints, then fail to recreate them later.

Any ideas about this? Can we find a way to deal with this case, or convince ourselves it's not a big deal?

-Jonathan

[Thomas Kellerer]

Hi Jonathan,

> This sounds like something interesting to explore. My first concern is, what
> do we do about cross-schema constraints?

I always felt the that the restriction of the databases to not allow
dropping a table (or column) that is part of a constraint way to
restrictive.
If I want to drop an object then I almost always want to drop
everything related to that.

In a nutshell: I personally wouldn't be concerned about cross schema
constraints because of that.

Regards
Thomas