There has also been an idea in the past to allow for other relational
operators on arbitrary table expressions, such as Table.select() but it was
rejected because the time wasn't ripe for such an operator yet, at the time:
- https://github.com/jOOQ/jOOQ/issues/13066
For the record, I'll
On Mon, May 20, 2024 at 4:49 PM fabio trabattoni
wrote:
> Thank you for your thoughtful response, Lukas. I'd like to clarify a few
> points:
>
> I don't consider my idea revolutionary, nor do I aim to build the next big
> framework from it. It was a simple attempt to solve a small problem.
>
>
Thank you for your thoughtful response, Lukas. I'd like to clarify a few
points:
I don't consider my idea revolutionary, nor do I aim to build the next big
framework from it. It was a simple attempt to solve a small problem.
While my idea resembles GraphQL to some extent, GraphQL is far more
Mine is a smaller attempt. I didn't want to build a general query engine, I
just wanted something that made sense inside a specific domain. The primary
goal is to force the devs to act in a well-defined pattern.
The general apporach is very similar though:
1) Create a simple grammar in the form
> An example of 2) is the DAO API, which I regret so much. It is such a
terrible bikeshed, being the only really opinionated thing in jOOQ. Sure,
users like it, and it can't be removed again for this reason. But it is not
well-designed. It was a "quick win," that will never implement the
Hello Fabio,
i just want to share my similar use-case, just to give a perspective to a
different way to solve dynamic querying.
- 1. a common Query-Model
- 2. a Mapper that maps the Query-Model to Dynamic Jooq
- 3. a Repository for each use-case that resolves data with help of
MULTISET,
Thanks for your message.
For the record of others following this discussion, it's a follow-up to
this Stack Overflow question:
https://stackoverflow.com/q/78495895/521799
Fetch plans like these aren't a new idea. JPA does indeed already explore
such functionality via entity graphs. I've seen
Hello everyone,
I hope this message finds you well. I’d like to share an idea for a
potential feature request, inspired by a brief discussion on SO with Lukas.
*INTRO* When starting a Java Spring project, developers often use JPA for
data mapping because it allows for quick and
