Skip to content

Fix future-incompat report #828

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
wants to merge 2 commits into from
Closed

Fix future-incompat report #828

wants to merge 2 commits into from

Conversation

EricFecteau
Copy link
Collaborator

When building, connector-x provides a future-incompat warning (see here: https://github.com/sfu-db/connector-x/actions/runs/16383175035/job/46298417726?pr=827#step:12:534) for the crate connection-string v0.1.13. This was a dependency of the version of tiberius being used by connector-x. I updated tiberius to the latest version, and updated the related crates bb8 and bb8-tiberius. This also solved the incompatibility of uuid version 1 (removing the uuid_old crate.

Warning: I don't have an MS SQL server to verify that this did not cause any issues. Uncertain what to do about that.

@wangxiaoying
Copy link
Contributor

wangxiaoying commented Jul 20, 2025

Thanks @EricFecteau for the PR!

The old tiberius is kept due to this issue: #762 (downgraded in this commit: 37dd8ed). But I still don't know the root cause for this though.

@EricFecteau
Copy link
Collaborator Author

Ah yeah, that makes sense! Will close for now.

@EricFecteau EricFecteau deleted the future-incompat branch July 20, 2025 10:36
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.

2 participants