Re: Command Triggers, patch v11 - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Command Triggers, patch v11
Date
Msg-id 1332176001.8435.1.camel@vanquo.pezone.net
Whole thread Raw
In response to Re: Command Triggers, patch v11  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Command Triggers, patch v11  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On sön, 2012-03-18 at 21:16 -0400, Tom Lane wrote:
> If we were going to change the output at all, I would vote for "CREATE
> TABLE nnnn" so as to preserve the rowcount functionality.  Keep in
> mind though that this would force client-side changes, for instance in
> libpq's PQcmdTuples().  Fixing that one routine isn't so painful, but
> what of other client-side libraries, not to mention applications?

Doesn't seem worth it to me.  At least, "SELECT nnnn" makes some sense:
nnnn rows were selected.  "CREATE TABLE nnnn" means what?  nnnn tables
were created?

What might make sense is to delegate this additional information to
separate fields in a future protocol revision.



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Command Triggers, patch v11
Next
From: Robert Haas
Date:
Subject: Re: Command Triggers, patch v11