Thanks for your patience. I've tried this with a more recent version of jOOQ but couldn't reproduce it. I vaguely recall having fixed something along these lines. Have you tried upgrading to jOOQ 3.10.5?
2018-03-01 19:52 GMT+01:00 Samir Faci <sa...@esamir.com>: > Here you go Lukas, > > psql --version > psql (PostgreSQL) 10.2 > > > > On Thu, Mar 1, 2018 at 8:01 AM, Lukas Eder <lukas.e...@gmail.com> wrote: > >> Hi Samir, >> >> Thank you for your report. In order to help reproduce this issue, would >> you mind indicating the database vendor and version? >> >> Indeed, using programmatic or configurative (as you did) generator >> strategies is the way forward to avoid these types of collisions. >> >> Thanks, >> Lukas >> >> 2018-02-28 17:50 GMT+01:00 Samir Faci <sa...@esamir.com>: >> >>> jooq: 3.9.0 >>> >>> when I try to generate a table, which is named tag that's contained >>> inside the schema named tag. (I know jooq doesn't like this but in the >>> past I'd end up with just a new table named tag_) I get the following error: >>> >>> >>> [ERROR] >>> /Users/samirfaci/projects/docker/mip-db/target/generated-sources/jooq/biz/neustar/ms/db/schema/legacy/tag/tables/Tag.java:[118,19] >>> error: cannot find symbol >>> [ERROR] symbol: variable IDENTITY_TAG >>> location: class Keys >>> /Users/samirfaci/projects/docker/mip-db/target/generated-sources/jooq/biz/neustar/ms/db/schema/legacy/tag/Keys.java:[41,77] >>> error: cannot find symbol >>> >>> >>> I think the correct value should be IDENTITY_TAG_ but just thought I'd >>> mention it. >>> >>> Our work around for now is to do something along these lines: >>> >>> <strategy> >>> <matchers> >>> <tables> >>> <table> >>> <!--when the schema and table are the same name, a >>> mismatch with the identity variables for the >>> tag table occurs, causing the generation to fail. >>> This resolves that--> >>> <expression>tag.tag</expression> >>> <tableIdentifier> >>> <expression>TAG_TABLE</expression> >>> </tableIdentifier> >>> </table> >>> </tables> >>> </matchers> >>> </strategy> >>> >>> >>> >>> Is there a better / recommended way of dealing with these types of >>> collisions? >>> >>> >>> -- >>> Thank you >>> Samir Faci >>> https://keybase.io/csgeek >>> >>> -- >>> 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 jooq-user+unsubscr...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- >> 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 jooq-user+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Thank you > Samir Faci > https://keybase.io/csgeek > > -- > 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 jooq-user+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- 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 jooq-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
