2018-05-13 10:53 GMT+02:00 Simon Niederberger <[email protected]> :
> Given a SelectQuery<? extends Record>, I'm struggling with the effects > from basically an empty field list. > > > 1. The query is created with jooq.selectQuery(getTable()); > 2. Later, some joins might be added > > When fetching from the query, the issue is that multiple tables with > identical field names lead to wrong data when fetching into a POJO. > I'm assuming that by this, you mean using your query as a derived table. Then, yes, you're not allowed to have ambiguous column names. Only top level SELECT statements may expose ambiguous column names in SQL. However, I'm not 100% certain what you're trying to do. Would you mind explaining your use case a bit more? > How can I change the field list of the SelectQuery? Or would that be part > of https://github.com/jOOQ/jOOQ/issues/1492 ? > #1492 has been rejected, and there won't be anything similar to replace it. > Current workaround (note the placement in the org.jooq.impl package in > order to access package-private methods): > Don't do that! :-) 1. From JDK 9 onwards (at least when you move to the module path), you won't be able to have your own org.jooq.impl package 2. We'll change internal API in pretty much every minor release, so your code will break very certainly -- 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.
