Skip to content

Commit a03ff95

Browse files
authored
Proofread
1 parent d5c5405 commit a03ff95

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

  • content/en/docs/refguide/modeling/domain-model/oql

content/en/docs/refguide/modeling/domain-model/oql/oql-v2.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -74,7 +74,7 @@ In OQL v2, the date arguments of functions [DATEPART](/refguide/oql-expression-s
7474

7575
### Columns Should Have a Name or an Alias
7676

77-
In OQL v1, when a column in the `SELECT` clause is a subquery, a function or a constant, it was possible for it not to have a name. For example:
77+
In OQL v1, when a column in the `SELECT` clause was a subquery, a function, or a constant, it was possible for it not to have a name. For example:
7878

7979
```sql
8080
SELECT
@@ -88,7 +88,7 @@ SELECT
8888
FROM Module.City
8989
```
9090

91-
The column names in this case would be `Name` and `null` names which would not be possible to refer to.
91+
The column names in this case would be `Name` and multiple columns named `null` which could not be referred to.
9292

9393
In OQL v2, such queries are no longer allowed. You must always provide an alias for expressions that do not result in a named column. The query above can be rewritten as follows:
9494

0 commit comments

Comments
 (0)