-
-
Notifications
You must be signed in to change notification settings - Fork 171
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
Deprecate / remove driver in favour of binder #383
Comments
Umm yes. But driver also works for other DB drivers, i.e. the vanilla |
@tyt2y3 hello! I have a PoC for this. I can draft PR. |
Sure |
@tyt2y3 maybe it is better to create another crate for rusqlite and Postgres? |
Um... not sure will it be a lot of hassle if we use feature flags. Otherwise, if we have multiple crates, isn't it similar to the situation we are in now (having multiple driver crates) ? |
@Sytten @tyt2y3 I create PR for rusqlite: #388. I have a problem. I cannot create it in
Maybe do you know work around? |
Usually one solution to that is to have one crate per integration like I think the one crate per integration is the better approach. I would also consider naming them |
@Sytten I made another crate for rusqlite. You can see my PR, but it doesn't help. Now cargo thinks that have two roots in one workspace |
Hum lets just add it to the root workspace? In theory it should not conflict with the sqlite version of sqlx since its a different crate. |
@Sytten no... Because Cargo.lock is one for workspace. |
Ah I think Rusqlite and SQLx has a conflicting requirement to
I think we have a similar setup in SeaORM |
Yeah I linked the issue in cargo for that. It is a bit annoying but no other choice. |
If I do this, I got error:
|
@Sytten @tyt2y3 @billy1624 I created PRs.
After merge these PRs we can deprecated/remove |
Hey @ikrivosheev, about the updated CI. I think...
I think clippy and fmt is just a additional checking but not prerequisites. REF: a057563 |
Also, I notice the updated CI spawn a instance to compile the crate with a specific set of features enabled. I guess the old way (single instance multiple steps) might compile faster. Because it only compile the changes but not the whole library every single time. The old way:
|
The merge sequence would be?
@ikrivosheev feel free to rearrange the list. |
Thanks! Sounds like a good plan |
Yes, this is the correct order. |
@billy1624 I have corrected all comments about CI in all PRs. |
Hey @ikrivosheev, the CI looks good :) |
Down the line I am not sure binders will be necessary at all if we switch the way value are handled and we use optional features. I guess its not a bad step in the meantime. |
I think we need some steps before doing this... |
New PR: #431. I forget about |
Yeah if you put resolves #XX in the PR body it will close the issue automatically |
Actually, I think it also makes sense (to be architecturally consistent) to separate Line 35 in 70120b7
That would make |
|
@tyt2y3 when we can remove sea-query-driver from source code? |
I added a deprecate notice to sea-query-driver, so I think it's good to remove now! |
I don't think the two should be maintained as it is confusing for the users and the binder is a better / more flexible solution long term.
The text was updated successfully, but these errors were encountered: