Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

SAP Sybase SQL Anywhere 16.0 » SQL Anywhere Server - Programming » .NET application programming » SQL Anywhere .NET Data Provider

 

Data access and manipulation

With the SQL Anywhere .NET Data Provider, there are two ways you can access data:

  • SACommand object   The SACommand object is the recommended way of accessing and manipulating data in .NET.

    The SACommand object allows you to execute SQL statements that retrieve or modify data directly from the database. Using the SACommand object, you can issue SQL statements and call stored procedures directly against the database.

    Within an SACommand object, an SADataReader is used to return read-only result sets from a query or stored procedure. The SADataReader returns only one row at a time, but this does not degrade performance because the SQL Anywhere client-side libraries use prefetch buffering to prefetch several rows at a time.

    Using the SACommand object allows you to group your changes into transactions rather than operating in autocommit mode. When you use the SATransaction object, locks are placed on the rows so that other users cannot modify them.

    For more information, see SACommand class [SQL Anywhere .NET] and SADataReader class [SQL Anywhere .NET].

  • SADataAdapter object   The SADataAdapter object retrieves the entire result set into a DataSet. A DataSet is a disconnected store for data that is retrieved from a database. You can then edit the data in the DataSet and when you are finished, the SADataAdapter object updates the database with the changes made to the DataSet. When you use the SADataAdapter, there is no way to prevent other users from modifying the rows in your DataSet. You need to include logic within your application to resolve any conflicts that may occur.

    For more information about conflicts, see Resolving conflicts when using the SADataAdapter.

    For more information about the SADataAdapter object, see SADataAdapter class [SQL Anywhere .NET].

There is no performance impact from using the SADataReader within an SACommand object to fetch rows from the database rather than the SADataAdapter object.


SACommand: Fetch data using ExecuteReader and ExecuteScalar
SACommand: Fetch result set schema using GetSchemaTable
SACommand: Insert, Delete, and Update rows using ExecuteNonQuery
SACommand: Retrieve primary key values for newly inserted rows
SADataAdapter: Overview
SADataAdapter: Fetch data into a DataTable using Fill
SADataAdapter: Format a DataTable using FillSchema
SADataAdapter: Insert rows using Update
SADataAdapter: Delete rows using Update
SADataAdapter: Update rows using Update
SADataAdapter: Retrieve primary key values for newly inserted rows
BLOBs
Time values