...which is to query using a client, but return ActiveRecord objects.
This would trigger a scenario where the PORO association code would
fire, which has adverse side-effects with ActiveRecord.
Instead, we do a one-off check to ensure adapter developers don't fall
into this trap. The expectation is this scenario is
ActiveRecord-specific, so we're OK with an explicit one-off check.
...which is to query using a client, but return ActiveRecord objects. This would trigger a scenario where the PORO association code would fire, which has adverse side-effects with ActiveRecord.
Instead, we do a one-off check to ensure adapter developers don't fall into this trap. The expectation is this scenario is ActiveRecord-specific, so we're OK with an explicit one-off check.