Oracle9i SQL Reference Release 1 (9.0.1) Part Number A90125-01 |
|
This appendix discusses Oracle's conformance with the SQL:1999 standards. The mandatory portion of SQL:1999 is known as Core SQL:1999 and is found in SQL:1999 Part 2 (Foundation) and Part 5 (Bindings). The Foundation features are analyzed in Annex F of Part 2 in the table "SQL/Foundation feature taxonomy and definition for Core SQL". The Bindings features are analyzed in Annex F of Part 5 in the table "SQL/Bindings feature taxonomy and definition for Core SQL".
This appendix declares Oracle's conformance to the SQL standards established by the American National Standards Institute (ANSI) and the International Standards Organization (ISO). (The ANSI and ISO SQL standards are identical.) It contains the following sections:
The following documents of the American National Standards Institute (ANSI) relate to SQL:
You can obtain a copy of ANSI standards from this address:
or from their web site:
http://webstore.ansi.org/ansidocstore/default.asp
A subset of ANSI standards, including the SQL standard, are X3 or NCITS standards. You can obtain these from the National Committee for Information Technology Standards (NCITS) at:
http://www.cssinfo.com/ncitsgate.html
The following documents of the International Organization for Standardization (ISO) relate to SQL:
You can obtain a copy of ISO standards from this address:
or from their web store:
http://www.iso.ch/cate/cat.html
The ANSI and ISO SQL standards require conformance claims to state the type of conformance and the implemented facilities. The Oracle9i server, Oracle Precompilers for C/C++ release 8.1, Oracle Precompiler for Cobol release 8.1, and SQL*Module for ADA release 8.0.4 provide full or partial conformance with the ANSI and ISO standards as described in the tables that follow.
The Core SQL:1999 features that Oracle fully supports are listed in Table B-1:
The Core SQL:1999 features that Oracle partially supports are listed in Table B-2:
Oracle has equivalent functionality for the features listed in Table B-3:
The Core SQL:1999 features that Oracle does not support are listed in Table B-4:
Feature ID | Feature |
---|---|
F501 |
Features and conformance views |
S011 |
Distinct data types |
Oracle complied fully with last Federal Information Processing Standard (FIPS), which was FIPS PUB 127-2. That standard is no longer published. However, for users whose applications depend on information about the sizes of some database constructs that were defined in FIPS 127-2, we list the details of our compliance in Table B-5.
Oracle supports numerous features that extend beyond standard SQL. In your Oracle applications, you can use these extensions just as you can use Core SQL:1999.
If you are concerned with the portability of your applications to other implementations of SQL, use Oracle's FIPS Flagger to help identify the use of Oracle extensions to Entry SQL92 in your embedded SQL programs. The FIPS Flagger is part of the Oracle precompilers and the SQL*Module compiler.
See Also:
Pro*COBOL Precompiler Programmer's Guide and Pro*C/C++ Precompiler Programmer's Guide for information on how to use the FIPS Flagger. |
Oracle supports most national, international, and vendor-specific encoded character set standards. A complete list of character sets supported by Oracle Appears in Appendix A, "Locale Data", in Oracle9i Globalization Support Guide.
Unicode is a universal encoded character set that lets you store information from any language using a single character set. Unicode is required by modern standards such as XML, Java, JavaScript, LDAP, CORBA 3.0. Unicode is compliant with ISO/IEC standard 10646. You can obtain a copy of ISO/IEC standard 10646 from this address:
Oracle9i complies fully with Unicode 3.0, the third and most recent version of the Unicode standard. For up-to-date information on this standard, visit the web site of the Unicode Consortium:
http://www.unicode.org
Oracle uses UTF-8 (8-bit) encoding by way of three database character sets, two for ASCII-based platforms (UTF8 and AL32UTF8) and one for EBCDIC platforms (UTFE). If you prefer to implement Unicode support incrementally, you can store Unicode data in either the UTF-16 or UTF-8 encoding form, in the national character set, for the SQL NCHAR
datatypes (NCHAR
, NVARCHAR2
, and NCLOB
).
|
Copyright © 1996-2001, Oracle Corporation. All Rights Reserved. |
|