| From: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] parse_coerce question |
| Date: | 1999-08-05 14:39:29 |
| Message-ID: | 37A9A221.C06759B7@alumni.caltech.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > In any case, you'll need to make sure that you only promote types one
> > direction, so that (for example)
> > select intcol from table where intcol < 33.5;
> > gets evaluated correctly.
> That is not parse_coerce()'s problem --- it just does what it's told.
Right. I wasn't sure how you were going to implement it. If you are
doing everything the same, but just pre-evaluating the result, we
should be OK.
- Thomas
--
Thomas Lockhart lockhart(at)alumni(dot)caltech(dot)edu
South Pasadena, California
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 1999-08-05 14:52:00 | Idea for speeding up uncorrelated subqueries |
| Previous Message | Tom Lane | 1999-08-05 14:21:04 | Re: [HACKERS] parse_coerce question |