Skip to content

Union ordering no longer deprecated #219

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.

Sign up for GitHub

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

Closed
wants to merge 1 commit into from
Closed

Union ordering no longer deprecated #219

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
64 changes: 0 additions & 64 deletions modules/ROOT/pages/notifications/all-notifications.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1373,8 +1373,6 @@ a|
To continue using it, escape the identifier by adding backticks around the identifier `%s`.
- The character with the Unicode representation `%s` is deprecated for unescaped identifiers and will not be supported in the future.
To continue using it, escape the identifier by adding backticks around the identifier `%s`.
- All subqueries in a UNION [ALL] should have the same ordering for the return columns.
Using differently ordered return items in a UNION [ALL] clause is deprecated and will be removed in a future version.
- Databases and aliases with unescaped `.` are deprecated unless to indicate that they belong to a composite database.
Names containing `.` should be escaped. (`%s`)
|Category
Expand Down Expand Up @@ -1440,68 +1438,6 @@ CREATE DATABASE `foo.bar`
======
=====

.Using differently ordered return items in a `UNION` clause
Copy link
Collaborator

Choose a reason for hiding this comment

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

I would rather leave the example and add a note that from 5.26, using differently ordered return items in a UNION [ALL] clause is no longer deprecated.

Copy link
Collaborator

Choose a reason for hiding this comment

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

And the same for the above.

[.tabbed-example]
=====
[.include-with-neo4j-code]
======
Query::
+
[source,cypher]
----
RETURN 'val' as one, 'val' as two
UNION
RETURN 'val' as two, 'val' as one
----

Description of the returned code::
All subqueries in a UNION [ALL] should have the same ordering for the return columns.
Using differently ordered return items in a UNION [ALL] clause is deprecated and will be removed in a future version.

Suggestions for improvement::
Use the same order for the return columns in all subqueries combined by a `UNION` clause.

+
[source,cypher]
----
RETURN 'val' as one, 'val' as two
UNION
RETURN 'val' as one, 'val' as two
----

======
[.include-with-GQLSTATUS-code]
======
Query::
+
[source,cypher]
----
RETURN 'val' as one, 'val' as two
UNION
RETURN 'val' as two, 'val' as one
----

Returned GQLSTATUS code::
01N00

Returned status description::
warn: feature deprecated.
All subqueries in a UNION [ALL] should have the same ordering for the return columns.
Using differently ordered return items in a UNION [ALL] clause is deprecated and will be removed in a future version.

Suggestions for improvement::
Use the same order for the return columns in all subqueries combined by a `UNION` clause.

+
[source,cypher]
----
RETURN 'val' as one, 'val' as two
UNION
RETURN 'val' as one, 'val' as two
----
======
=====

.Using the Unicode \u0085 in an unescaped identifier
[.tabbed-example]
=====
Expand Down