From: | Patrik Kudo <kudo(at)partitur(dot)se> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: != and <> operators |
Date: | 2001-03-13 15:45:45 |
Message-ID: | Pine.BSF.4.31.0103131643470.6873-100000@tb303.partitur.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
How many of the other dbms' out there have this "hardwired hack"? Is
something that's postgres-specific, or is it found in oracle and sqlserver
too?
Regards,
Patrik Kudo
ech`echo xiun|tr nu oc|sed 'sx\([sx]\)\([xoi]\)xo un\2\1 is xg'`ol
Känns det oklart? Fråga på!
On Tue, 13 Mar 2001, Tom Lane wrote:
> Patrik Kudo <kudo(at)partitur(dot)se> writes:
> > I've for a while now been using the != operator in my sql queries, but in
> > almost all examples I see <> instead. Are there any good reason to use
> > any instead of the other? I prefer !=, but if you convince me, I'll change to
> > what you other guys are using ;-)
>
> "<>" is the SQL-standard name, and also the internal name of all these
> operators. There is a hardwired hack in the lexer to convert != to <>.
> So write whichever you feel like, but <> is what you'll see in dumps and
> so forth ...
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Ross J. Reedstrom | 2001-03-13 15:57:41 | Re: SQL Dummy Needs Help |
Previous Message | Richard Poole | 2001-03-13 15:07:52 | Re: Re: Use of the LIMIT clause ? |