2017-05-11 23:59 GMT+02:00 Joseph P. <[email protected]>:
> So you like your XSD, I'm surprised but so be it. Let's postpone further
> discussions on the topic until we can speak of it "IRL".
>
Why IRL? Are there any expressions you'd like to use that would be NSFW? ;)
> Thanks a lot, I dig into this one and... used:
> database.withProperties(new
> Property().withKey(VERSION_PROPERTY_KEY).withValue("v"
> + version)));
>
> But then :
> - there's no getter for the properties, I had to cast the Database like
> this :
> ((AbstractDatabase) definition.getDatabase()).getProperties().getProperty(
> LatestModelGenerator.VERSION_PROPERTY_KEY)
>
-- could you put getProperty in Database as well?
>
You're absolutely right, thanks for pointing this out. Noted:
https://github.com/jOOQ/jOOQ/issues/6214
> - I'm unsure about the side effects of adding such a property... Is it
> safe?
>
Ideally, you'll configure them through your generator configuration. See
tns:Properties in:
https://www.jooq.org/xsd/jooq-codegen-3.9.2.xsd
(there it is again, the XSD)
> - if ever you've a better way...
>
No, that's the intended way. Writing the properties is straigthforward, and
that's what they are for. For arbitrary parameters to custom Database
implementations. jOOQ uses them out of the box for JPADatabase or
XMLDatabase, for instance.
> > I'm afraid, I'm not too happy to implement such a workaround here. Any
> additional protected method that exposes some of these internals is just as
> good as a user actually patching the logic completely.
>
> Somehow I was expecting this, as well as feeling selfish for asking ^^
> Good answer Sir!
>
You can always try :)
Thanks,
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.
