Ryan Leckey

```rust // 20210314225352_name.rs #[sqlx::migration] // generates fn main() that calls this migration function pub async fn migrate_default_materials( txn: &mut SqliteTransaction, ) -> Result { // Create tables and data Ok(())...

We now ( on master ) have an `Acquire` trait. This is not the clean API I was hoping for but it does **work** and that may be all you...

We used to do as you're suggesting with `impl Executor for Pool`. However, that would require `&mut` access to a `Pool`. Which, arguably isn't hard to get as you can...

This *will* be done but the main issue is how breaking a change it will be to change the type enumeration around before we stabilize it. We've tried to hide...

> If the inline form could also permit {foo.bar}, that would be amazing! We should probably follow the syntax recommendation here if we want to allow expressions: https://rust-lang.github.io/rfcs/2795-format-args-implicit-identifiers.html#alternative-solution---interpolation ```rust let...

@chakAs3 @tobiasdiez Can we **please** set this up? I would personally be a lot more motivated to contribute if I could use those contributions quickly without waiting for a formal...

That makes complete sense. I agree with a `WARN` with some threshold. We don't need to make it configurable, at least in the beginning.

> Format the SQL queries I think we can assume the queries are reasonably formatted? > Accurately parse the query type Do we need this? Looking back at my example,...

It's failing because now the typed documentation is being generated and that takes a serious amount of RAM. I'm away now but I'll try and circle back and add a...

The Hashgraph SDK _**does not actually use**_ Long v4. The primary usage comes from generated code from ProtobufJS. The ProtobufJS library uses Long v5. This only works right now because...