TQL name: Difference between revisions
Jump to navigation
Jump to search
(Created page with "{{stub}} A TQL name is a name which fits a specific set of restrictions, allowing it to be used unambiguously in TQL queries. Attributes and Globals must...") |
No edit summary |
||
| Line 5: | Line 5: | ||
==Restrictions== | ==Restrictions== | ||
The following restrictions apply: | The following restrictions apply: | ||
* Must be entirely capitalized | * Must be entirely capitalized, to avoid ambiguity. | ||
* May only consist of letters, numbers, and underscores | * May only consist of letters, numbers, and underscores, to avoid issues with special characters | ||
* May not | * May not contain the word AND or WHERE, with an underscore directly before or after it, to avoid ambiguity when determining discrete clauses. The following examples are not allowed: | ||
** | ** _AND | ||
** AND_ | |||
** FOO_ANDS | |||
** FOO_SAND | |||
** WHERE_ | |||
** WHERE_FOO | |||
Revision as of 14:22, 26 June 2020
This article is a stub.
A TQL name is a name which fits a specific set of restrictions, allowing it to be used unambiguously in TQL queries. Attributes and Globals must always have a name conforming to those restrictions, because queries use those names verbatim.
Restrictions
The following restrictions apply:
- Must be entirely capitalized, to avoid ambiguity.
- May only consist of letters, numbers, and underscores, to avoid issues with special characters
- May not contain the word AND or WHERE, with an underscore directly before or after it, to avoid ambiguity when determining discrete clauses. The following examples are not allowed:
- _AND
- AND_
- FOO_ANDS
- FOO_SAND
- WHERE_
- WHERE_FOO