You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Generated code should include the source code of views now that we have API for this content via TableOptions (#9799). In a first step, the source code will be in string form, as plain SQL. If we can parse it, we'll make a parse call.
Since there may be compilation or parser errors when such source code is being generated, we have to introduce this feature with a new guard flag: <sourcesOnViews/> in configuration/generator/generate/sourcesOnViews.
The sources will be made available through jOOQ-meta API via Definition.getSource() (see #9816)
Generated code should include the source code of views now that we have API for this content via
TableOptions
(#9799). In a first step, the source code will be in string form, as plain SQL. If we can parse it, we'll make a parse call.Since there may be compilation or parser errors when such source code is being generated, we have to introduce this feature with a new guard flag:
<sourcesOnViews/>
inconfiguration/generator/generate/sourcesOnViews
.The sources will be made available through jOOQ-meta API via
Definition.getSource()
(see #9816)Dialects for which this will be supported:
FORCE
keyword inCREATE FORCE VIEW
, in the parser: Various parser bugs / missing features #8452)XMLDatabase(implemented separately, through Add support for INFORMATION_SCHEMA.VIEWS in jooq-meta.xsd #9819)The text was updated successfully, but these errors were encountered: