Thanks for the clarification, Simon On Wed, Oct 23, 2024 at 2:09 PM Simon Martinelli <simon.martine...@gmail.com> wrote:
> IMO, that’s the important message: “what jOOQ thinks a POJO is. It's a bag > of values, not an entity” > > As I said, I use DAOs and POJOs only for a demo because I have never found > a real-life use case. > If I had one wish, I'd wish you simply don't demo DAOs :) > One of the issues with equals/hashCode is that if I use the POJOs together > with some frameworks that use those methods, the current implementation is > incorrect in the context of those frameworks. > For example, if I use a POJO in a Vaadin Grid and try to refresh the item > in the Grid, this will not work because equals will return false after > editing the POJO. > I had the same issue with the jOOQ Records and therefore created this > https://github.com/72services/jooq-utilities > Yes, this seems to be similar to putting any mutable objects in HashSets (e.g. ArrayList). Though perhaps, the Vaadin Grid should then use an IdentityHashMap to keep track of objects? -- 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 jooq-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jooq-user/CAB4ELO79J0vPQFJqg-bpKtF0oQhgnaZF5c%3DwK%2BFnay3Spfwiig%40mail.gmail.com.
