EF Core 7 breaking change with triggers

EF Core 7 has a breaking change where tables are assumed to not have triggers by default, and if they do have triggers, inserts and updates fail.

Would it be possible to add a switch to the connection dialog to implement the model building convention that marks all table as having triggers? This isn't as efficient as per table triggers, but at least would allow inserts and updates work with databases containing tables that have triggers. If there is an easy, simple way to implement per-table trigger marking, that would be great.



Sign In or Register to comment.