Re: Codegenerated Path-Expressions with Databases (Mariadb, Mysql) that have unique FK-names

2024-06-11 Thread 'Bernd Huber' via jOOQ User Group
sorry following correction to the second MatcherStrategy example. I tried it like this: .withFields( new MatchersFieldType() .withFieldIdentifier(new MatcherRule()

Re: Codegenerated Path-Expressions with Databases (Mariadb, Mysql) that have unique FK-names

2024-06-11 Thread 'Bernd Huber' via jOOQ User Group
thank you Lukas, im currently using a custom GeneratorStrategy. It seems when i use a custom GeneratorStrategy i can not additionally use the Matchers. I read about it in following page: https://www.jooq.org/doc/latest/manual/code-generation/codegen-matcherstrategy/ Quote: - "...Instead of

Re: Codegenerated Path-Expressions with Databases (Mariadb, Mysql) that have unique FK-names

2024-06-11 Thread Lukas Eder
Look into these sections: - https://www.jooq.org/doc/latest/manual/code-generation/codegen-generatorstrategy/ - https://www.jooq.org/doc/latest/manual/code-generation/codegen-matcherstrategy/ On Tuesday, June 11, 2024, 'Bernd Huber' via jOOQ User Group < jooq-user@googlegroups.com> wrote: > Im

Re: jOOQ+Liquibase+docker

2024-06-11 Thread Lukas Eder
Thanks for your comments folks, and for documenting your workarounds here, David. In fact, I can see the problem now in IntelliJ. And (much worse), I can see similar problems with ./gradlew test commands, when tampering with the build cache as part of this task:

Re: jOOQ+Liquibase+docker

2024-06-11 Thread David Bullock
Hi again, So just to check, I took the sourceSet {} hack out of a working build.gradle.kts, reloaded it, and watched as IDEA un-marked the codegen output dir as a 'source' directory in the GUI. This was on version 2024.1.1. Then leaving it alone, I upgrade to 2024.1.3. Upon load of the project,

Re: jOOQ+Liquibase+docker

2024-06-11 Thread David Bullock
Sheesh, I wrote some gorgeous comments on that issue, but they're all vanished. Basically, if you ran 'gradle build', it would work. But IDEA wasn't picking up the location of the generated files from the java/kotlin source-sets, and had 'good code is red' issues because of it. Explicitly

Re: jOOQ+Liquibase+docker

2024-06-11 Thread Pasha Finkelshtein
It doesn't seem so Pasha Finkelshteyn Developer Advocate [image: Logo] Mobile: +49 1525 981-7123 Email: pasha.finkelsht...@bell-sw.com bell-sw.com [image: facebook icon] [image: twitter icon] [image:

Jooq Typesafe Mapping Constructors vs Reflection

2024-06-11 Thread 'Bernd Huber' via jOOQ User Group
Hello guys, i wonder how you guys are defining your Business Models (DTOs) for the different use-cases and how you are defining the constructors of the DTOs for use with the Jooq Typesafe Api (convertFrom, Records.mapping, mapping, ...) For example: My DTOs have 3 kinds of fields: - Simple

Codegenerated Path-Expressions with Databases (Mariadb, Mysql) that have unique FK-names

2024-06-11 Thread 'Bernd Huber' via jOOQ User Group
Im using Mariadb, and the FKs in Mariadb need to be provided with a unique FK-name. see: - https://mariadb.com/kb/en/foreign-keys/ - Quote: "The symbol clause, if specified, is used in error messages and must be unique in the database." Sadly (because of this) the jooq-codegen generates

Re: jOOQ+Liquibase+docker

2024-06-11 Thread Lukas Eder
Hi group, Does anyone have insight into whether this issue has been resolved by IntelliJ? I vaguely recall having seen similar problems on some computer of mine, but I can't reproduce it with IntelliJ IDEA 2024.1.3 (Ultimate Edition), Build #IU-241.17890.1. Cheers, Lukas On Friday, April 5,

Re: Liquibase and Jooq against MySql testcontainer In Gradle SpringBoot Project

2024-06-11 Thread Lukas Eder
Thanks for your message. We'll have gradle examples eventually in our MCVE template: https://github.com/jOOQ/jOOQ-mcve/issues/41 They'll be using testcontainers too. Unfortunately, until then, I can't really comment about the "best way" to do it. (It will be very hard with gradle anyway, because