26

I use Entity Framework Migrations for code first to control my database model. It works charming and I can handle until now everything. But now I need to add one database trigger and I would like to do this with EF Migrations and not use a separate sql script for only this case (This would be confusing for clients, esp. after we convinced them that we can handle everything with EF Migrations). My trigger is straight forward and looks like tis:

CREATE OR REPLACE TRIGGER [name] BEFORE UPDATE ON myTable ...

Is there a command to add a trigger to EF Migrations?

StefanG
  • 1,234
  • 2
  • 22
  • 46

2 Answers2

44

You can just add a Sql("SQL COMMAND HERE") method call to your migration's Up method. Don't forget to also add the drop statement to the Down method. You can create an empty migration if you need, just by running Add-Migration without any changes to the model.

public partial class Example : DbMigration
{
    public override void Up()
    {
        Sql("CREATE OR REPLACE TRIGGER [name] BEFORE UPDATE ON myTable ...");
    }

    public override void Down()
    {
        Sql("DROP TRIGGER [name]");
    }
}
Andy Brown
  • 18,961
  • 3
  • 52
  • 62
  • 3
    You can also add IF NOT EXISTS(select * from sys.triggers where name = 'name') to UP() to make it idempotent. – eoghank Feb 13 '14 at 13:44
  • 17
    @eoghank. I'm not sure I agree. The idea of migrations is that they should be repeatable in all directions, and that they therefore prevent that situation occurring. In theory, if we need existence checks, we're not using migrations correctly - as we don't do existence checking for tables, we shouldn't for triggers? – Andy Brown Feb 13 '14 at 14:03
  • 8
    For EF core, use migrationBuilder.Sql("blah blah..."); – wye Jul 27 '17 at 02:08
  • If write such migrations (either for ef, ef core or fluent migrator) I can not use the "Down" part. Example: 1st migration creates a trigger. 2nd migration updates the trigger. I migrate db. Its nice.. the second migration did not fail, because it replaced the trigger from the first migration, but now.. I want to downgrade one step. Ups! I am, technically at migration 1, but there is no trigger bcs it was deleted by the Down step of migration 2. – korulis Dec 16 '20 at 10:42
  • 2
    @korulis, 2nd migration is update, so "Down" for it should be update to the original state (not drop) – Aleksey Cherenkov Jun 09 '21 at 23:10
6

Recently I faced similar problem and didn't find a solution to not write sql manually. So I wrote a little package which allows to write migrations using Ef Core entity builder like this:

modelBuilder.Entity<Transaction>()
    .AfterInsert(trigger => trigger
        .Action(triggerAction => triggerAction
            .Upsert(transaction => new { transaction.UserId },
                insertedTransaction => new UserBalance { UserId = transaction.UserId, Balance = insertedTransaction.Sum },
                (insertedTransaction, oldBalance) => new UserBalance { Balance = oldBalance.Balance + insertedTransaction.Sum })));

This code will be translated into sql and applied to migrations will be looks like

public partial class AddTriggers : Migration
{
    protected override void Up(MigrationBuilder migrationBuilder)
    {
        migrationBuilder.Sql("CREATE FUNCTION LC_TRIGGER_AFTER_INSERT_TRANSACTION() RETURNS trigger as $LC_TRIGGER_AFTER_INSERT_TRANSACTION$ BEGIN INSERT INTO user_balances (user_id, balance) VALUES (NEW.user_id, NEW.sum) ON CONFLICT (user_id) DO UPDATE SET balance = user_balances.balance + NEW.sum; RETURN NEW;END;$LC_TRIGGER_AFTER_INSERT_TRANSACTION$ LANGUAGE plpgsql;CREATE TRIGGER LC_TRIGGER_AFTER_INSERT_TRANSACTION AFTER INSERT ON transactions FOR EACH ROW EXECUTE PROCEDURE LC_TRIGGER_AFTER_INSERT_TRANSACTION();");
    }

    protected override void Down(MigrationBuilder migrationBuilder)
    {
        migrationBuilder.Sql("DROP TRIGGER LC_TRIGGER_AFTER_INSERT_TRANSACTION ON transactions;DROP FUNCTION LC_TRIGGER_AFTER_INSERT_TRANSACTION();");
    }
}

Maybe it will be helpful for someone.

Belyansky Ilya
  • 331
  • 5
  • 4