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

Merged
merged 4 commits into from
Mar 3, 2025

Conversation

NataliaIvakina
Copy link
Collaborator

@NataliaIvakina NataliaIvakina commented Feb 26, 2025

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.

Copy link
Collaborator

@renetapopova renetapopova 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.

@NataliaIvakina NataliaIvakina merged commit 0bcc0d4 into neo4j:dev Mar 3, 2025
8 checks passed
@NataliaIvakina NataliaIvakina deleted the dev-initialize-db branch March 3, 2025 15:49
NataliaIvakina added a commit to NataliaIvakina/docs-operations that referenced this pull request Mar 3, 2025
…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.
NataliaIvakina added a commit to NataliaIvakina/docs-operations that referenced this pull request Mar 3, 2025
…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.
NataliaIvakina added a commit that referenced this pull request Mar 3, 2025
…well (#2154) (#2160)

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.
NataliaIvakina added a commit that referenced this pull request Mar 4, 2025
…well (#2154) (#2161)

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.
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.

4 participants