From 0e9eb01721e4538b80508f94bf31503e0d377ba5 Mon Sep 17 00:00:00 2001 From: Vitaly Tomilov Date: Fri, 6 Mar 2015 18:09:36 +0000 Subject: [PATCH] docs update. --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 3124918d..9ebf98e3 100644 --- a/README.md +++ b/README.md @@ -102,11 +102,11 @@ Each query function resolves data according to the Query Result Maskdata is a single object. If the query returns no data or more than one row of data, it is rejected. * `many` - data is an array of objects. If the query returns no rows, it is rejected. * `one` | `none` - data is `null`, if no data was returned; or a single object, if there was one row of data returned. If the query returns more than one row of data, the query is rejected. -* `many` | `none` - data is an array of objects. When no rows returned, `data` is an empty array. +* `many` | `none` - data is an array of objects. When no rows are returned, data is an empty array. If you try to specify `one` | `many` in the same query, such query will be rejected without executing it, telling you that such mask is not valid. -> This is all about writing robust code, when the client declaratively specifies what kind of data it is ready to handle. +> This is all about writing robust code, when the client declaratively specifies what kind of data it is ready to handle, leaving the burden of all extra checks to the library. ### Functions and Procedures In PostgreSQL stored procedures are just functions that usually do not return anything.