Thanks a lot for the feedback, Samir 2017-03-21 14:20 GMT+01:00 Samir Faci <[email protected]>:
> I looked at pulling DAO into our auto-generation code and never really > found much use to them. Usually the way they fetch a record isn't really > correct for my use case. > > ie. A lot of times fetching by the PKey isn't what I'm looking for and at > least when I was looking at this there wasn't really an obvious way of > doing custom fetching behavior or really to expand upon it. > > For simple Crud I'd much rather use the Record type. > > record.refresh() > record.update() > record.store() > That's exactly the point. > give me all I actually care about and the .fetchInto() combined with the > auto-generated pojos are all I've used. > Oh, interesting bit about the auto-generated POJOs. So, they're sufficient for (most) of your use-cases? From the jOOQ perspective, they're closely linked to the DAOs (so, the deprecation *might* also touch on that POJO generation). > +1 on dropping support for it. I don't object to DAO/Repository design > pattern but I find that I usually need to write customized > code rather then relying on auto-generated code for most of my use cases. > Exactly. The DAOs are too opinionated / simple for that customized implementation -- 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.
