In our own query usage, about half of the queries are dynamic. Mostly because similar static queries are merged into one form.
Actually the enforced order of the DSL API makes it complex, at least on the code level. The supported use cases are simple. DSL is about naming methods and supporting fluent / cascaded usage. It is as simple as the regular form, just different. Br, Timo. On Jan 5, 2:32 pm, Lukas Eder <[email protected]> wrote: > > Some users might start with the DSL approach and will need to refactor the > > whole query into the regular form when the structure becomes dynamic. > > Hmm, I personally think that this is rarely the case, but I might be wrong. > Is that something you know from your users? I prefer to keep the DSL API > simple but maybe I'll reintroduce a getQuery() method exposing the > implementation and the link to the regular API...
