Replies: 1 comment 4 replies
-
I guess the only thing we could do would be to detect this case and disallow eager loading. You cannot eager load unless all items being tactically eager loaded are using the same association definition. |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
In 5.63.0, tactical eagerloading was made to work with class table inheritance (here #1962). However, it doesn't support subclasses with different associations that have the same name (which was explicitly noted here: 9a9f111)
We have an existing schema that is relying that behavior (so we're still using 5.62.0). We're getting around to upgrading Sequel so I'm wondering if you'd consider handling that case for tactical eagerloading or have another suggestion.
Here is small demo to illustrate:
Using 5.62.0, the eagerloading doesn't work but the results are accurate:
After 5.63.0 tactical eagerloading kicks in but we get innacurate disc counts:
Let me know what you think. Thanks!
Beta Was this translation helpful? Give feedback.
All reactions