| From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Peter Eisentraut" <peter_e(at)gmx(dot)net> |
| Cc: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>, "Oliver Elphick" <olly(at)lfix(dot)co(dot)uk>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: |
| Date: | 2002-09-13 04:56:36 |
| Message-ID: | GNELIHDDFBOCMGBFGEFOCEDKCEAA.chriskl@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > Bruce Momjian writes:
> >> I would love to say that this is related to change in casts, but that
> >> isn't the case.
>
> > Sure it is. The float=>int casts need to be made implicit, or
> we'll have
> > tons of problems like this.
>
> Well, yeah. That did not seem to bother anyone last spring, when we
> were discussing tightening the implicit-casting rules. Shall we
> abandon all that work and go back to "any available cast can be applied
> implicitly"?
>
> My vote is "tough, time to fix your SQL code".
Wasn't the resolution back then to "wait until beta and see who complains"?
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2002-09-13 04:59:59 | Re: |
| Previous Message | Alvaro Herrera | 2002-09-13 04:56:19 | Re: DROP COLUMN misbehaviour with multiple inheritance |