| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
| Cc: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk>, <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <ZeugswetterA(at)spardat(dot)at>, <pgman(at)candle(dot)pha(dot)pa(dot)us>, <pgsql-hackers(at)postgresql(dot)org>, <pgsql-interfaces(at)postgresql(dot)org> |
| Subject: | Re: Roadmap for FE/BE protocol redesign |
| Date: | 2003-03-13 10:07:34 |
| Message-ID: | 20030313180705.T16715-100000@houston.familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-interfaces |
> > Obviously there is cost, but doing a lookup only on demand, has got to be
> > cheaper in the long run than including the entire column definition in the
> > message whether it's wanted or not?
>
> So if there are 100 fields, should we ask the backend
> the column name 100 times ?
No, you do a single select that returns 100 results...
Then you cache them in your frontend...
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hiroshi Inoue | 2003-03-13 15:05:22 | Re: Roadmap for FE/BE protocol redesign |
| Previous Message | Hannu Krosing | 2003-03-13 10:07:28 | Re: Roadmap for FE/BE protocol redesign |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hiroshi Inoue | 2003-03-13 15:05:22 | Re: Roadmap for FE/BE protocol redesign |
| Previous Message | Hannu Krosing | 2003-03-13 10:07:28 | Re: Roadmap for FE/BE protocol redesign |