This is an old revision of the document!
The products table is a parent table with a primary key that has a column cardinality of 10,000. This means it has 10,000 unique product codes.
The orders table is a child table with 10,000,000 rows. This means it has a table cardinality of 10,000,000.
SELECT O.PRODUCT_CODE, O.CUSTOMER_NO, O.STATUS FROM PRODUCTS P, ORDERS O WHERE P.PRODUCT_CODE=O.PRODUCT_CODE AND P.PRODUCT_NAME = 'PRINTER'
For example: Customers is the parent table and activity and orders are the child tables. Selecting from both the activity and orders table for a particular customer will produce a cartesian product. Meaning, every row in the activity table will be qualified with every row in the orders table. If activity has 10 rows for one customer and orders has 10 rows for the same customer, the cartesian product is 100 rows. table1 (t1) contains 2 rows (r1, r2) and table2 (t2) contains 3 rows (r1, r2, r3). The cartesian product or these tables contains 6 rows: t1r1-t2r1, t1r1-t2r1, t1r1-t2r3, t1r2-t2r1, t1r2-t2r2, t1r2-t2r3.
A list containing data elements where each data element has a pointer to the previous and successive data element. See also: linked list
A child table or detail data set.
A column or field in a child table that identifies rows in the table containing the same values; also known as a repeating key. See also: key
There is a one-to-many relationship between the parent table and the child table.
composite keys
In OmniAccess, cursors are established by a call to oaopencursor, and closed by a call to oaclosecursor. They are referenced through the cursor option as an integer value in calls to OmniAccess routines. In ODBC and JDBC, cursors are created with statement objects.