2.1.1.31 F812, Basic flagging

  • Article
  • 2 minutes to read

V0031:

The [ISO/IEC9075-2:2011] specification states the following:

 Part 1, Subclause 8.5, "SQL flagger": With "level of flagging" specified to be Core SQL Flagging and "extent of checking" specified to be Syntax Only
  
 NOTE — This form of flagging identifies vendor extensions and other non-standard SQL by checking syntax only without requiring access to the catalog information.

The [ISO/IEC9075-1:2011] specification states the following:

 Subclause 8.5, "SQL flagger":
  
 An SQL Flagger is an implementation-provided facility that is able to identify SQL language extensions, or other SQL processing alternatives, that may be provided by a conforming SQL-implementation...
  
 An SQL Flagger provides one or more of the following "level of flagging" options:
 — Core SQL Flagging
 — Part SQL Flagging
  
 An SQL Flagger that provides one of these options shall be able to identify SQL language constructs that violate the indicated subset of SQL language. The subset of SQL language used by "Core SQL Flagging" is Core SQL....
  
 An SQL Flagger provides one or more of the following "extent of checking" options:
 — Syntax Only
 — Catalog Lookup
  
 Under the Syntax Only option, the SQL Flagger analyzes only the SQL language that is presented; it checks for violations of any Syntax Rules that can be determined without access to the Information Schema. It does not necessarily detect violations that depend on the data type of syntactic elements, even if such violations are in principle deducible from the syntax alone.

The [ISO/IEC9075-1:2008] specification excerpt differs from the [ISO/IEC9075-1:2011] specification as follows:

 An SQL Flagger provides one or more of the following "level of flagging" options:
 — Core SQL Flagging
 — Part SQL Flagging
 — Package SQL Flagging

Microsoft SQL Server 2008 R2 and Microsoft SQL Server 2012 vary as follows:

Transact-SQL partially supports this feature. Transact-SQL supports the SET FIPS_FLAGGER statement, which specifies that a Transact-SQL program checks for compliance with the FIPS 127-2 standard [FIPS127], which is based on the ISO SQL-92 standard [SQL92].