Katarina Supe
Katarina Supe
No problem, just wanted to make sure it's all properly linked 😄
@gitbuda I tried this out, and the behavior is how @ljhhuxiaoba described it. Not sure if this is expected behavior on Memgraph side.
Hi @weelink, thank you for reporting this issue. The fix should be available under Memgraph 2.16. I hope that works well for you and if you have any other issues,...
+1 from the community with the additional comment that in-memory analytical storage mode wouldn't be feasible. [Source](https://discord.com/channels/842007348272169002/890968055339958292/1227881931144826890).
Just a heads up here - TTL is an Enterprise feature. If you'd like to try it out, you can [request Enterprise trial](https://memgraph.com/enterprise-trial). If you need any help or would...
Hi @e1ijah1, this issue is currently not a high priority because it is not an issue that blocks or slows down the usage of Memgraph. It is a 'nice to...
@gitbuda, this seems to be an unexpected behavior. I tried different kinds of construct, too, and tried using string instead of boolean, but encountered the same error as @lomnido. ```...
If I try with `WITH`: `MATCH (n2:L2),()
We had an internal discussion about this issue. It wasn't fixed in 2.13 as I mentioned above. The issue I referred to was closed because, currently, there is no good...
Reported by another community member: > BFS should indeed return ALL the paths of specified length according to Memgraph's own specs.