From 82e97c863657f91cbf3b54518c917f6cd43bafa0 Mon Sep 17 00:00:00 2001 From: Valeria Khokha <32414756+ValeriaKhokha@users.noreply.github.com> Date: Thu, 8 Apr 2021 16:23:18 +0300 Subject: [PATCH 1/2] Update data_model.rst --- doc/book/box/data_model.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/book/box/data_model.rst b/doc/book/box/data_model.rst index 8132323b82..3d4ac99338 100644 --- a/doc/book/box/data_model.rst +++ b/doc/book/box/data_model.rst @@ -40,7 +40,7 @@ Tarantool operates data in the form of tuples. They play the same role as "row columns" or "record fields" in relational databases, with a few improvements: - * fields can be composite structures, such as arrays or maps, and + * fields can be composite structures, such as arrays or maps, * fields don't need to have names. A given tuple may have any number of fields, and the fields may be of @@ -73,9 +73,9 @@ In our example there's a space called ``'tester'``. At least one space is required to store data with Tarantool. Each space has the following attributes: - * a unique **name** specified by the user + * a unique **name** specified by the user, * a unique **numeric identifier** which can be specified by - the user, but usually is assigned automatically by Tarantool. + the user, but usually is assigned automatically by Tarantool, * an **engine**: *memtx* (default) -- in-memory engine, fast but limited in size, or *vinyl* -- on-disk engine for huge data sets. From 7a1bf1000dc5aefd2fde6cbd18aecd2ee35727cd Mon Sep 17 00:00:00 2001 From: Valeria Khokha <32414756+ValeriaKhokha@users.noreply.github.com> Date: Thu, 8 Apr 2021 16:23:18 +0300 Subject: [PATCH 2/2] Update data_model.rst fix #2029 --- doc/book/box/data_model.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/book/box/data_model.rst b/doc/book/box/data_model.rst index 8132323b82..3d4ac99338 100644 --- a/doc/book/box/data_model.rst +++ b/doc/book/box/data_model.rst @@ -40,7 +40,7 @@ Tarantool operates data in the form of tuples. They play the same role as "row columns" or "record fields" in relational databases, with a few improvements: - * fields can be composite structures, such as arrays or maps, and + * fields can be composite structures, such as arrays or maps, * fields don't need to have names. A given tuple may have any number of fields, and the fields may be of @@ -73,9 +73,9 @@ In our example there's a space called ``'tester'``. At least one space is required to store data with Tarantool. Each space has the following attributes: - * a unique **name** specified by the user + * a unique **name** specified by the user, * a unique **numeric identifier** which can be specified by - the user, but usually is assigned automatically by Tarantool. + the user, but usually is assigned automatically by Tarantool, * an **engine**: *memtx* (default) -- in-memory engine, fast but limited in size, or *vinyl* -- on-disk engine for huge data sets.