•
|
If you specify CASCADE, Pervasive PSQL uses the delete cascade rule. When a user deletes a row in the parent table, the database engine deletes the corresponding rows in the dependent table.
|
•
|
If you specify RESTRICT, Pervasive PSQL enforces the delete restrict rule. A user cannot delete a row in the parent table if a foreign key value refers to it.
|
•
|
•
|
•
|
Relative paths containing a period (‘.’ - current directory), double-period (‘..’ - parent directory), slash ‘\’, or any combination of the three are allowed. The path must contain a file name representing the SQL table name (path_name cannot end in a slash ‘\’ or a directory name). All file names, including those specified with relative paths, are relative to the first Data Path as defined in the Named Database configuration.
|
•
|
A CREATE INDEX statement uses the linked duplicates method up to the value specified for the number of pointers
|
•
|
Once the value specified for the number of pointers is reached, a CREATE INDEX statement uses the repeating duplicates method
|
•
|
If the value specified for the number of pointers has been reached and a linked-duplicate index is dropped, a CREATE INDEX statement uses the linked duplicates method for the next key
|
•
|
A CREATE INDEX statement cannot create a repeating- duplicate key if pointers are still reserved for linked- duplicate keys.
|