| From: | "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu> |
|---|---|
| To: | Postgres Hackers List <hackers(at)postgreSQL(dot)org>, Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>, Jan Wieck <jwieck(at)debis(dot)com> |
| Cc: | Vadim Mikheev <vadim(at)krs(dot)ru> |
| Subject: | Re: [HACKERS] Case statement ready? |
| Date: | 1998-12-04 15:44:11 |
| Message-ID: | 3668034B.40A651DB@alumni.caltech.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > I seem to have a CASE statement implemented...
OK, it looked to me that I'm not touching any files Vadim is working on,
so I've gone ahead and committed changes for the CASE construct to the
CURRENT (main) tree.
The changes don't actually affect the system catalogs, but I would
assume that we would not want this to be a feature added to the RELEASE
tree. Speak up if you think it should be added there too.
I've put in a rudimentary regression test for CASE, but I'll update that
soon with some better tests.
If anyone has a chance to look at the new code wrt the rewriter and
optimizer costing that would be great. For the costing I would assume
that the cost should be related to the sum of the costs of the
individual clauses within the CASE statement (or maybe half of the sum).
- Tom
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oleg Broytmann | 1998-12-04 16:06:13 | Re: [HACKERS] Date/time on glibc2 linux |
| Previous Message | Michael Meskes | 1998-12-04 15:04:15 | Re: [HACKERS] Date/time on glibc2 linux |