gremlify
  • Getting Started
  • Workspaces
  • Use a Template
  • Define a Schema
  • Build Your own Graph
  • Compose Queries
  • Run Queries
  • Organization
  • FAQ
  • Terms of Service
  • Privacy Policy
Powered by GitBook
On this page
  • Run
  • Query History
  • JSON view
  • Table view
  • Error view

Was this helpful?

Run Queries

PreviousCompose QueriesNextOrganization

Last updated 5 years ago

Was this helpful?

We already built a graph and composed a query. We are now ready to test it out agains the database!

Now the Gremlify Results panel should look like that:

Meaning we did not execute any query yet.

Run

Assuming we have a Simple Graph with only one Vertex:

And a query:

g.V();

Let's run it against the graph, by simply clicking on "Run" in the main toolbar:

Now the above Query result panel shows:

Query History

Every query you run in your session will be saved into the query history, which is available in the platform sidebar:

Clicking on an item will load this query into your Workspace query editor.

Query History is not saved with the Workspace, or anywhere.

JSON view

Table view

Sometimes it is more appealing to see the results in a tabular view. To switch to Table view, simple click on the Table icon:

Let's take a look on an actual Table view, produced by the following query:

g.E();

Ordering columns is done by clicking on the column header

As for the nature of tables, not every query result will have a tabular view available. In this case Gremlify will ask you to switch to JSON mode.

As stated above, some query results will not have a proper tabular representation and therefor will display the following query and results:

g.E().project('test').
    by(valueMap(true))

Error view

Everyone makes mistakes, but no worries, in case you have an error in your query, Gremlify will give you the most detailed error message as possible.

Some errors might occur due to Gremlin syntax errors:

g.Vx();

In this case, Gremlify will switch to error view:

In some other cases, your query syntax is just fine, but the actual run against the database encountered a Runtime Exception:

g.V().inV();

You will now see:

The results JSON view displays the data in a form.

JSON
Query results - JSON view
Query History