Skip to content

Conversation

@JPryce-Aklundh
Copy link
Collaborator

No description provided.

Copy link
Collaborator

@Hunterness Hunterness left a comment

Choose a reason for hiding this comment

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

I haven't looked to confirm if the existing links are correct/up-to-date.

Comment on lines 115 to 142
The table below outlines which Cypher version is assigned to databases in different upgrade or installation scenarios:

[cols="3", options="header"]
|===
| Scenario | `db.query.default_language` | Databases


| *Standard DBMS upgrade to Neo4j 2025.06+*
| Unset
| *Existing system database:* `CYPHER 5` +
*Existing user databases:* `CYPHER 5` +
*New user databases default:* `CYPHER 5`


| *Custom DBMS upgrade to Neo4j 2025.06+*
| Manually set to `CYPHER_25` by administrator
| *Existing system database:* `CYPHER 5` +
*Existing user databases:* `CYPHER 5` +
*New user databases default:* `CYPHER 25`


| *New installation of Neo4j 2025.06+*
| Set to `CYPHER_5`
| *New system database:* `CYPHER 5` +
*New user databases default:* `CYPHER 5`


|===
Copy link
Collaborator

Choose a reason for hiding this comment

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

I like this kind of table, if we don't want to keep it here maybe it should be added to the cypher-version-configuration page?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

@renetapopova added a similar one to the upgrade and migration guide, to which this PR links.

https://github.com/neo-technology/neo4j-upgrade-migration-guide/commit/d1c219d46513b1ce2341cb3427f167fccd9e620b

Copy link
Collaborator

Choose a reason for hiding this comment

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

Copy link
Collaborator

Choose a reason for hiding this comment

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

not sure I understand that ones current table though
image

the table here were more explicit in what the different scenarios were which was nice, so maybe we need to update that table somewhat.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Copy link
Collaborator

@Hunterness Hunterness left a comment

Choose a reason for hiding this comment

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

Looks good to me (but I still haven't confirmed that the links are up-to-date and don't plan to either :P)

@neo4j-docops-agent
Copy link
Collaborator

neo4j-docops-agent commented Jul 2, 2025

Thanks for the documentation updates.

The preview documentation has now been torn down - reopening this PR will republish it.

@rsill-neo4j rsill-neo4j merged commit 0e8aeab into neo4j:dev Jul 2, 2025
4 checks passed
rsill-neo4j added a commit that referenced this pull request Jul 2, 2025
… Manual and Upgrade and migration guide (#1327)

Co-authored-by: Richard Sill <[email protected]>
Co-authored-by: Therese Magnusson <[email protected]>
@rsill-neo4j rsill-neo4j added the cherry-picked This PR was merged in another version and the changes has been cherry picked in this PR. label Jul 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cherry-pick-to-cypher-25 cherry-picked This PR was merged in another version and the changes has been cherry picked in this PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants