From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | lockhart(at)alumni(dot)caltech(dot)edu (Thomas G(dot) Lockhart) |
Cc: | meskes(at)usa(dot)net, pgsql-hackers(at)hub(dot)org |
Subject: | Re: [HACKERS] PREPARE |
Date: | 1998-11-17 16:16:52 |
Message-ID: | 199811171616.LAA09176@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-interfaces |
> > I'm still holding back PREPARE for ecpg until I can think of a
> > good solution. The best of course would be in the backend.
>
> So what would it take to do this in the backend? I think the places
> which would need to be touched fall into areas I either know about or am
> starting to look at to implement the CASE clause.
>
> We'd need:
> - a "named buffer" (or several) to hold the intermediate input
portals
> - a way to pass in parameters or substitution arguments
SQL functions?
> - a way to decide if previous parser/planner/executor
> results can be reused
--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Taral | 1998-11-17 18:12:23 | RE: [HACKERS] SQL vs. OQL |
Previous Message | Tom Lane | 1998-11-17 15:25:31 | Re: [HACKERS] Tree type, how best to impliment? |
From | Date | Subject | |
---|---|---|---|
Next Message | Warren Craig | 1998-11-17 16:36:57 | ODBC and Access |
Previous Message | Thomas G. Lockhart | 1998-11-17 13:45:19 | Re: [HACKERS] PREPARE |