Hello, > I am trying out jOOQ (v2.2.2) against an Oracle 11.2.0.3 database API > that is heavily weighted towards pl/sql packages, views, and UDTs. > Previously I have used JPublisher to generate Java classes that can > call against this API. Using jOOQ - I am receiving compile errors in > the generated code. Is there a preferred method for reporting errors?
You can report issues on this user group, or directly in Trac, if you're sure it's a bug, and if you have a SourceForge account: https://sourceforge.net/apps/trac/jooq/newticket I have created Ticket #1358 for this: https://sourceforge.net/apps/trac/jooq/ticket/1358 > The DBAs that develop the database side like to overload their calls > to provide returned data in a variety of means. Here is one of the > errors I am encountering with Oracle package procedures. Here are 3 > retrieve text calls in the package (note one is called > retrieve_text2). I see. jOOQ uses indexes for disambiguation of overloaded stored procedures in packages. This is done, too, to prevent compilation errors, as Java: - doesn't support OUT parameters - doesn't support named parameters However, there is no check if disambiguated names would collide with other, similar names. Hence, disambiguation must become a bit more sophisticated. How does JPublisher do it? Cheers Lukas
