Hello Aaron, > You added printFKSetter() to the default code but the feature is missing in > the interfaces and the pojos.
The method signature wouldn't be compatible between records and pojos, so putting any such method in the interfaces will be tricky as generaetd interfaces are implemented by both records and pojos. Note, there aren't any fetchXXX() methods either in the interfaces. I can see how it might make sense in pojos but then the pojos wouldn't be pojos anymore. What do you think? Would that really add value to pojos? > The same is true for the DAOs where it would be interesting to have > getBy<ColumnName>( Long | Record ). Absolutely! Tracked as #1552: https://sourceforge.net/apps/trac/jooq/ticket/1552 I guess it would be called findBy[...] to align method names with existing ones. Or maybe fetchBy[...] to re-use the term "fetch"? Also, a distinction between "fetch", "fetchOne" and "fetchAny" might be interesting. Primary / unique key information could help knowing whether it is even possible that several records can be fetched from a single value. In other words, if a key is present on a column, then there would only be a "fetchOne" method for that column. Another possibility is to generate varargs parameters to "fetch", for instance: List<P> fetchByName(String...) > I'm also missing a getAll() method in the DAOs. It's called findAll(), see above.
