Hi there,
2014-01-27 Sha <[email protected]>
> Not a problem.
>
> Me slowing gaining knowledge of JOOQ , and able to resolve problems on my
> own.
>
Sounds great! :-)
> Except ,
> Calling procedures within another procedure.
>
Well ... have you thought about it this way? If in T-SQL, a procedure A
calls a procedure B, then in Java, a method A will call a method B? And
both methods contain jOOQ code.
> And temporarily storing the records like temp tables.
>
Yes, there's really no easy way around this. But actually, I'm wondering if
this should really be a new jOOQ feature. A T-SQL temporary table is really
not that different from a jOOQ Result. It should be able to select from
jOOQ results, or join them, or pass them to T-SQL functions. Maybe, there
should be a method like:
<R extends Record> Table<R> table(Result<R>)
I'll register this as feature request #2984
https://github.com/jOOQ/jOOQ/issues/2984
Note, though, that I still think it is a bad idea to load local temporary
tables into Java memory, from a performance perspective.
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.
