You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
is there any way to exclude system-versioned columns from synchronization using a blacklist,
or is the whitelist approach (as shown in the older example above) the only option?
For example, I have a table like this with two system-versioned columns,
and I need to synchronize it:
CREATE TABLE [WorkPlan](
[WorkPlanId] [uniqueidentifier] NOT NULL,
...
[RecordValidFrom] datetime2 GENERATED ALWAYS AS ROW START NOT NULL,
[RecordValidTo] datetime2 GENERATED ALWAYS AS ROW END NOT NULL,
CONSTRAINT [PK_WORKPLAN] PRIMARY KEY CLUSTERED
(
[WorkPlanId] ASC
) WITH (STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, OPTIMIZE_FOR_SEQUENTIAL_KEY = OFF) ON [PRIMARY],
PERIOD FOR SYSTEM_TIME ([RecordValidFrom], [RecordValidTo])
) ON [PRIMARY]
I can create the whitelist dynamically before each synchronization call by using reflection
on the EF Core entity, but I would prefer not to do that. Ideally, I would like to configure
a blacklist or define this behavior in the setup or directly in the database.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
is there any way to exclude system-versioned columns from synchronization using a blacklist,
or is the whitelist approach (as shown in the older example above) the only option?
For example, I have a table like this with two system-versioned columns,
and I need to synchronize it:
CREATE TABLE [WorkPlan](
[WorkPlanId] [uniqueidentifier] NOT NULL,
...
[RecordValidFrom] datetime2 GENERATED ALWAYS AS ROW START NOT NULL,
[RecordValidTo] datetime2 GENERATED ALWAYS AS ROW END NOT NULL,
CONSTRAINT [PK_WORKPLAN] PRIMARY KEY CLUSTERED
(
[WorkPlanId] ASC
) WITH (STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, OPTIMIZE_FOR_SEQUENTIAL_KEY = OFF) ON [PRIMARY],
PERIOD FOR SYSTEM_TIME ([RecordValidFrom], [RecordValidTo])
) ON [PRIMARY]
I can create the whitelist dynamically before each synchronization call by using reflection
on the EF Core entity, but I would prefer not to do that. Ideally, I would like to configure
a blacklist or define this behavior in the setup or directly in the database.
Is there any supported way to achieve this?
Thanks,
Peter
Beta Was this translation helpful? Give feedback.
All reactions