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

adapter: mz_object_fully_qualified_names includes database and schema IDs #27069

Conversation

RobinClowers
Copy link
Contributor

Motivation

  • This PR adds a feature that has not yet been specified.
    The console often ends up joining mz_databases and mz_schemas manually, because we need the database and or schema IDs.

Checklist

  • This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
  • This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
  • If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
  • If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).
  • This PR includes the following user-facing behavior changes:
    • No public facing changes

@RobinClowers RobinClowers requested review from a team and morsapaes as code owners May 13, 2024 23:38
Copy link
Member

@benesch benesch left a comment

Choose a reason for hiding this comment

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

+1 from me on behalf of the SQL council.

@@ -3304,18 +3304,20 @@ UNION ALL
}
});

pub static MZ_OBJECT_FULLY_QUALIFIED_NAMES: Lazy<BuiltinView> = Lazy::new(|| BuiltinView {
pub static MZ_OBJECT_FULLY_QUALIFIED_NAMES: Lazy<BuiltinView> = Lazy::new(|| {
BuiltinView {
Copy link
Member

Choose a reason for hiding this comment

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

Something strange happened here.

@RobinClowers RobinClowers force-pushed the fully-qualified-names-view-includes-ids branch 3 times, most recently from 7fce374 to 45a88f9 Compare May 14, 2024 16:34
@RobinClowers RobinClowers force-pushed the fully-qualified-names-view-includes-ids branch from 45a88f9 to c9f99d4 Compare May 14, 2024 18:22
@RobinClowers RobinClowers force-pushed the fully-qualified-names-view-includes-ids branch from 091e90e to 81ca910 Compare May 14, 2024 21:16
@RobinClowers RobinClowers merged commit a5a1d30 into MaterializeInc:main May 14, 2024
74 of 75 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants