Hello, I've had a closer look at how this should be implemented if done thoroughly. Unfortunately, the information_schema.columns view is a bit complex and the linked stack overflow answers will not provide a reliable solution to this for all data types (e.g. when materialized views contain array types).
As the estimated deadline for 3.4 is already tight, I prefer not to include this anymore. The workaround to extend jOOQ-Meta in client code might already be sufficient if typesafe queries against materialized view are essential. Best Regards, Lukas 2014-05-07 20:40 GMT+02:00 Raman Gupta <[email protected]>: > Thanks for creating the issue Lukas, and the pointer to the plain sql > portion of the manual in the interim. It works :) > > Regards, > Raman > > > On Wednesday, May 7, 2014 2:11:42 PM UTC-4, Lukas Eder wrote: > >> Hi there, >> >> Thanks for the heads-up. I think this shouldn't be too hard to add to the >> code generator. I have registered #3254 for this, to be implemented in jOOQ >> 3.4: >> https://github.com/jOOQ/jOOQ/issues/3254 >> >> In the mean time, you could try to enhance PostgresDatabase in jOOQ-Meta, >> in order for it to report also materialized views according to what Erwin >> Brandstetter has suggested in your example here: >> http://stackoverflow.com/a/19147681/521799 >> >> >> 2014-05-07 20:01 GMT+02:00 Raman Gupta <[email protected]>: >> >> It doesn't work. >>> >>> information_schema.tables does not contain any information about >>> postgresql materialized views, at least currently: http://postgresql. >>> 1045698.n5.nabble.com/Re-Materialized-views-WIP-patch-td5740513i40.html >>> >>> See also: http://stackoverflow.com/questions/19127561/how-to- >>> introspect-materialized-views >>> >>> Since this doesn't work (and probably won't anytime soon), I'm looking >>> for the right way to create a select statement that includes a sub-query on >>> a materialized view joined with another table. Since I can't access the >>> materialized view directly via jOOQ, I can write the sub-query in pure SQL. >>> I can also run the sub-query and pass the results of it to the jOOQ query. >>> >>> But is there a way to use the Jooq DSL to hook up a plain-SQL query to >>> the in() clause of a Jooq query so that Jooq can execute it all in one db >>> call? >>> >> >> Yes, there is. You will find the necessary information in these sections >> of the manual: >> http://www.jooq.org/doc/latest/manual/sql-building/plain-sql/ >> >> 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. > -- 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.
