Replies: 1 comment 2 replies
-
Whilst this sounds perfect and works for many easy cases, at some point one will realize its shortcomings, that certain queries and the way the model system is setup will not work and not produce the desired result. At this point, you've to options: fix The dataloader approach itself is just an architectural concept and this library does not dictate whether you use overblog/dataloader-php or roll your own. All you do with such concepts is, you "write your own resolvers" everywhere. Which can be a lot of bloat for easy tasks (especially relations) but OTOH gives you complete freedom and ways of optimizing your results you cannot do with Further, TL;DR:
Personally I never used SelectFields, always dataloader approach (we rolled our own implementation though). And I'm still using this library in production, so it's not just some distant memory either. HTH! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi! I've read about SelectFields in issues and discussions and some developers prefer dataloaders.
What are any pros and cons of each approach?
Currently, I've got a problem with using ::select and ::with methods in the same query, and I'm looking for some solutions.
Beta Was this translation helpful? Give feedback.
All reactions