Hi Andrus
I'm curious as to your reluctance to redundancy in this case ?
A few points to consider:
1. This is entirely a convenience API. It's goal is to inline code as
smoothly as possible, making it more concise and readable. The resulting
code should have as few grammatical markers and c
Hi Michael
Sorry I wasn't clear. What I meant is with an EXTRA boolean parameter like
in my original API proposal, like so:
public ObjectSelect apply( boolean onCondition, Consumer op )
{
if ( onCondition ) op.accept( this );
return this;
}
On Tue, 09 Jul 2024 17:11:33 +0200, Michae
Hi Nikita
That's an interesting suggestion with the Predicate parameter. I gave it
some thought and came up with the following concern.
Consider that ObjectSelect is a builder and that the fluent method
invocations can happen in "kind of" any order. So then if they're
rearranged it may re
Hi John
.and(yearRange != null ? APPOINTMENT_DATE.gt(yearRange) : expTrue())
Yeah, I remember trying this for Expressions as well initially.
It does get the job done but I was fussy and didn't like it for two
reasons:
1. The first is that it results in "AND 1=1" being added to the SQL
st
