Reading Standard Compliance Tables
For each language element and statement, the standards compliance is noted in a table, e.g. for GRANT ACCESS PRIVILEGE:
X/Open-95 SQL-92 Yes The use of the keyword PRIVILEGES in conjunction with the keyword ALL is not mandatory in Mimer SQL.
The table lists for each relevant standard:
- The name of the standard
- An indication of how Mimer SQL complies with the standard, i.e. MIMER EXTENSION means the entire SQL statement or concept is something specific to Mimer SQL and is not included in any standard.
EXTENDED means that the SQL statement or concept is included in the named standard(s) and Mimer SQL implements extra features over and above those described in the standard(s); YES indicates that the SQL statement or concept is implemented in Mimer SQL in accordance with named standard(s)
- Comments that clarify, where required, details of Mimer SQL compliance with the standard. Typically used to describe extended Mimer SQL features or any applicable differences between the standard and the Mimer SQL implementation.
In writing standard-compliant SQL application programs, make sure that only features included in the standard are used where Mimer SQL offers extended features, and that features which are labeled MIMER EXTENSION are avoided as far as possible.
When Mimer SQL extended features must be used, try to isolate the code containing these features and use comments to identify the non-standard statements. In this way, porting of application code to other standard environments is simplified.
Upright Database Technology AB
Voice: +46 18 780 92 00
Fax: +46 18 780 92 40