profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/hoijnet/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

hoijnet/nrpe_exporter 0

Prometheus NRPE exporter

hoijnet/remarkable-touchgestures 0

touch gestures for reMarkable

issue commentterminusdb/terminusdb

Path regular expression is inconsistent to expectations for repeated "any predicate"

Looking forward to 5.0 in anticipation! Thanks for confirming the bug.

hoijnet

comment created time in a month

issue commentterminusdb/terminusdb

Path traversal documentation incorrectly formatted

Thanks for the update! It looks beautiful, helpful and much clearer! 🙏

hoijnet

comment created time in 3 months

issue openedterminusdb/terminusdb

Path regular expression is inconsistent to expectations for repeated "any predicate"

Describe the bug A path regular expression "()+" or "(){1,2} does not identify/traverse more than one level from source to target which would be expected considering that "(property_name_level_1|property_name_level_2)+" does traverse more than one level.

To Reproduce Steps to reproduce the behavior:

  1. Go to TerminusDB Console Query tab
  2. Enter any of the following:
    • Traverses two levels: WOQL.path("v:source", "(propertyname_firstlevel|propertyname_secondlevel){1,2}", "v:target", "v:traversed")
    • Does not work, expecting same traversals or more than above: WOQL.path("v:source", "(*){1,2}", "v:target", "v:traversed")
    • Traverses two levels: WOQL.path("v:source", "(propertyname_firstlevel|propertyname_secondlevel)+", "v:target", "v:traversed")
    • Does not work, expecting same traversals or more than above: WOQL.path("v:source", "(*)+", "v:target", "v:traversed")
  3. Click Run Query

Expected behavior For the ones that work I got the correct result, traversal from source-->intermediary-->target and the path in v:traversed.

For the ones that does not work, when using "any predicate, *", only one level is traversed: source-->intermediary, and only the path for the source-->intermediary traversal is present in the result.

Screenshots N/A

Info (please complete the following information):

image

Additional context N/A, small database, minimal test does not yield expected behaviour

created time in 3 months

issue openedterminusdb/terminusdb

Path traversal documentation incorrectly formatted

Describe the typo/ misinformation On the documentation about the primitives, the information for path regular expression for path traversal, in the patterns part, are missing the characters for some fields ("alternatives" and "any predicate")

Expected changes

I was expecting/presuming the following and it seems to work as per expectations:

  • pipe should be representing the alternatives
  • star should be representing the any predicate option

Looks like the characters fell off, might be a good idea to write out which character it is.

Screenshots image

Additional context Will add separate issue for path traversal with star.

created time in 3 months