Joey de Waal
Joey de Waal
It seems like the stack is overflowing in debug mode, in release mode the tests pass.
> We probably need to do the same thing to `PgConnection` as was done to `MySqlConnection` and wrap the fields in a `Box`, then it'll be less to pass around....
Thanks for the comment, it did not support all nested domain types. I updated the PR and added the unit test from the mentioned PR.
The macro's don't know about your custom enum `UserClass`, you can override the inferred type with the [type override syntax](https://docs.rs/sqlx/latest/sqlx/macro.query.html#type-overrides-output-columns). E.g. `SELECT id, class as "class: UserClass" FROM ...`
The `#[derive(sqlx::Type)]` just implements the [`Type`](https://docs.rs/sqlx/latest/sqlx/trait.Type.html), [`Encode`](https://docs.rs/sqlx/latest/sqlx/trait.Encode.html) and [`Decode`](https://docs.rs/sqlx/latest/sqlx/trait.Decode.html) traits for your enum. This makes it possible to decode/encode the enum but the macro's still don't know about it.
> Lay some of the groundwork for the execution model refactor I've been meaning to do (run the connection on a background task for parallelism and cancellation safety) > This...
CI is passing and this PR is using your commit, so this should be ready for the next step. What should the replacement for the `Execute` trait look like? Also...
Ah I forgot to check the `Any` driver, that's unfortunate because it would solve #1430 and #1151.
Yes, I'll work on this today