> You can also generate a path builder class so you can
> do the same thing for related objects too. For example:
>
> Artist.NAME.eq("Picasso") // equals
> Artist.DATE_OF_BIRTH.lt(now()) // less than
Having to repeat Artist. all over the place is exactly what I'd like to get rid
of.
Hmm...
...
... I see it's hard to see whether that's actually a problem or not.
I see myself arguing on matters of principle, which is nice but risks failure
when confronted with reality.
I also see John arguing with small examples, which is nice but risks failure
when trying to scale to complicated queries.
How about if everybody with an interest in the topic scour their projects for
the nastiest SQL that they have, and present them here?
We'd have a set of use cases that will really test the various approaches.
Regards
Jo
