apoc.trigger.remove
This procedure is not intended to be used in a cluster environment, and may act unpredictably. |
Please note that this procedure is deprecated. Use the following ones instead, which allow for better support in a cluster:
where databaseName is the database where we want to execute the triggers. |
Syntax |
|
||
Description |
Removes the given trigger. |
||
Input arguments |
Name |
Type |
Description |
|
|
The name of the trigger to drop. |
|
Return arguments |
Name |
Type |
Description |
|
|
The name of the trigger. |
|
|
|
The query belonging to the trigger. |
|
|
|
|
|
|
|
The parameters for the given Cypher statement. |
|
|
|
Whether or not the trigger was installed. |
|
|
|
Whether or not the trigger was paused. |
Enable Triggers
By default triggers are disabled.
We can enable them by setting the following property in apoc.conf
:
apoc.trigger.enabled=true
apoc.trigger.refresh=60000
Option Key | Value | Description |
---|---|---|
apoc.trigger.enabled |
true/false, default false |
Enable/Disable the feature |
apoc.trigger.refresh |
number, default 60000 |
Interval in ms after which a replication check is triggered across all cluster nodes |
Usage Examples
If we want to remove the trigger created by the example in apoc.trigger.add, we can run the following query:
CALL apoc.trigger.remove("count-removals");
name | query | selector | params | installed | paused |
---|---|---|---|---|---|
"count-removals" |
{} |
{} |
FALSE |
FALSE |