Every xDMS I used offers alias declaration as FIELD_THAT_EXISTS as ALIAS_NAME And it is grammatically correct: meaning "we will call that field as ‘‘alias’’ " It is not “Player_one as Denis”, but “Denis as Player_one”. Is there any eye-opening explanation of why it is reversed in DQL, or it will…

It follows the alias syntax from GraphQL because DQL roots were around being a GraphQL like database query language but for obvious reasons the GraphQL syntaxes alone was not enough and IMHO, the DQL syntax still isn’t either.

Is aliases declaration reversed on purpose?

Users Dgraph

mrXCray (Denis) July 17, 2022, 12:38pm 3

Sounds like there is no plans to change that
But explanation is eye-opening, thank you!

Topic		Replies	Views
Do aliases work in the latest Dgraph 1.2.0 update? Dgraph	1	307	January 29, 2020
`@reverse` with custom field on inverse relation Dgraph kind:question , dgraph , dql	4	600	October 28, 2020
Saturday question Dgraph	1	544	February 26, 2019
@hasInverse GraphQL to DQL mapping Dgraph kind:question	2	1798	August 23, 2024
Introspection can't use Aliases GraphQL	8	871	September 17, 2021

Is aliases declaration reversed on purpose?

Related topics