| From: | "D'Arcy" "J(dot)M(dot)" Cain <darcy(at)druid(dot)net> |
|---|---|
| To: | miker(at)scifair(dot)acadiau(dot)ca (Michael Richards) |
| Cc: | darcy(at)druid(dot)net, vev(at)michvhf(dot)com, pgsql-patches(at)postgreSQL(dot)org, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [PATCHES] Patches to get number of tuples affected |
| Date: | 1999-06-30 19:20:50 |
| Message-ID: | m10zPuc-0000dEC@druid.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Thus spake Michael Richards
> > Why not overload PGTuples() instead (assuming it doesn't already do this)?
As mentioned in another posting, I meant PQntuples().
> Tuples returned tells you how many you can get using the getvalue series.
> If you tried that with an update, it core dumps. I think the two are
> really related, but fundamentally different.
I'm just thinking that it's easy for PQntuples() to tell what it has
to return and branch accordingly. It just makes it easier to remember
the function. No asking which get tuple count function works for update
and which for select.
--
D'Arcy J.M. Cain <darcy(at){druid|vex}.net> | Democracy is three wolves
http://www.druid.net/darcy/ | and a sheep voting on
+1 416 424 2871 (DoD#0082) (eNTP) | what's for dinner.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Cary O'Brien | 1999-06-30 19:48:01 | Oracle and hot backups |
| Previous Message | D'Arcy J.M. Cain | 1999-06-30 19:13:54 | Re: [PATCHES] Patches to get number of tuples affected |