| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | David Rysdam <drysdam(at)ll(dot)mit(dot)edu> |
| Cc: | pgsql-interfaces(at)postgresql(dot)org |
| Subject: | Re: Not clear on what PQgetResult does |
| Date: | 2005-11-17 19:38:18 |
| Message-ID: | 451.1132256298@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-interfaces |
David Rysdam <drysdam(at)ll(dot)mit(dot)edu> writes:
> I don't understand in what sense PQgetResult is asynchronous.
It isn't. You can use it in an asynchronous client, but the way you do
that is by not calling it until PQisBusy says you can (which means the
whole result has arrived, and you're just calling PQgetResult to get
hold of it).
> If the latter, is pgtcl's pg_getresult supposed to work the same way?
Dunno ... there was no such command last time I looked at pgtcl.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rysdam | 2005-11-17 20:01:52 | Re: Not clear on what PQgetResult does |
| Previous Message | David Rysdam | 2005-11-17 19:00:41 | Not clear on what PQgetResult does |