Ivan Krivosheev

> Ah I think Rusqlite and SQLx has a conflicting requirement to `libsqlite3` The only solution is to not put the crate in the global workspace. I mean adding the...

@Sytten @tyt2y3 @billy1624 I created PRs. - https://github.com/SeaQL/sea-orm/pull/970 - remove `sea-query-driver` from SeaORM - https://github.com/SeaQL/sea-query/pull/423 - rewrite examples using `sea-query-binder` - https://github.com/SeaQL/sea-query/pull/416 - rewrite CI and add simple features to...

> The merge sequence would be? > > 1. [issues-383 Improve sea-query-binder #416](https://github.com/SeaQL/sea-query/pull/416) - rewrite CI and add simple features to `sea-query-binder` > > 2. [ issues-383 Rewrite examples using...

@billy1624 I have corrected all comments about CI in all PRs.

> 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...

I reopen the issues, PR: 1. https://github.com/SeaQL/sea-query/pull/422 2. https://github.com/SeaQL/sea-query/pull/423 3. https://github.com/SeaQL/sea-orm/pull/970

New PR: https://github.com/SeaQL/sea-query/pull/431. I forget about `thread-safe`

> Actually, I think it also makes sense (to be architecturally consistent) to separate `postgres` support to a dedicated crate as well: > > https://github.com/SeaQL/sea-query/blob/70120b7c99eb40009782066fbb9496d9638c2696/Cargo.toml#L35 > > That would make...

@tyt2y3 when we can remove sea-query-driver from source code?

@billy1624 can you fix `clippy warnings`? I think this is very useful.