Dynamic Hibernate Query Join Optimization

After the refactor, I built and deployed the feature branch to the dev environment and focused on validation. I tested all relevant combinations using Insomnia, including valid inputs, invalid values, and null or missing fields across every matching attribute. I documented request and response behavior and monitored application logs to confirm the query executed as expected and no new errors were introduced. I wrapped up by adding method-level documentation and clarifying inline comments to explain how the query is assembled and why certain decisions were made. The end result is a query that’s easier to maintain, more efficient under typical request patterns, and safer to extend in the future.

Then, I updated the repository implementation to reference those string constants instead of embedding SQL directly. I added boolean flags derived from the API request to represent which parts of the query should be included, which made the intent explicit and gave me a clean way to control how the query was assembled at runtime. One important change was moving from numbered positional parameters to named parameters. This allowed me to keep the primary query path unchanged while dynamically building the unioned portion of the query without having to constantly manage parameter ordering. With that complete, I added conditional logic to apply joins and WHERE clauses only when the corresponding request fields were present, reducing unnecessary joins and improving the query execution path.

I started by pulling the native SQL out of the large static Java string and breaking it into more focused pieces. I created and updated string constants for the base query, FROM clauses, WHERE clauses, and the group/order logic, which made the query much easier to reason about and modify without worrying about breaking unrelated parts.