From 80fc1a8613a266a32a6906fe86ee44c1549033d8 Mon Sep 17 00:00:00 2001
From: James Ahlborn <jtahlborn@yahoo.com>
Date: Wed, 6 Nov 2013 03:25:46 +0000
Subject: [PATCH] cookbook updates

git-svn-id: https://svn.code.sf.net/p/jackcess/code/jackcess/trunk@833 f203690c-595d-4dc9-a70b-905162fa7fd2
---
 src/site/xdoc/cookbook.xml | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)

diff --git a/src/site/xdoc/cookbook.xml b/src/site/xdoc/cookbook.xml
index 2d0ec1b..7bb31a9 100644
--- a/src/site/xdoc/cookbook.xml
+++ b/src/site/xdoc/cookbook.xml
@@ -266,6 +266,25 @@
     </section>
 
     <section name="Finding Stuff">
+      <subsection name="Cursors, what are they good for?">
+        <p>
+          Actually, a lot!  Now that we've covered the basics, let's move into
+          some intermediate level topics.  The first and foremost is the use
+          of the <a
+          href="apidocs/com/healthmarketscience/jackcess/Cursor.html">Cursor</a>.
+          As mentioned earlier, Cursors are the best way to interact with the
+          data in a Table (beyond trivial data entry).  If you are familiar
+          with databases in general, then cursors should be a familiar idea.
+          A Cursor is, in essence, the combination of a Table and a "bookmark"
+          pointing to a Row of data in the Table.  The various Cursor
+          operations either move the bookmark around within the Table or
+          provide read/write operations on the current Row.  While caching and
+          re-using Cursor instances will provide benefits with respect to both
+          speed and memory, they are "lightweight" enough to be used in an
+          on-demand capacity.
+        </p>
+      </subsection>
+
       <p>
         FIXME, writeme
       </p>
-- 
2.39.5