Skip to content

SAP HANA Keyword Compatibility Reference

Generated for GSP Java version 4.1.0.8 on 2026-03-15

This page was generated using hybrid static extraction from parser source files combined with runtime validation against the actual GSP parser. Re-run the extraction script after parser updates to keep this page current.

Keyword-as-Column-Name Support

As of version 4.1.0.8, the GSP SAP HANA parser includes a lexer lookahead mechanism that allows 31 vendor-unreserved keywords to be used as unquoted column names in SELECT statements.

The lookahead pre-scans the token list before parsing and converts context-specific keywords to identifiers when they appear in column-name position:

  • After: SELECT, ,, DISTINCT, or ALL
  • Before: FROM, AS, WHERE, GROUP, ORDER, HAVING, LIMIT, UNION, INTERSECT, EXCEPT, INTO, ,, ), or ;
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
-- Works: keyword as column name
SELECT array FROM t;

-- Works: keyword as column name
SELECT auto_corr FROM t;

-- Works: keyword as column name
SELECT avg FROM t;

-- Original keyword syntax also still works

Full Classification Overview

Out of 655 keywords recognized by the GSP SAP HANA parser:

Classification Count Description
Allowed 612 Can be used as an unquoted column name in both canonical contexts
Context-specific 33 Fails as SELECT keyword FROM t but works as SELECT t.keyword FROM t
Blocked 10 Cannot be used as an unquoted column name in either context

Context-Specific Keywords (33)

These keywords fail when used as bare column names (SELECT keyword FROM t) but succeed when table-qualified (SELECT t.keyword FROM t).

Keyword Reason
ALL SELECT qualifier
ARRAY Type keyword
AUTO_CORR Grammar keyword
AVG Grammar keyword
CASE Expression keyword
CORR Grammar keyword
CORR_SPEARMAN Grammar keyword
COUNT Grammar keyword
CROSS_CORR Grammar keyword
DFT Grammar keyword
DISTINCT SELECT qualifier
FIRST_VALUE Grammar keyword
FULL JOIN keyword
INTERVAL Type keyword
LAST_VALUE Grammar keyword
LEAD Grammar keyword
LOCATE_REGEXPR Grammar keyword
MAX Grammar keyword
MEDIAN Grammar keyword
MIN Grammar keyword
NTH_VALUE Grammar keyword
OCCURRENCES_REGEXPR Grammar keyword
PERCENTILE_CONT Grammar keyword
PERCENTILE_DISC Grammar keyword
RANK Grammar keyword
REPLACE_REGEXPR Grammar keyword
STRING_AGG Grammar keyword
SUBSTRING_REGEXPR Grammar keyword
SUBSTR_REGEXPR Grammar keyword
SUM Grammar keyword
TOP SELECT qualifier
UNION Clause keyword
VAR Grammar keyword

Blocked Keywords (10)

These keywords cannot be used as unquoted column names in either context.

Keyword Workaround
CALL SELECT "call" FROM t
DELETE SELECT "delete" FROM t
EXPORT SELECT "export" FROM t
FROM SELECT "from" FROM t
IMPORT SELECT "import" FROM t
INSERT SELECT "insert" FROM t
ROLLBACK SELECT "rollback" FROM t
SELECT SELECT "select" FROM t
UPDATE SELECT "update" FROM t
UPSERT SELECT "upsert" FROM t

Workaround: Double-Quoted Identifiers

For any keyword that fails as an unquoted column name, you can use double-quoted identifiers:

1
2
3
4
5
-- Blocked or context-specific keyword as column name
SELECT "call" FROM t;

-- Or use table qualification for context-specific keywords
SELECT t.all FROM t;

Scope and Limitations

  • Tested contexts: SELECT keyword FROM t and SELECT t.keyword FROM t. Other contexts (DDL column definitions, INSERT column lists, aliases) may behave differently.
  • Version-specific: This report reflects GSP Java version 4.1.0.8.
  • Case sensitivity: Keywords are case-insensitive. select, SELECT, and Select are all treated the same.

How to Report Discrepancies

If you encounter a keyword that behaves differently from what this page describes, please report it through your support channel. Include:

  1. The exact SQL statement
  2. The GSP parser version
  3. Whether the same SQL works in SAP HANA

Methodology

  1. Static extraction: A Python script parses the lexer (.cod) and grammar (.y) source files to identify all 655 keywords and their grammar classifications.
  2. Runtime validation: A Java test harness validates every classification against actual TGSqlParser runtime behavior.
  3. JSON dataset: The authoritative data is stored in docs/generated/hana_keyword_compatibility.json.