Nothing Special   »   [go: up one dir, main page]

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: improve column type info #347

Merged
merged 7 commits into from
Jul 19, 2024
Merged

fix: improve column type info #347

merged 7 commits into from
Jul 19, 2024

Conversation

Weakky
Copy link
Contributor
@Weakky Weakky commented Jul 17, 2024

Overview

Related to https://github.com/prisma/team-orm/issues/1222.

Improve column type information so that Quaint can better infer its own ColumnType for the TypedSQL initiative.

@Weakky Weakky marked this pull request as ready for review July 17, 2024 16:19
@@ -7,11 +7,13 @@ pub struct TokenFeatureExtAck {
}

#[derive(Debug)]
#[allow(dead_code)]
Copy link
Contributor Author
@Weakky Weakky Jul 17, 2024

Choose a reason for hiding this comment

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

All of these are clippy fixes coming from Rust 1.79.0. I don't want to remove all of this code until we give tiberius proper attention again.

Copy link

Choose a reason for hiding this comment

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

Hm, github's mentioning a bunch of clippy warnings in files that weren't in this PR, I guess those are also to be left until this happens

@Weakky Weakky merged commit 0e2897a into main Jul 19, 2024
32 checks passed
@Weakky Weakky deleted the feat/better-column-type branch July 19, 2024 09:32
Weakky added a commit that referenced this pull request Jul 19, 2024
Weakky added a commit that referenced this pull request Jul 19, 2024
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.

3 participants