summaryrefslogtreecommitdiff
path: root/doc/development/serializing_data.md
diff options
context:
space:
mode:
authorGitLab Bot <gitlab-bot@gitlab.com>2020-02-27 00:09:19 +0000
committerGitLab Bot <gitlab-bot@gitlab.com>2020-02-27 00:09:19 +0000
commit0a0e82d1440b06650e5fc524168b1f50a8feec68 (patch)
treec2202560fb250008cf4109e99537b10604faf01b /doc/development/serializing_data.md
parentf82d5dcab7c3d9a672abc827c92f86887b683a7d (diff)
downloadgitlab-ce-0a0e82d1440b06650e5fc524168b1f50a8feec68.tar.gz
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/serializing_data.md')
-rw-r--r--doc/development/serializing_data.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/serializing_data.md b/doc/development/serializing_data.md
index 37332c20147..af791f5a4e0 100644
--- a/doc/development/serializing_data.md
+++ b/doc/development/serializing_data.md
@@ -20,7 +20,7 @@ alternative.
## Serialized Data Is Less Powerful
When using a relational database you have the ability to query individual
-fields, change the schema, index data and so forth. When you use serialized data
+fields, change the schema, index data, and so forth. When you use serialized data
all of that becomes either very difficult or downright impossible. While
PostgreSQL does offer the ability to query JSON fields it is mostly meant for
very specialized use cases, and not for more general use. If you use YAML in