> I had also tried to put the routine in the from clause, because I had
> noticed the whole row value mess PostgreSQL introduces.
> The SQL workaround works great. At this point I think you're going to
> implement the from(Routine) method, right? I think it makes sense, since you
> can actually do SELECT * FROM myFunction(...) (and in most cases, that's the
> only alternative).
Yes, the SQL standard specifies the UNNEST() function (a.k.a. TABLE()
function). This already works beautifully for jOOQ's Oracle
integration, when functions return CURSOR, TABLE, VARRAY types:
SELECT * FROM TABLE(myFunction(...))
It will be the preferred way of implementation for Postgres, too, eventually
> I'm really enjoying jOOQ, I'm using it as parte of a university project and
> after having tried Hibernate and Cayenne I have to say this is much much
> better!
Great, thanks for the feedback
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/groups/opt_out.
