Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make query language more English-like #70

Closed
neomatrix369 opened this issue Jun 26, 2019 · 1 comment
Closed

Make query language more English-like #70

neomatrix369 opened this issue Jun 26, 2019 · 1 comment

Comments

@neomatrix369
Copy link

neomatrix369 commented Jun 26, 2019

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).

@flyingsilverfin
Copy link
Member

We're currently happy with the way TypeQL is structured and aren't making dramatic english-like simplifications to it in the next few years

@haikalpribadi haikalpribadi reopened this Jan 11, 2023
@haikalpribadi haikalpribadi closed this as not planned Won't fix, can't repro, duplicate, stale Jan 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants