Home | Previous Page | Next Page   Developing an Access Method > Testing the Access Method >

Inserting, Querying, and Updating Data

If you want to test fragmented tables, use the SQL syntax in Supporting Fragmentation. If you want to support user-configured options, use the SQL syntax in Providing Configuration Keywords.

You can provide support in the access method for CREATE TABLE statement keywords that affect transaction processing. For example, if a CREATE TABLE statement specifies the WITH ROWIDS keyword, the access method must add a column of visible row identifiers to the table and allow queries on row identifiers. If a CREATE TABLE statement specifies the LOCK MODE clause, the access method must impose and manage locks during data retrieval and update. To determine the state of a table during transaction processing, the access method calls VTI functions to determine the lock mode, data-entry constraints, referential constraints, and other state information.

A user sets the isolation level with commands such as SET ISOLATION and SET TRANSACTION or with configuration settings in the ONCONFIG file. It is recommended that you document the isolation levels that the access method supports, as mi_scan_isolevel() describes. For information about setting isolation levels, refer to the IBM Informix: Guide to SQL Syntax and the IBM Informix: Guide to SQL Tutorial.

A database server administrator can use the ONCONFIG file to set defaults for such things as isolation level, locking, logging, and sbspace name. For information about defaults that you can set for the test-environment ONCONFIG file, refer to the IBM Informix: Administrator's Guide.

For information about SQL statements and keywords that your access method can support, refer to the IBM Informix: Guide to SQL Syntax. For information about the VTI functions that determine which statements and keywords the user specifies, refer to Descriptor Function Reference.

Home | [ Top of Page | Previous Page | Next Page | Contents | Index ]