mirror/dolt
1
0
Fork 0
mirror of https://github.com/dolthub/dolt.git synced 2026-02-11 10:33:08 -06:00
Code Issues Packages Projects Releases 128 Wiki Activity

Update intro.md

Browse Source 
Fix typos
This commit is contained in:
Erik Arvidsson
2016-06-02 17:59:09 -07:00
parent b442b3b716
commit 9b91c204d4
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
doc/intro.md
View File

@@ -41,7 +41,7 @@ noms sync http://localhost:8000:foo http://localhost:8000:bar
This command is trivial and causes basically zero IO. Noms checks whether the destination database has the chunk pointed to by `foo`, finds that it does (obviously, because it is in the same database), and then adds a new dataset pointing at that chunk.
Syncs across database can be effiicent by the same logic if the destination database already has all or most of the chunks required chunks.
Syncs across database can be efficient by the same logic if the destination database already has all or most of the chunks required chunks.
See [Noms Command Line Tour](cli-tour.md) for more on the command-line interface to Noms.
@@ -85,7 +85,7 @@ Strings, numbers, unions, and structs are not chunked, and should be used for "r
Types serve several purposes in Noms:
1. Most importantly, types allow Noms data to be self-describing. Ever Noms chunk has a header that describes its type. This means that anyone (or any software) can look at the header of a chunk and know the shape of all the data reachable via that chunk with some precision. This makes writing code that works with Noms much less error-prone. In languages that support generics, one can work with Noms data in a completely statically typed way.
1. Most importantly, types allow Noms data to be self-describing. Every Noms chunk has a header that describes its type. This means that anyone (or any software) can look at the header of a chunk and know the shape of all the data reachable via that chunk with some precision. This makes writing code that works with Noms much less error-prone. In languages that support generics, one can work with Noms data in a completely statically typed way.
2. Users of Noms can define their own structures and publish data that uses them. This allows for ad-hoc standardization of types within communities working on similar data.
@@ -168,4 +168,4 @@ Also, because Noms collections are ordered search trees, it is possible to imple
So, for example, if you wanted to find all the people of a particular age AND having a particular hair color, you could construct a second map having type `Map<String, Set<Person>>`, and intersect the two sets.
Over time, we plan to develop this basic capability into support for some kind of generalized query system.
Over time, we plan to develop this basic capability into support for some kind of generalized query system.