"Sergey Moroz" <[EMAIL PROTECTED]> writes:
> So I wonder why doesn't postgres store hashes for all queries and
> misses parsing step if not needed like Oracle does?
Because we think it's a waste of cycles, not to mention storage.
regards, tom lane
I think the same way :). But as I mentioned in the first letter I'm not a C
guy. So I wonder why doesn't postgres store hashes for all queries and
misses parsing step if not needed like Oracle does?
On 8/3/07, Sibte Abbas <[EMAIL PROTECTED]> wrote:
>
> On 8/3/07, Sergey Moroz <[EMAIL PROTECTED]> w
On 8/3/07, Sergey Moroz <[EMAIL PROTECTED]> wrote:
> No that is not I meant. The problem in Prepared statements is in that you
> should determine SQL inside the function. I want to pass a query as a
> parameter, as well as query parameters.
> For example (I want to create a function like the follow
No that is not I meant. The problem in Prepared statements is in that you
should determine SQL inside the function. I want to pass a query as a
parameter, as well as query parameters.
For example (I want to create a function like the following):
select *
from exec_query(
On 8/2/07, Sergey Moroz <[EMAIL PROTECTED]> wrote:
> The problem is that I can't find the way to exclude query parsing (prepare
> step) for custom queries. In other words I want to create a function that
> accepts a query text with "$1, $2, etc." and variables as params, executes
> the query and re
The problem is that I can't find the way to exclude query parsing (prepare
step) for custom queries. In other words I want to create a function that
accepts a query text with "$1, $2, etc." and variables as params, executes
the query and returns a set of record. I could use 'execute' in plpgsql but
