On 2013-09-30 14:16, Mike Goodwin wrote:
In terms of h2 code is there a reason that the parameter references
need to be copied in the manner that they are? In my simplistic
understanding for a given stored procedure there will always be a
fixed number of parameters, so in an ideal world a single data
structure could be used to store those parameters. (Any generated sub
queries would have to reference the parameters by number but
presumably we always control that),
Some functions take variable numbers of parameters, which complicates
things. And then there are things which need to be re-evaluated because
they're in a sub-query, etc, etc.
SQL gets complicated fast :-(
Your particular test-case appears to have a VIEW which uses an ALIAS
FUNCTION (i.e. a Java stored procedure) to generate one of the the
view's query parameters, and then the ALIAS seems to be querying another
VIEW, which is __also__ getting the value of a query parameter from
__another__ ALIAS.
I look forward to seeing the reduced test-case, which I suspect will
still be a doozy :-)
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/groups/opt_out.
