TQL name: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
|||
| Line 6: | Line 6: | ||
The following restrictions apply: | The following restrictions apply: | ||
* Must be entirely capitalized, to avoid ambiguity. | * Must be entirely capitalized, to avoid ambiguity. | ||
* May only consist of letters, numbers, and underscores, to avoid issues with special characters | * May only consist of letters, numbers, and underscores, to avoid issues with special characters. | ||
* Must be at least 1 and at most 100 characters long. | |||
* 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: | * 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 | ||
Revision as of 06:37, 29 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.
- Must be at least 1 and at most 100 characters long.
- 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
- WHERE_
- WHERE_FOO