Closed lukaseder closed 1 year ago
Would it be possible to also support refresh
(admittingly I think just a PostgreSQL feature)
https://www.postgresql.org/docs/11/sql-refreshmaterializedview.html
i.e.,
refresh materialized view FOO with data
refresh materialized view FOO with no data
and maybe
refresh concurrently materialized view FOO ....
Presently I'm using raw SQL to do it, which is fine :-) Just if you're in that area, perhaps supporting refresh might be doable too :-)
Thank you.
@dharrigan Thanks for your suggestion. We could consider this, but it's unlikely this will be prioritised any time soon. There are more compelling syntaxes to support before this one...
No problem :-) As mentioned, having the ability to use raw sql is totally fine to accomplish this...you have a lot on your plate anyway :-) Maybe one day...
thank you.
I'll move REFRESH
to its own issue:
Will look into this issue (without REFRESH
) for jOOQ 3.19
We currently cannot
CREATE
,ALTER
, orDROP
materialized views. Supporting these statements is a prerequisite for being able to export them usingMeta.ddl()
: https://github.com/jOOQ/jOOQ/issues/6412Tasks
CREATE VIEW
OR REPLACE
~ (this isn't supported natively anywhere, except in Snowflake). Will do later: https://github.com/jOOQ/jOOQ/issues/15593IF NOT EXISTS
ALTER VIEW
IF EXISTS
DROP VIEW
IF EXISTS
COMMENT ON MATERIALIZED VIEW
DDL
export supportMetaImpl
MetaSQL
support for some dialectsTABLE
being a materialized view (asDatabaseMetaData::getTables
reportsTABLE
, instead ofMATERIALIZED VIEW
) for:XMLGenerator
XMLDatabase
Diff
Workarounds for limitations:
Dialects with similar features, which are out of scope for now:
Dialects with buggy implementations:
Future work