Re: which statements need bind/describe messages?

My client library sends Parse/Bind/Describe/Execute/Sync for each query,
unless it's using a previously-prepared statement, in which case it can
omit the Parse message.

For which statements can I also avoid sending Bind and Describe?

As far as I can tell, I can just send Parse/Execute/Sync for any utility
statements (i.e. those that are handled by ProcessUtility()) that do not
UtilityReturnsTuples(). Furthermore, I can omit Describe for ordinary
(i.e. without "returning") INSERT and DELETE and UPDATE. Right?

I could also omit Bind for any queries that do not have bind parameters,
except that I always want binary-format results; so I suppose I always
have to send Bind for non-utility statements.

Comments appreciated.

-- ams

At 2008-08-09 15:57:42 +0530, ams(at)oryx(dot)com wrote:
>
> For which statements can I also avoid sending Bind and Describe?

I can't avoid sending Bind because Execute needs a portal and Bind is
what creates one. Let's pretend I didn't mention Bind at all. Sorry.

-- ams