Hi Christopher, Thanks for this feedback. I always felt that this is a place where there's room for improvement.
> For example: > https://sourceforge.net/apps/trac/jooq/ticket/1418 > As a user who reads the release note, this does not tell me what I can > do to benefit from that change (settings to activate? Or is it by > default? etc.). Usually, you can assume that jOOQ is always backwards-compatible. So if you don't know what the ticket does, you can assume that you won't be concerned. In this case, it's just the behaviour of OracleDatabase, that was changed to ignore the case of supplied <inputSchema/> names from the code generator configuration. You could always search the repository for #1418: https://github.com/jOOQ/jOOQ/commit/7e32e33e8648dfcf856d92f5a159d2120c50cfb1 Another way is to search the user group for ticket names. If there is a discussion, I always link the ticket to the discussion and vice-versa. But of course, searching the group and repository should be the last means of reconstructing some change. > Another one: > https://sourceforge.net/apps/trac/jooq/ticket/1253 > I think you said on the forum that some databases do not support > escape syntax, which information should have been added to the ticket. We've discussed escaping off the user group (unfortunately, that's why I'm CC'ing this to the group), so this information is in our private e-mails. Another jOOQ user asked me to increase the priority of this, unfortunately also in private e-mails... This is about users who want to use jOOQ to render SQL with inlined bind variables (for execution in third-party tools). They usually don't want any JDBC escape syntax in that SQL. So I took the time to figure out how every database handles date/time literals natively, such that the escape syntax can be avoided. I'll consider adding more information to the tickets in the future. Also, if I knew how to simply migrate the Trac tickets to GitHub, I'd love to do that. With GitHub, commits and tickets are better linked to each other, for easier trackability. In addition, more people have a GitHub account rather than a SourceForge account. Cheers Lukas 2012/7/8 Christopher Deckers <[email protected]>: > Hi Lukas, > > One thing that I get frustrated with the tickets is that I see the > title and the description but not how it got resolved. This is > particularily of interest for people who follow the release note ( > http://www.jooq.org/notes.php ) because it mentions the improvements > in the form of tickets. > > For example: > https://sourceforge.net/apps/trac/jooq/ticket/1418 > As a user who reads the release note, this does not tell me what I can > do to benefit from that change (settings to activate? Or is it by > default? etc.). > > Another one: > https://sourceforge.net/apps/trac/jooq/ticket/1253 > I think you said on the forum that some databases do not support > escape syntax, which information should have been added to the ticket. > > Basically, I am suggesting that all information related to a ticket be > added in the ticket and not just locked in your memories :) > > Hope this helps, > -Christopher
