2013/9/11 Nicholas Ustinov <nusti...@gmail.com> > 1) I suppose, ideally JOOQ should give choice to user: use native syntax > for hierarchical queries (recursive CTEs, connect by, or maybe smth else:)) > or use some crossDB syntax (maybe based on Oracle one), but with some > restrictions (I mean pseudo columns) >
In general, there's no such thing as a "cross DB" syntax. There are just db-specific features that can be emulated in *some* other databases. Such as CONNECT BY, which can be simulated with CTE. > 2) It's better to have partially implemented feature and possibilities for > improving it in future than not to have it at all :) (I mean extended list > of pseudo columns too) > Maybe :-) > 3) I suppose, recursive CTEs need to be defined in two steps to allow > recursive use of columns: at first we should define header of CTE/view with > column list but without actual implementation, and actual implementation, > maybe, included in SELECT statement. I'm not so good in JOOQ internal > structure, but I can try to express it in code... > Yes, please attempt to express it in code. I think I get your idea. You mean something similar to how PL/SQL, Ada allow for declaring stuff first and then providing the actual implementation further down? > 4) I think, here, in CTEs, we touch the same problem as problem of > defining reusable parts of SQL with implementation and some field contract. > I'm not sure what you mean by this. 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 jooq-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
