-
Notifications
You must be signed in to change notification settings - Fork 2.5k
Fix ordering issues in EXPORT DATABASE #10677
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
Closed
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…te the catalog entries
…inders CatalogEntryRetriever, add tests with created types and dependencies created by them
… dependencies of the generated columns are registered as dependencies of the table
…, don't make any cross-catalog dependencies, detect and properly error when CREATE OR REPLACE statements depend on itself
…recreated by GetInfo in the CatalogEntry
Tishj
commented
Feb 19, 2024
Tishj
commented
Feb 19, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some things I noticed:
(been a while since I actively worked on this)
…w we want to handle this in the future, we want to preserve some dependencies, but not all because dropping a column for example could result in dropping dependencies
One thing I discovered while playing around with this, in this case we would want to register the type as a dependency, but not the table used, currently we don't register any of them as a dependency. |
…is no way to introduce a dependency into a CTAS
Mytherin
added a commit
that referenced
this pull request
Oct 11, 2024
…s before export (#14196) This PR fixes duckdblabs/duckdb-internal#3050 This PR is a revival of #10677 We use GetNaiveExportOrder as we already do, but now we use `DependencyManager::ReorderEntries` to make sure a dependent entry gets exported first if the dependency manager is aware that there is a dependency on the entry.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Supersedes #8619
This PR fixes https://github.com/duckdblabs/duckdb-internal/issues/120
This PR fixes #8496
This PR fixes #9713
This PR will:
schema.sql
order #8619We introduce LogicalDependency as a precursor to PhysicalDependency, this merely contains the information needed to look up the catalog entry, so it's safe to serialize/deserialize
Inside
SingleFileCheckpointWriter::CreateCheckpoint()
there was a duplicate of GetNaiveExportOrder, this now uses theDependencyManager::GetExportOrder
methodViews now create a dependency on the table they're referencing (as long as they are in the same catalog)
This changes some existing behavior, but is in line with postgres behavior
1: Indexes are not included in this, this requires some additional work that needs to be done outside of this PR