From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "hubert depesz lubaczewski" <depesz(at)gmail(dot)com> |
Cc: | postgresql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: strange change (and error) in 8.3 ? |
Date: | 2007-06-14 14:54:28 |
Message-ID: | 4857.1181832868@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"hubert depesz lubaczewski" <depesz(at)gmail(dot)com> writes:
> but in 8.3 i get:
> # select 1 where '1'::text in (1::int8);
> ERROR: operator does not exist: text = bigint
> why? i mean - i see that types are bad, but it worked in 8.2. why it was
> broken/modified in 8.3?
This is intentional --- implicit casts to text are gone. You should be
happy that the above now fails, because it's calling your attention to
the fact that you've got very ill-defined semantics there. Is the
comparison going to be done according to text rules, or according to
int8 rules? (This would matter, for instance, if there was a space
in the string.) There are dozens of examples in the archives of people
having been burnt by the old behavior, for instance
http://archives.postgresql.org/pgsql-general/2007-02/msg01028.php
http://archives.postgresql.org/pgsql-general/2007-02/msg00871.php
http://archives.postgresql.org/pgsql-hackers/2005-11/msg00510.php
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2007-06-14 14:57:56 | Re: DeadLocks... |
Previous Message | Frank Wittig | 2007-06-14 14:40:32 | Re: pg_xlog - files are guaranteed to be sequentialy named? |