Including child dependencies without parent works if added from "empty" changeset

[Benjin]

Repro:
0. Create two new databases, e.g. DatabaseOne and DatabaseTwo

1. In DatabaseOne, create two tables with a PK/FK relationship:

CREATE TABLE ParentTable (
    ParentID INT PRIMARY KEY,
    ParentName NVARCHAR(50) NOT NULL
);

CREATE TABLE ChildTable (
    ChildID INT PRIMARY KEY,
    ChildName NVARCHAR(50) NOT NULL,
    ParentID INT NOT NULL,
    FOREIGN KEY (ParentID) REFERENCES ParentTable(ParentID)
);

2. Compare from DatabaseOne (with tables) -> DatabaseTwo (empty db)
3. Try to exclude ParentTable -> see error that a dependent exists (correct)
4. Exclude everything using "Exclude all changes" checkbox -> succeeds (correct)
5. Re-add only ChildTable

Expected:

• Error because ParentTable needs to be there first

Reality:

• No error, UI shows ParentTable excluded
• Clicking "generate script" produces a script that creates both ChildTable and ParentTable
• Applying changes also creates both tables, despite ParentTable being excluded

[lewis-sanchez]

@Benjin, did Azure Data Studio allow this or did it show an error message like you were expecting?

[Benjin]

Looks like ADS has the same behavior that I'm seeing in MSSQL. That'd make this not a blocker for Public Preivew since it isn't a regression.