| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
| Cc: | Ilir Gashi <I(dot)Gashi(at)city(dot)ac(dot)uk>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Possible bug? |
| Date: | 2004-07-01 21:10:21 |
| Message-ID: | 5671.1088716221@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> writes:
> Technically speaking, I believe the queries are simply invalid without the
> presence of casts from the spec's standpoint.
Right. The reason PG doesn't error is that we have an implicit cast
from integer to text. I've opined before that we should mark most
cross-type-category casts as explicit-only ... they are just too prone
to give unexpected answers, as in this case.
It's interesting that Oracle seems to be converting text to integer
instead of vice versa. Or maybe they have some truly bizarre string
comparison operation that ignores leading '0'? Whatever they are
doing, there's no support for it in the spec.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jean-Luc Lachance | 2004-07-01 22:16:29 | Re: No rows returned from the SQL query (possible bug) |
| Previous Message | Stephan Szabo | 2004-07-01 19:42:57 | Re: Possible bug? |