summaryrefslogtreecommitdiff
path: root/sql/event_parse_data.cc
diff options
context:
space:
mode:
authorIan Gilfillan <github@greenman.co.za>2020-07-14 00:42:47 +0200
committerAnel <an3l@users.noreply.github.com>2020-07-22 23:18:12 +0200
commitd2982331a62e22ff10fd7768f450303bc90d1caf (patch)
treee1f6f08983de4626d66e5b93e5c1f5399c3bff9c /sql/event_parse_data.cc
parent62d73df6b270cc94ba577e96d3bf325170f306fe (diff)
downloadmariadb-git-d2982331a62e22ff10fd7768f450303bc90d1caf.tar.gz
Code comment spellfixes
Diffstat (limited to 'sql/event_parse_data.cc')
-rw-r--r--sql/event_parse_data.cc6
1 files changed, 3 insertions, 3 deletions
diff --git a/sql/event_parse_data.cc b/sql/event_parse_data.cc
index 3dbcaba8bb0..92ba27a25a1 100644
--- a/sql/event_parse_data.cc
+++ b/sql/event_parse_data.cc
@@ -100,7 +100,7 @@ Event_parse_data::init_name(THD *thd, sp_name *spn)
ENDS or AT is in the past, we are trying to create an event that
will never be executed. If it has ON COMPLETION NOT PRESERVE
(default), then it would normally be dropped already, so on CREATE
- EVENT we give a warning, and do not create anyting. On ALTER EVENT
+ EVENT we give a warning, and do not create anything. On ALTER EVENT
we give a error, and do not change the event.
If the event has ON COMPLETION PRESERVE, then we see if the event is
@@ -359,7 +359,7 @@ wrong_value:
EVERY 5 MINUTE STARTS "2004-12-12 10:00:00" means that
the event will be executed every 5 minutes but this will
start at the date shown above. Expressions are possible :
- DATE_ADD(NOW(), INTERVAL 1 DAY) -- start tommorow at
+ DATE_ADD(NOW(), INTERVAL 1 DAY) -- start tomorrow at
same time.
RETURN VALUE
@@ -413,7 +413,7 @@ wrong_value:
EVERY 5 MINUTE ENDS "2004-12-12 10:00:00" means that
the event will be executed every 5 minutes but this will
end at the date shown above. Expressions are possible :
- DATE_ADD(NOW(), INTERVAL 1 DAY) -- end tommorow at
+ DATE_ADD(NOW(), INTERVAL 1 DAY) -- end tomorrow at
same time.
RETURN VALUE