| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Sam Mason <sam(at)samason(dot)me(dot)uk> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Javascript support in the backend, i.e. PL/JS |
| Date: | 2007-11-16 17:18:09 |
| Message-ID: | 20644.1195233489@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Sam Mason <sam(at)samason(dot)me(dot)uk> writes:
> On Fri, Nov 16, 2007 at 10:56:55AM -0500, Tom Lane wrote:
>> More generally, I think that the average programmer would rather just
>> not be bothered with all these details; he'd want to write
>>
>> for (row in spi.query("...sql..." [, arguments])) { ...
> OK. Would you expect this to use cursors under the hood? I can't see a
> good way of making this work without them unless I accept that they're
> going to fail if the record set gets too large.
Yeah, you want it to "just work" ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2007-11-16 17:38:08 | Re: pg_ctl -t N register ?? |
| Previous Message | Bruce Momjian | 2007-11-16 17:08:22 | Re: [COMMITTERS] pgsql: update files for beta3 |