Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify that drop_trigger uses different parameters than create_trigger #112

Merged
merged 1 commit into from
Jan 2, 2024
Merged

Clarify that drop_trigger uses different parameters than create_trigger #112

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -202,6 +202,15 @@ you need to actually implement `up`/`down` methods in your migration
(rather than `change`) so that it does the right thing when
rolling back.

The `drop_trigger` currently only supports the `drop_trigger(name, table, options = {})`
format. You will need to determine what the resulting trigger name is (e.g. `SHOW TRIGGERS`
query) and use that name in the `drop_triggers` call. Your `down` migration method
might contain something like:

```ruby
drop_trigger(:users_after_insert_row_tr, :transactions)
```

#### Manual triggers and :compatibility

As bugs are fixed and features are implemented in HairTrigger, it's possible
Expand Down