avtrujillo

Looks like implementations are defined starting [here](https://github.com/SeaQL/sea-orm/blob/master/src/entity/active_model.rs#L653) for the following: - Option\\> where V: IntoActiveValue\ + Into\ + Nullable, - Option\ where V: IntoActiveValue\ + Into\ + Nullable, - bool...

I found out about moro through [this blog post](https://tmandry.gitlab.io/blog/posts/2023-03-01-scoped-tasks/), following a link from [this one](https://without.boats/blog/the-scoped-task-trilemma/), which together do a good job of laying out the problem space and where moro...

Realizing now that this is very similar to the changes made in [this branch](https://github.com/launchbadge/sqlx/commit/11ecb307d72a14cf327f1e273b06d12f6b6dd2cd), which is a couple months behind main

Currently taking a crack at this. I was wondering about the reasoning behind requiring the output of Executor::schedule() to be 'static. The comments of Executor::spawn_inner() mention that > // `self.schedule()`...