| From: | "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu> |
|---|---|
| To: | Michael Meskes <meskes(at)usa(dot)net> |
| Cc: | pgsql-hackers(at)hub(dot)org |
| Subject: | Re: [HACKERS] PREPARE |
| Date: | 1998-11-17 13:45:19 |
| Message-ID: | 36517DEF.7989C4EC@alumni.caltech.edu |
| 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
- a way to pass in parameters or substitution arguments
- a way to decide if previous parser/planner/executor
results can be reused
What else?
- Tom
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Terry Mackintosh | 1998-11-17 14:55:14 | Re: [HACKERS] Tree type, how best to impliment? |
| Previous Message | The Hermit Hacker | 1998-11-17 13:25:10 | Re: [HACKERS] More PostgreSQL+CORBA |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 1998-11-17 16:16:52 | Re: [HACKERS] PREPARE |
| Previous Message | The Hermit Hacker | 1998-11-17 13:25:10 | Re: [HACKERS] More PostgreSQL+CORBA |