fix(meta): fix order when restoring metadata #19791
Open
+16
−1
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.
I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
#19763 didn't fix the issue correctly, since
alter table set schema
may result in a row of with obj_type=TABLE and schema_id > oid, which still violates the constraintFK_object_schema_id
.This PR ensures rows with obj_type=DATABASE are inserted first, then obj_type=SCHEMA, lastly others.
Checklist
Documentation
Release note