Hi Michael, > Is there a reason why the equals method in AbstractStore is final?
There is no specific reason for the equals method to be final. In general I tend to design my implementation classes using final methods for two reasons: 1. It's easier for me to implement my own API, as I always know which methods must/may/can't be implemented/overridden. 2. I can avoid inadvertently breaking client code by changing the API or implementation facts. > I have to overriding the equals method in my entities and now I have a > problem. In a framework the object methods should never be final > because only the business logic is responsible to deliver meaningful > implementations. I agree. Making equals() or hashCode() or any Object method final is probably not a good idea. I'll fix this in the next release: https://sourceforge.net/apps/trac/jooq/ticket/837 > By the way: Jooq is a fantastic project! Thank you
