RAD Studio |  |

Executing Commands That Do Not Return Records
See Also
Collapse All

You can use a dbExpress dataset even if the query or stored procedure it represents does not return any records. Such commands include statements that use Data Definition Language (DDL) or Data Manipulation Language (DML) statements other than SELECT statements (For example, INSERT, DELETE, UPDATE, CREATE INDEX, and ALTER TABLE commands do not return any records). The language used in commands is server-specific, but usually compliant with the SQL-92 standard for the SQL language.

The SQL command you execute must be acceptable to the server you are using. Unidirectional datasets neither evaluate the SQL nor execute it. They merely pass the command to the server for execution.

Note: If the command does not return any records, you do not need to use a unidirectional dataset at all, because there is no need for the dataset methods that provide access to a set of records. The SQL connection component that connects to the database server can be used directly to execute a command on the server. See Sending commands to the server for details.
The following topics discuss how to create and execute a command that does not return any records:

- Specifying the command to execute
- Executing the command

In addition, the topic,Creating and modifying server metadata, discusses some of the SQL commands that do not return datasets:
See Also

Connecting to the Database Server

Types of dbExpress Datasets

Specifying What Data to Display

Creating Master/detail Relationships

Accessing Schema Information

Fetching the Data

Debugging dbExpress Applications

Copyright(C) 2009 Embarcadero Technologies, Inc. All Rights Reserved.
What do you think about this topic? Send feedback!