Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Creating and managing graphs and views #314

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

boggle
Copy link
Contributor

@boggle boggle commented May 8, 2018

This is a proposal for creating and managing graphs and views in the catalog and inside the query.
It also covers views and parameterized views.

It is part of the redesign of Cypher for adding support for working with multiple graphs that targets Cypher 10.

View latest version of CIP from associated branch

@boggle boggle changed the title Creating and administrating graphs and views Creating and managing graphs and views May 8, 2018

=== Managing views in the catalog

Views in the catalog can be managed with `COPY`, `RENAME`, `DELETE QUERY` in the same way as graphs.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why the distinction that COPY and RENAME do not require the additional keyword of what is copied/renamed, but DELETE needs that?


Semantics:

1. `<composite statement>` must not be a correlated subqueries.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo: "a"

4. `RETURN GRAPH <view name>`


== Local declarations
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This whole section is not so clear to me.


1. `<composite statement>` must not be a correlated subqueries.

2. An error is raised, if a local declaration would shadow an already exisint local declaration.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo: "exisint"

[source, cypher]
----
QUERY _myView(args) {
WITH a, b
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is the difference between binding expectations and parameters?

<composite statement>
}
MATCH (x)-[r:KNOWS]->(y)
CALL PER since _myView(5 WITH x AS a, y AS b) YIELD ...
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very weird syntax IMHO.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants