Chris Shadek

@paulofaria do you have suggestions on the best way to fix this?

This is the part of the spec that specifies that mutations should run in series. http://spec.graphql.org/June2018/#sec-Mutation

Thanks. I'm using Postgres. If it helps, most of the logs have to do with shortening index or foreign key names, like the following: 2021-09-23T12:54:24-0400 notice codes.vapor.postgres : relation "_fluent_migrations"...

Also if it changes anything, I'm using ```autoMigrate()``` inside the setup method for XCTests.

I'm now using the latest version of every package and I still get the same behavior. See below: ``` let app = Application(.testing) try configure(app) app.logger.logLevel = .error app.addMigrations() try...

@paulofaria, is this an easy fix? I'd be happy to work on it if you can point me in the right direction.

@NeedleInAJayStack given the recent focus on improving connections, it might make sense to revisit this. Do you have an idea of how this might be achieved? The current solution is...

I believe this is no longer an issue after #84. Maybe this should be closed? We could add an example of connections to the Usage Guide.

Closing because #108 adds documentation to the Usage Guide to show how to use connections. Furthermore, other recent improvements that were introduced alongside `PartialSchema` should solve the double pass issue.

So I'm able to repeat the same error when I test an async function that includes a `defer` with a `Task`. (See below) For some reason, when I use the...