Services has a GraphQLService that can be used to make recursive GraphQL queries from the service layer, which is sometimes more reasonable than doing complex SQL queries. Unfortunately doing so allocates another connection, which can lead to deadlocks if the pool is empty. This works around the issue by using another mapping that is bound to the Services database session rather than to the connection pool.
Serviceshas aGraphQLServicethat can be used to make recursive GraphQL queries from the service layer, which is sometimes more reasonable than doing complex SQL queries. Unfortunately doing so allocates another connection, which can lead to deadlocks if the pool is empty. This works around the issue by using another mapping that is bound to theServicesdatabase session rather than to the connection pool.I feel shame, obvs.