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

Clarify that CREATE OR REPLACE DB deletes indexes and constraints as well (#2154) #2161

Merged
merged 1 commit into from
Mar 4, 2025

Conversation

NataliaIvakina
Copy link
Collaborator

You may need to preserve the database structure (indexes and constraints) when you move the database from test env to production. In this case, it's important to know that the CREATE OR REPLACE DB cmd removes not only data but also indexes and constraints. If you want to keep them, you have to do it before executing the command.

…well (neo4j#2154)

You may need to preserve the database structure (indexes and
constraints) when you move the database from test env to production. In
this case, it's important to know that the `CREATE OR REPLACE DB` cmd
removes not only data but also indexes and constraints. If you want to
keep them, you have to do it before executing the command.
@neo-technology-commit-status-publisher
Copy link
Collaborator

Thanks for the documentation updates.

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

@NataliaIvakina NataliaIvakina merged commit ab73af7 into neo4j:5.x Mar 4, 2025
4 checks passed
@NataliaIvakina NataliaIvakina deleted the 5.x-initialize-db branch March 4, 2025 09:02
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.

2 participants