Table Procedure Examples, Design, and Use

Table Procedure Examples, Design, and Use

This appendix provides information you can use to:

• Design table procedures and select unique key fields
• Understand how Quick Bridge determines what access strategies to employ to retrieve and update records.
• Study examples of table procedure specifications for a variety of record/set relationships
• Specify a DBName for a table procedure
• Reference authorities required to modify records in the dictionary
• See samples of the output files created by the table procedure you defined in the chapter "Creating Table Procedure Specifications."
• How to assign a data type of date to SQL columns
• Reference messages you might receive when you generate your table procedure

To get the most out of Quick Bridge, you should be familiar with the data structure of the target database and understand how the generated table procedure can be used in your SQL access strategy. To review, a network-type database defines data by elements that are grouped together into record occurrences, which together form a record type. A set defines the relationship between record types. In a relational database, data is represented in columns; a group of columns form a row. Together, the columns and rows form a table. A foreign key defines the relationship between tables. Among other uses, table procedures give users of nonSQL-defined schemas a way to map SQL DML statements to navigational DML statements.

This section contains the following topics:

Identify Record Relationships

Choose Unique Key Fields

Access Methods for Selected Records

Samples from the Commonweather Database

Sample SQL Statements

Specify a DBName for Table Procedures

Authority Required to Generate Table Procedures

Sample Files

SQL Data Type Mapping and Defining SQL Columns as Date Columns

Messages Returned From a Generated Table Procedure