From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Dave(at)micro-automation(dot)net |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Sqlstatement with !=-1 fails |
Date: | 2001-10-09 16:33:05 |
Message-ID: | 3605.1002645185@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Dave Cramer" <Dave(at)micro-automation(dot)net> writes:
> pl=# select * from person where id !=-1;
> ERROR: Unable to identify an operator '!=-' for types 'int8' and 'int4'
> You will have to retype this query using an explicit cast
This is not a bug. It's a consequence of wanting to allow user-definable
multicharacter operator names. See the rules about allowable operator
names,
http://www.ca.postgresql.org/users-lounge/docs/7.1/postgres/sql-syntax.html#SQL-SYNTAX-OPERATORS
regards, tom lane
PS: no, != is not an SQL-standard operator name ... <> is.
From | Date | Subject | |
---|---|---|---|
Next Message | Jon Lapham | 2001-10-09 16:58:55 | Re: ERROR: cannot insert duplicate... on VACUUM ANALYZE |
Previous Message | Janning Vygen | 2001-10-09 16:22:10 | Creating html form definitions for a frontend inside postgresql?? |