Feature Request: Performant disableOptionWhen to Avoid N+1 Queries #16019
andrewdwallo
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Issue
When using
disableOptionWhen
with a Select component, it's highly probable to create an N+1 query problem:This becomes highly inefficient with many options.
Proposed Solution
Add a more efficient way to disable options based on model attributes without triggering separate queries if using a relationship(), or add some type of bulk behavior.
Beta Was this translation helpful? Give feedback.
All reactions