You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Graql is still a bit terse for some instances, especially when the rule definitions start becoming more involved. SQL is quite English-like but can become verbose, Graql expresses a lot of the same definitions in shorted constructs but maybe some improvements can be done to meet half-way.
Current Workaround
Learn the constructs and get acquainted with the language.
Proposed Solution
Constructs can be arranged in more like a sentence format: subject-verb-object, subject-verb, a number of improvements can be achieved by just rearranging the constructs or maybe renaming them.
From a technical perspective, it could mean extending or enhancing the parser to understand different formats or maybe extending the vocabulary so it knows more words or similar words. End-users could use the existing format or the new proposed format when writing Graql.
Additional Information
I'm happy to suggest literal improvements if you can point me to a resource which lists the lexicon/constructs of the Graql language and some examples of usages.
By making Graql more English-like we could definitely help this idea: vaticle/typedb-studio#153 (I have raised this to help the current idea from the other perspective).
The text was updated successfully, but these errors were encountered:
Problem to Solve
Graql is still a bit terse for some instances, especially when the rule definitions start becoming more involved. SQL is quite English-like but can become verbose, Graql expresses a lot of the same definitions in shorted constructs but maybe some improvements can be done to meet half-way.
Current Workaround
Learn the constructs and get acquainted with the language.
Proposed Solution
Constructs can be arranged in more like a sentence format: subject-verb-object, subject-verb, a number of improvements can be achieved by just rearranging the constructs or maybe renaming them.
From a technical perspective, it could mean extending or enhancing the parser to understand different formats or maybe extending the vocabulary so it knows more words or similar words. End-users could use the existing format or the new proposed format when writing Graql.
Additional Information
I'm happy to suggest literal improvements if you can point me to a resource which lists the lexicon/constructs of the Graql language and some examples of usages.
By making Graql more English-like we could definitely help this idea: vaticle/typedb-studio#153 (I have raised this to help the current idea from the other perspective).
The text was updated successfully, but these errors were encountered: