Add examples to the glossary descriptions #275
Conversation
|
This PR includes documentation updates Updated pages: |
|
Hey @Lojjs, I've also created 3 cards folowing our discussions on Thursday. I wonder if we want to doble-check with one more person, for example, Lasse, if the parameters' descriptions make sense to him as well. |
renetapopova
force-pushed
the
dev-parameters
branch
from
a1d5526 to
80290c8
Compare
…ifictaions, and fix inconsistencies in variables and descriptions
renetapopova
force-pushed
the
dev-parameters
branch
from
80290c8 to
9ba8c61
Compare
Co-authored-by: Lasse Heemann <7661319+l-heemann@users.noreply.github.com>
Co-authored-by: Lasse Heemann <7661319+l-heemann@users.noreply.github.com>
Co-authored-by: Lasse Heemann <7661319+l-heemann@users.noreply.github.com>
Co-authored-by: Lasse Heemann <7661319+l-heemann@users.noreply.github.com>
Co-authored-by: Lasse Heemann <7661319+l-heemann@users.noreply.github.com>
Co-authored-by: Lasse Heemann <7661319+l-heemann@users.noreply.github.com>
|
Thanks for the documentation updates. The preview documentation has now been torn down - reopening this PR will republish it. |
| //52N22 and 52N36 to change $field to $arg. Check 22N98 with Antonio. | ||
| [[fun]]$fun:: Function name, for example, `collect()`. | ||
| [[funClass]]$funClass:: User-defined function implementation class name, for example, `MyFunctionClass`. | ||
| [[graph]]$graph:: The name of a graph, for example, `myGraph`. |
There was a problem hiding this comment.
Out of curiosity, is this parameter for GDS-related features?
How do we (in the team-errors) define and distinguish graph and database?
We have these terms in the Neo4j Glossary. Are those definitions still true and valid?
There was a problem hiding this comment.
I believe graph here is unrelated to the graph in GDS, both referencing the scientific concept that Neo4j builds on https://en.wikipedia.org/wiki/Graph_theory.
@nadja-muller Do you have a more detailed explanation for the graph vs database question? I attempted an example with composite but that felt more confusing than helpful 😅
There was a problem hiding this comment.
It's a bit tricky. I think what we ended up on was:
- graph: logical object, data in the database container e.g. once you access the data, you try to access the graph (which is why it is used as a target of the USE clause)
- database: container/file of the graph (which is why it is used in the administration commands)
I'm not sure how to write this out formally, however. There are very close to each other. Does that help you?
There was a problem hiding this comment.
There was a problem hiding this comment.
@l-heemann, are you happy with this PR? May I merge it?
Co-authored-by: Lasse Heemann <7661319+l-heemann@users.noreply.github.com>
7 participants
No description provided.