Re: prepareable statements - Mailing list pgsql-patches

From Rod Taylor
Subject Re: prepareable statements
Date
Msg-id 1028154261.4116.40.camel@jester
Whole thread Raw
In response to prepareable statements  (nconway@klamath.dyndns.org (Neil Conway))
List pgsql-patches
> Peter objected to the EXECUTE syntax, whereas Rod Taylor said it was
> good. Not really sure which way to go...

Why I like Execute:

CALL is for use with functions, so they're different (non-conflicting)
commands.

Works like a function call -- but it's not a function.  It implies your
running something that has been prepared or compiled.  You compile the
source (etc.), then execute the binary.

You prepare the statement, then execute the result.

Lastly, Perl (DBI) uses execute(args) for a prepared statement so it's
somewhat familiar for a large group.


pgsql-patches by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: lock listing
Next
From: Thomas Lockhart
Date:
Subject: Re: int64 timestamp patch for contrib/pg_controldata