You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some query hints are very specific values, rather than a boolean, like a timeout on an SQL query. Usually it is not too hard wired in a production grade system but configurable. It is impossible to achieve this behavior with @QueryHints({@QueryHint...}) since the value of QueryHint is not going through on expression language lookup (which would help to get the value at least from a properties/yaml file).
Another possibility I see, and it is somewhat covered in this ticket, is that the JpaRepository interface methods should support some kind of List structure as an input so we can pass them in programatically when we call those methods.
The text was updated successfully, but these errors were encountered:
Some query hints are very specific values, rather than a boolean, like a timeout on an SQL query. Usually it is not too hard wired in a production grade system but configurable. It is impossible to achieve this behavior with
@QueryHints({@QueryHint...})
since the value of QueryHint is not going through on expression language lookup (which would help to get the value at least from a properties/yaml file).Another possibility I see, and it is somewhat covered in this ticket, is that the JpaRepository interface methods should support some kind of List structure as an input so we can pass them in programatically when we call those methods.
The text was updated successfully, but these errors were encountered: