> #1846 I like the features.
I dislike the multitude of modes that the resultset could be in. You can't infer its contract from the type anymore, you have to inspect its configuration as well. The knee-jerk approach to solve that would be a separate subclass per mode (assuming you can't change the mode after creating the resultset). I don't know whether that would create problems elsewhere. > #2265 Can't say much about that one, I'm unsure what contracts are affected. However, this: > making all records updatable if fetched accordingly. sounds like that may be losing type information, i.e. that Record couldn't update to the database before and now it can; that's a loss of information available to the code maintainer, because now he has to infer the difference from data flow and can't rely on types anymore. I may be misinterpreting this though. HTH Jo -- 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/groups/opt_out.
