Hello, I just stumbled upon the enhancement issue "#4724 Add Table.eq(Table<R>) and Table.ne(Table<R>)" [1]. I have trouble understanding when a self-join using the primary key (or all columns) would be useful. None of the self-joins I ever wrote were of the form ON t1.id = t2.id. Rather, I usually join ON t1.parent_id = t2.id or similar. Since the data from t1 and t2 will be duplicated, there is nothing new to filter or select. So what legitimate use cases are there for such a convenience method?
I realize the above discussion may not seem JOOQ specific, so let me add the following: I recently ran into unexpected behavior (to me) due to a subtle confusion of the `equal()` and `equals()` methods as documented in "#4366 Add on(Boolean), where(Boolean), having(Boolean), etc.". Therefore, if the Table.equal(Table<R>) feature will be included in 3.8, I'd at least like to understand the intended feature before I can accidentally trigger it ;-) Kind regards, [1]: https://github.com/jOOQ/jOOQ/issues/4724 [2]: https://github.com/jOOQ/jOOQ/issues/4366 -- 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/d/optout.
