On 10/30/2012 03:14 PM, David Johnston wrote:
"LIKE" is apparently not an operator but a special SQL construct.
Almost. :) The real problem is this, from the manual:
"The operator name is a sequence of up to NAMEDATALEN-1 (63 by default)
characters from the following list:
+ - * / < > = ~
> -Original Message-
> From: pgsql-general-ow...@postgresql.org [mailto:pgsql-general-
> ow...@postgresql.org] On Behalf Of Thalis Kalfigkopoulos
> Sent: Tuesday, October 30, 2012 3:55 PM
> To: pgsql-general@postgresql.org
> Subject: [GENERAL] overloading LIKE operator
Hi all,
I'd like to be able to operate LIKE using as arguments an integer and
a text value.
In postgresql 9.0 the following raises an error:
# SELECT 123 LIKE '123';
ERROR: operator does not exist: integer ~~ unknown
LINE 1: select 123 like '123'; ^
HINT: No operator matches t
Ralph Smith wrote:
I never did get an answer to this.
I get:
ERROR: cannot change return type of existing function
HINT: Use DROP FUNCTION first.
** Error **
ERROR: cannot change return type of existing function
SQL state: 42P13
Hint: Use DROP FUNCTION first.
When I try t
On Fri, Jun 13, 2008 at 06:11:43PM -0700, Ralph Smith wrote:
> I get:
> ERROR: cannot change return type of existing function
> HINT: Use DROP FUNCTION first.
Don't use CREATE OR REPLACE for the second one. The OR REPLACE is
trying to replace a function of the same name.
A
--
Andrew Sulliva
I never did get an answer to this.
I get:
ERROR: cannot change return type of existing function
HINT: Use DROP FUNCTION first.
** Error **
ERROR: cannot change return type of existing function
SQL state: 42P13
Hint: Use DROP FUNCTION first.
When I try to:
CREATE OR REPLAC
Suresh Tri wrote:
But when I try to drop the existing || operator, I get the following
error
ERROR: cannot drop operator ||(text,text) because it is required by
the database system
Also I cannot modify the application which runs over the database.
Hence I cannot overload || (varchar,varchar) and u
Hi,
I was trying to overload concat operator ||(text,text) such a way that
it behaves like Oracle. i.e. I want 'abc' || null to return 'abc'
instead of null.
I know that it is not the expected behaviour in postgres, but since I
am migrating the database from oracle to postgres , I need this
behav
I used the internal function text_pattern_lt and it is working fine!
Thanks for helping.
cheers
Suresh
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Am Dienstag, 31. August 2004 15:18 schrieb Suresh Tri:
>> Can any one tell how to use the previous version of ooperator while
>> overloading one.
> Don't call the previous operator, call the function underlying the previous
> operator.
Or put them i
10 matches
Mail list logo
