From 218b69289bea7ff131b8c38b64db3d23504f7a04 Mon Sep 17 00:00:00 2001 From: Owen Jacobson Date: Sat, 26 Jan 2013 14:42:32 -0500 Subject: Typo police. (Thanks, @jessamynsmith!) --- wiki/mysql/choose-something-else.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'wiki/mysql') diff --git a/wiki/mysql/choose-something-else.md b/wiki/mysql/choose-something-else.md index 5797437..9c7f0bd 100644 --- a/wiki/mysql/choose-something-else.md +++ b/wiki/mysql/choose-something-else.md @@ -628,7 +628,7 @@ table. Table manipulation -- creation, structural modification, and so on -- runs into similar problems. MySQL itself parses each `CREATE TABLE` statement, then hands off a parsed representation to the table engine so that it can manage -storage. The parsed representation lossy: there are plenty of forms MySQL's +storage. The parsed representation is lossy: there are plenty of forms MySQL's parser recognizes that aren't representable in a `TABLE` structure, preventing engines from implementing, say, column or tuple `CHECK` constraints without MySQL's help. -- cgit v1.2.3