Was this page helpful?
Caution
You're viewing documentation for an unstable version of ScyllaDB Open Source. Switch to the latest stable version.
CQL distinguishes between reserved and non-reserved keywords. Reserved keywords cannot be used as an identifier. They are truly reserved for the language (but one can enclose a reserved keyword by double-quotes to use it as an identifier). Non-reserved keywords, however, only have a specific meaning in a certain context but can be used as identifiers otherwise. The only raison d’être of these non-reserved keywords is convenience: some keyword are non-reserved when it was always easy for the parser to decide whether they were used as keywords or not.
Keyword |
Reserved? |
|---|---|
|
yes |
|
no |
|
no |
|
yes |
|
yes |
|
yes |
|
yes |
|
no |
|
yes |
|
no |
|
yes |
|
yes |
|
yes |
|
no |
|
no |
|
no |
|
yes |
|
no |
|
no |
|
yes |
|
no |
|
no |
|
no |
|
no |
|
yes |
|
no |
|
no |
|
no |
|
yes |
|
yes |
|
yes |
|
no |
|
no |
|
yes |
|
yes |
|
yes |
|
no |
|
no |
|
no |
|
no |
|
yes |
|
no |
|
yes |
|
no |
|
no |
|
yes |
|
yes |
|
yes |
|
yes |
|
no |
|
yes |
|
no |
|
no |
|
yes |
|
no |
|
yes |
|
no |
|
no |
|
no |
|
yes |
|
no |
|
no |
|
yes |
|
no |
|
no |
|
no |
|
yes |
|
yes |
|
no |
|
yes |
|
no |
|
yes |
|
yes |
|
yes |
|
yes |
|
no |
|
yes |
|
yes |
|
no |
|
no |
|
no |
|
yes |
|
yes |
|
yes |
|
no |
|
yes |
|
no |
|
no |
|
yes |
|
yes |
|
yes |
|
no |
|
no |
|
no |
|
no |
|
no |
|
no |
|
yes |
|
no |
|
no |
|
no |
|
no |
|
no |
|
yes |
|
yes |
|
no |
|
yes |
|
no |
|
no |
|
no |
|
yes |
|
yes |
|
yes |
|
no |
|
no |
|
yes |
|
no |
|
no |
|
no |
|
no |
|
yes |
|
yes |
|
no |
The following type names are not currently used by CQL but are reserved for potential future use. User-defined types may not use reserved type names as their name.
type |
|---|
|
|
|
|
|
|
© 2016, The Apache Software Foundation.
Was this page helpful?