From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Douglas M(dot) Westfall" <dougw(at)net(dot)kent(dot)edu> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Bug Report |
Date: | 2003-11-23 18:43:49 |
Message-ID: | 28503.1069613029@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
"Douglas M. Westfall" <dougw(at)net(dot)kent(dot)edu> writes:
> 1) table contains a valid inet field
> 2) query works fine in pgsql 7.2 & 7.3
> 3) query no longer works in pgsql 7.4
> select * from <table> where <field> ilike '%<inetvalue>%' ;
> ERROR: Unable to identify an operator '~~*' for types 'inet' and '"unknown"'
> You will have to retype this query using an explicit cast
This certainly did not work in 7.3 (in fact, you are quoting the 7.3
spelling of the error message).
There is not and never has been a LIKE operator for inet values; it's
only defined for textual data types. The reason it "worked" in 7.2 was
that 7.2 would implicitly cast the inet value to text for you. In 7.3
we changed a lot of casts to not be implicitly invocable, because of the
potential for unexpected behavior. Personally I'd class this as an
example of exactly the kind of unexpected behavior we meant to
prevent...
Short anser: cast the field value to text.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Klint Gore | 2003-11-24 06:35:49 | variable not found in subplan target list? |
Previous Message | Tom Lane | 2003-11-23 18:30:16 | Re: IpcSemaphoreCreate: semget(...) failed: No space left on device |