Cursor overview

When you use standard table commands in your sanScript code such as get or change, Dexterity automatically runs a query against the appropriate table on the server. The results of the query are gathered in a cursor.


Groups of records in the cursor are copied to a buffer on the client as they are needed. Each group of records is called a cursor block.


Then individual records are copied from the client buffer to the table buffer.


When the next block of data in the cursor is needed, the current data in the client buffer is released. The table on the server is then queried, and the next block of result data is retrieved and copied to the client buffer.

From sanScript, accessing data in a SQL data source is fundamentally no different than accessing data in c-tree or Pervasive.SQL tables. But, because of the use of cursors, there are some issues you must be aware of. These issues are described in the following sections.

Documentation Feedback