Yeah, you're right, doesn't make sense to generate code on runtime, how I
missed it :(
But is there any simple way to generate code just when I want
programmatically ?
Does it work to do something like this ? .withSchemaVersionProvider("1") ?
and to save that value to a env var and change from time to time ?
On Monday, April 3, 2017 at 3:28:56 PM UTC+2, Lukas Eder wrote:
>
>
>
> 2017-04-03 14:24 GMT+01:00 Durim Kryeziu <[email protected]
> <javascript:>>:
>
>> Thanks for reply Lukas,
>>
>> In my case, the best situation is to execute only when I want,
>> unfortunately our database doesn't have versions neither we want to use
>> Maven plugin. For me best is to expose like I tried to do and call that
>> endpoint only when I want to call it.
>> Did I placed that code in the right place ?
>>
>
> I just now realised that you put that logic inside of a RestController.
> Why? I mean, code generation is something that happens at build time, not
> at runtime? What problem is running code generation through rest solving?
>
>
>> I also disabled the JooqAutoConfiguration from my Spring Boot app and did
>> all configuration what you did here:
>>
>> https://github.com/jOOQ/jOOQ/tree/master/jOOQ-examples/jOOQ-spring-boot-example/src/main/java/org/jooq/example/spring/config
>>
>
> I suspect that the stack trace is incomplete. Where does the
> StackOverflowError happen? In Spring, I guess, but why? Have you debugged
> through it?
>
> Cheers,
> Lukas
>
--
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.
