I am the other person Garret was referring to. This was never a bug in
JOOQ but likely a miscommunication between us or confusion on behalf of one
of us.
At some point either me or another developer here intentionally generated
JOOQ code for the "pg_catalog" schema methods md51 and md52 so that we
could reference them from Java. We later decided we didn't need to
reference those methods anymore.
I came across this post because I was just today re-generating the source
code and trying to figure out why these methods weren't also regenerated.
For future reference for myself, if I ever do need to generate source for
these pg_catalog methods, this is how to configure it:
<generator>
<name>org.jooq.util.DefaultGenerator</name>
<database>
<name>org.jooq.util.postgres.PostgresDatabase</name>
<includes>md5*</includes>
<excludes></excludes>
<schemata>
<schema>
<inputSchema>pg_catalog</inputSchema>
</schema>
</schemata>
</database>
On Monday, April 11, 2016 at 1:46:36 AM UTC-7, Lukas Eder wrote:
>
> Hi Garret,
>
> Thank you very much for the update.
>
> No worries, it happens to the best. And as you've noticed yourself, after
> waiting long enough, some things just disappear by themselves. :) I do hope
> you'll be using jOOQ again for another client, though!
>
> Since I couldn't reproduce it at the time, I haven't created any issues
> yet.
>
>
--
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.
