Unexpected behavior of CONSTRAINT DEFAULT CAST(0 AS BIT) in dacpac converted to CONVERT([bit],(0) in target DB

[ssreerama]

• SqlPackage or DacFx Version: Both
• .NET Framework (Windows-only) or .NET Core: Both
• Environment (local platform and source/target platforms): All

Steps to Reproduce:

1. Create a database and create a table (below syntax) in SSMS
   2.CREATE TABLE [dbo].[Demo] ( [DemoId] INT IDENTITY (1, 1) NOT NULL, [Field1] BIT CONSTRAINT [Field1Constraint] DEFAULT CAST(0 AS BIT) NOT NULL );
2. When script out the created the table, you can observe the CAST(0 AS BIT) changes to CONVERT([bit],(0)).
3. Since both are same according to the engine, but dacfx fails to recognize them and generated the differences, which might cause drop and recreating then column/ater table/ rebuild as well in some scenarios.

Did this occur in prior versions? If not - which version(s) did it work in?

(DacFx/SqlPackage/SSMS/Azure Data Studio) All

[IVNSTN]

more functions with this effect listed here #350