Schema query error: `SERVER ERROR: Not well formed WOQL JSON-LD` about terminusdb HOT 5 OPEN

Good find. The documentation mentions both triple and quad forms for this query. I think this is a bug indeed, or a client issue. For others seeing this later, check the documentation and use the quad style for now, but there are situations where there are many operations in the schema that really needs the from style!

Great catch @alexander-mart

from terminusdb.

This is a client bug, the generated JSON is:

{"@type":"Limit","limit":10,
  "query":{"@type":"And",
  "and":[{"@type":"From"},
              {"@type":"Triple",
               "subject":{"@type":"NodeValue","variable":"cls"},
               "predicate":{"@type":"NodeValue","node":"rdf:type"},
               "object":{"@type":"Value","node":"sys:Class"}}]}} 

Fluent syntax apparently does not work here, You can use the two argument call to from for now, and we can fix the documentation, but it would probably be nice if the fluent syntax worked to generate the right code here.

from terminusdb.

I'd like to just check my understanding so that I interpret the fluent style correctly, the fluent style continuation is from my understanding always an extra appended parameter to the argument list? I was thinking about this for the WOQL-TS client and what was the correct interpretation.

Should thus the below be what should be in the doc link?

let v = Vars("cls");
from("schema", WOQL.triple(v.cls, "rdf:type", "sys:Class"))

With triple being the last argument of from()

from terminusdb.

With triple being the last argument of from()

Yes, for example convention in Ramda (Functional Programming JS-library):

The primary distinguishing features of Ramda are:

• Ramda emphasizes a purer functional style. Immutability and side-effect free functions are at the heart of its design philosophy. This can help you get the job done with simple, elegant code.
• Ramda functions are automatically curried. This allows you to easily build up new functions from old ones simply by not supplying the final parameters.
• The parameters to Ramda functions are arranged to make it convenient for currying. The data to be operated on is generally supplied last.

The last two points together make it very easy to build functions as sequences of simpler functions, each of which transforms the data and passes it along to the next. Ramda is designed to support this style of coding.

Source: https://ramdajs.com/

How is currying work:

• https://medium.com/@hayavuk/data-pipelines-with-ramda-7fe886d88f5f

These queries should be identical (if from() function was curried):

let v = Vars("cls");
from("schema", WOQL.triple(v.cls, "rdf:type", "sys:Class"))

let v = Vars("cls");
from("schema").triple(v.cls, "rdf:type", "sys:Class")

from terminusdb.

Good find. The documentation mentions both triple and quad forms for this query. I think this is a bug indeed, or a client issue. For others seeing this later, check the documentation and use the quad style for now, but there are situations where there are many operations in the schema that really needs the from style!

Great catch @alexander-mart

For those who are looking for a solution 👍
For now, please use:

WOQL.quad("v:cls", "rdf:type", "sys:Class", "schema")

See: https://terminusdb.com/docs/javascript/#fromgraphrefquery

Instead of

from("schema", triple("v:cls", "rdf:type", "sys:Class"))

from terminusdb.