TQL name: Difference between revisions
Jump to navigation
Jump to search
m (→Restrictions) |
mNo edit summary |
||
| Line 7: | Line 7: | ||
* 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 begin with a letter. Explicitly not a number. | |||
* Must be at least 1 and at most 100 characters long. | * 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: | ||
Revision as of 11:44, 5 March 2021
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 begin with a letter. Explicitly not a number.
- 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
- AND_
- FOO_ANDS
- WHERE_
- WHERE_FOO