Hi Ryan > What do you think about bloating the UpdatableRecord object a bit more and > adding value change listeners to the record?.
Hehe, I see. Well, I will register the idea as a feature request #2010: https://github.com/jOOQ/jOOQ/issues/2010 I have plans of adding something like an org.jooq.Trigger, which can be registered to listen to all sorts of events that go through jOOQ (i.e. more sophisticated events than the ones received by org.jooq.ExecuteListener). Maybe, there can be UpdatableRecord-specific trigger actions, too: https://github.com/jOOQ/jOOQ/issues/1691 > My use case is that I am using the UpdatableRecord for data binding > purposes. It would be great to listen to value change events in the record > so I can then sync back to the UI. Is this mostly about value change events originating from calls like record.refresh()? Could you elaborate a bit more on what you'd like to do? > This UpdatableRecord object is like a swiss army knife. I love it :) Yes, well, there is always some risk with swiss army knife tools. If things aren't implemented in a very general way, they add too much complexity for users that don't need the extra feature. In this case, improved listener support will align well with what is currently called an ExecuteListener, though.
