Skip to content

fetch-and-update-rowsets-odbc.md

Latest commit

 

History

History
46 lines (31 loc) · 2.73 KB

fetch-and-update-rowsets-odbc.md

File metadata and controls

46 lines (31 loc) · 2.73 KB
title Fetch and Update Rowsets (ODBC) | Microsoft Docs
ms.custom
ms.date 03/06/2017
ms.prod sql
ms.prod_service database-engine, sql-database, sql-data-warehouse, pdw
ms.reviewer
ms.technology native-client
ms.topic reference
helpviewer_keywords
rowsets [ODBC]
ms.assetid cf0eb3b4-8b72-49fc-a845-95edc360cf93
author markingmyname
ms.author maghan
monikerRange >=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-server-2016||=sqlallproducts-allversions||>=sql-server-linux-2017||=azuresqldb-mi-current

Fetch and Update Rowsets (ODBC)

[!INCLUDEappliesto-ss-asdb-asdw-pdw-md]

To fetch and update rowsets

  1. Optionally, call SQLSetStmtAttr with SQL_ROW_ARRAY_SIZE to change the number of rows (R) in the rowset.

  2. Call SQLFetch or SQLFetchScroll to get a rowset.

  3. If bound columns are used, use the data values and data lengths now available in the bound column buffers for the rowset.

    If unbound columns are used, for each row call SQLSetPos with SQL_POSITION to set the cursor position; then, for each unbound column:

    • Call SQLGetData one or more times to get the data for unbound columns after the last bound column of the rowset. Calls to SQLGetData should be in order of increasing column number.

    • Call SQLGetData multiple times to get data from a text or image column.

  4. Set up any data-at-execution text or image columns.

  5. Call SQLSetPos or SQLBulkOperations to set the cursor position, refresh, update, delete, or add row(s) within the rowset.

    If data-at-execution text or image columns are used for an update or add operation, handle them.

  6. Optionally, execute a positioned UPDATE or DELETE statement, specifying the cursor name (available from SQLGetCursorName) and using a different statement handle on the same connection.

See Also

Using Cursors How-to Topics (ODBC)