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

fix: Object name casing for views and schemas #927

Merged
merged 1 commit into from
Apr 27, 2023

Conversation

vrongmeal
Copy link
Contributor

Fixes: #908

@vrongmeal vrongmeal requested review from scsmithr and f0ssel April 27, 2023 19:41
Fixes: #908

Signed-off-by: Vaibhav <vrongmeal@gmail.com>
@vrongmeal vrongmeal force-pushed the vrongmeal/entity-name-fix branch from 60478b1 to 9a62077 Compare April 27, 2023 19:58
Copy link
Member

@scsmithr scsmithr left a comment

Choose a reason for hiding this comment

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

If everything passes, this looks good to me.

Comment on lines +261 to +267
/// [`SchemaReference`] represents a multi-part schema that may require further
/// resolution.
#[derive(Debug, Clone, PartialEq, Eq)]
pub enum SchemaReference {
Bare { schema: String },
Full { schema: String, catalog: String },
}
Copy link
Member

Choose a reason for hiding this comment

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

apache/datafusion#6096 includes a schema reference type that we can use once that's merged.

@vrongmeal vrongmeal merged commit a358336 into main Apr 27, 2023
@vrongmeal vrongmeal deleted the vrongmeal/entity-name-fix branch April 27, 2023 21:09
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.

Ensure proper casing for database names
2 participants