From 56ebc6a65698153d80d99ae034c1c90d612d6925 Mon Sep 17 00:00:00 2001 From: Desmond Brand Date: Wed, 18 Mar 2015 00:40:22 -0700 Subject: [PATCH] Fix typo: itterate -> iterate --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 16adc25f..1cddfbfd 100644 --- a/README.md +++ b/README.md @@ -5,7 +5,7 @@ Use a PostgreSQL result cursor from node with an easy to use API. ### why? -Sometimes you need to itterate through a table in chunks. It's extremely inefficient to use hand-crafted `LIMIT` and `OFFSET` queries to do this. +Sometimes you need to iterate through a table in chunks. It's extremely inefficient to use hand-crafted `LIMIT` and `OFFSET` queries to do this. PostgreSQL provides built-in functionality to fetch a "cursor" to your results and page through the cursor efficiently fetching chunks of the results with full MVCC compliance. This actually ends up pairing very nicely with node's _asyncness_ and handling a lot of data. PostgreSQL is rad.