Understanding BNF Notation
The MDX grammar rules for Essbase are presented using Backus-Naur Form (BNF) syntax notation throughout this documentation. Learning to read BNF will help you understand MDX syntax as you write statements or formulas to help you with Essbase analysis and data extraction.
This section briefly explains the meaning of symbolic notations used to describe grammar in this MDX documentation. The following table of conventions is not a complete description of BNF, but it can help you read the grammar rules presented in this document.
Table 4-2 BNF Notation Elements
Symbol | Description | Example |
---|---|---|
(A word in angle brackets.) |
The word presented in angle brackets is not meant to be literally used in a statement; its rules are further defined elsewhere. |
When reading the following syntax,
you know that |
(A word in angle brackets, followed directly by the symbol |
A definition, or BNF "production." The symbol The word referred to elsewhere as the placeholder |
The following syntax tells you that a tuple is defined as either one member in parenthesis, or two or more comma-separated members in parenthesis.
|
The pipe symbol or "OR" symbol. |
Precedes alternatives. The symbol | can be interpreted to mean "or."
|
The following syntax:
can be used to build any of the following literal statement parts:
|
(Text in all caps.) |
A query-grammar keyword, to be typed literally. |
When reading the following syntax,
you know that |
(Square brackets enclosing some word or item.) |
An optional element. |
In the following high-level query syntax,
everything, technically, is optional except for SELECT and FROM. Therefore, a query containing only the words
would in fact be valid; however, it would select one consolidated data value from its best estimate of a cube context, which might not be very useful. |
|
You can optionally append a comma-separated list of one or more <words> .
|
The following syntax
indicates that multiple, comma-separated axis specifications can optionally be supplied to the |