Trigger logic in EF Code First implementation

Question

I have changed my MVC app database implementation from database first to code first. The only thing left is to move Triggers. I do not know where to put them. Should I put them in Repository and implement them in add/ edit / delete methods? Or maybe there is more appropriated place to execute triggers depending on repositories actions. Please let me any ideas of trigger implementation in Code First approach.

Triggers is a somewhat elusive name here, but it's clear from your question what you're talking about. Where did you have them before? What is so different between DBF and CF that the implementation should differ considerably? — Gert Arnold, Feb 15 '13 at 22:55

score 1 · Accepted Answer · edited May 23 '17 at 12:14

1

Can't offer loads of help here as I've never had to do it, but you could look at overriding DbContext.SaveChanges depending on how many triggers you're talking about...

Update Take a look at this question for a better example.

edited May 23 '17 at 12:14

Community

1
1

answered Feb 15 '13 at 11:25

chrisb

2,200
1
20
23

Trigger logic in EF Code First implementation

1 Answers1