This is causing some severe headaches with a client of mine who has thousands of rows (not many but enough to slow down) which have many associations.
This adapter does a SELECT WHERE and counts that length when it should do a SELECT COUNT WHERE to prevent massive overhead.
Ive read about this issue in other adapters but mysql and postgres are probably a lot more up to date.
I'm happy to submit a PR to fix unless there's a solution elsewhere?
This is causing some severe headaches with a client of mine who has thousands of rows (not many but enough to slow down) which have many associations.
This adapter does a SELECT WHERE and counts that length when it should do a SELECT COUNT WHERE to prevent massive overhead.
Ive read about this issue in other adapters but mysql and postgres are probably a lot more up to date.
I'm happy to submit a PR to fix unless there's a solution elsewhere?