From 0c66bb4020b2030d116a236dfb03806b90d550cc Mon Sep 17 00:00:00 2001 From: Josh Soref Date: Wed, 8 Nov 2017 00:45:05 +0000 Subject: [PATCH] spelling: atomicity --- doc/why-triggerless.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/why-triggerless.md b/doc/why-triggerless.md index 50153b9..2ea8c81 100644 --- a/doc/why-triggerless.md +++ b/doc/why-triggerless.md @@ -16,7 +16,7 @@ Use of triggers simplifies a lot of the flow in doing a live table migration, bu Triggers are stored routines which are invoked on a per-row operation upon `INSERT`, `DELETE`, `UPDATE` on a table. They were introduced in MySQL `5.0`. -A trigger may contain a set of queries, and these queries run in the same transaction space as the query that manipulates the table. This makes for an atomicy of both the original operation on the table and the trigger-invoked operations. +A trigger may contain a set of queries, and these queries run in the same transaction space as the query that manipulates the table. This makes for an atomicity of both the original operation on the table and the trigger-invoked operations. ### Triggers, overhead