Is your feature request related to a problem? Please describe.
Many database management providers support the HIDDEN keyword or VISIBLE/INVISIBLE keywords to hide columns from wildcard operations like SELECT *. When using data access layers like EntityFrameworkCore, certain columns are expected to be hidden. Currently, FluentMigrator does not provide support for such operations, other than to manually create the columns using an "escape hatch" to raw SQL execution, like Execute.Sql, Execute.EmbeddedScript, or Execute.WithConnection
Describe the solution you'd like
Create a file in the top-level adr folder to describe each database providers support for column visibility toggles.
Propose, but do not implement, an API that extends the existing Create.Column and Create.Table("Example").WithColumn("HiddenColumn") with a visibility toggle API.
Additional context
This is unrelated to data masking features introduced to support GDPR.
Is your feature request related to a problem? Please describe.
Many database management providers support the
HIDDENkeyword orVISIBLE/INVISIBLEkeywords to hide columns from wildcard operations likeSELECT *. When using data access layers like EntityFrameworkCore, certain columns are expected to be hidden. Currently, FluentMigrator does not provide support for such operations, other than to manually create the columns using an "escape hatch" to raw SQL execution, likeExecute.Sql,Execute.EmbeddedScript, orExecute.WithConnectionDescribe the solution you'd like
Create a file in the top-level adr folder to describe each database providers support for column visibility toggles.
Propose, but do not implement, an API that extends the existing Create.Column and Create.Table("Example").WithColumn("HiddenColumn") with a visibility toggle API.
Additional context
This is unrelated to data masking features introduced to support GDPR.