TQL name: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
|||
| (3 intermediate revisions by the same user not shown) | |||
| 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. | ||
* May not | * Must begin with a letter. Explicitly not a number or underscore. | ||
* Must be at least 1 and at most 100 characters long. | |||
* May not start with any of the following XML, AND_, WHERE_ | |||
* May not end with an underscore. | |||
* The following examples are not allowed: | |||
** AND | |||
** _AND | ** _AND | ||
** AND_ | ** AND_ | ||
Latest revision as of 15:00, 22 October 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 or underscore.
- Must be at least 1 and at most 100 characters long.
- May not start with any of the following XML, AND_, WHERE_
- May not end with an underscore.
- The following examples are not allowed:
- AND
- _AND
- AND_
- FOO_ANDS
- WHERE_
- WHERE_FOO