Hi all, I've just started using JOOQ and am excited about it. I've hit a snag with something I'm trying to do, I can see a some ways around it but perhaps people on this list will point out the best way (or perhaps something obvious I'm missing).
As I understand, when building a query, the returned type goes through various steps e.g. SelectJoinStep, SelectConditionStep. This is clearly beneficial in most cases. However, in my case, I want the query to be built up by different parts of the code - for example, one part will add certain joins, another part will add certain other constraints, which are part of a "configuration" stage, before finally giving it to the main part of the code that will then build and execute the rest of the query [1]. The problem is, if I've needed to add some constraints on the SelectConditionStep, I don't have the SelectJoinStep any more. Actually, if I simply retain a reference to the earlier Join step, I can still modify it, and that seems to work - is that luck, or can I rely on this now and into the future? A quick look at the code makes me think it's OK, but I didn't dig too deep. Is there a "best practice" for this kind of use case? Happy to write more if my use case isn't very clear. Thanks, Dan [1] The motivation is to factor out certain query filtering (say, date ranges, or content versions, etc) from the main logic of the feature doing the query, as what filtering applies can change depending on context orthogonal to the feature. -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
