Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f2DF4Sx33976 for ; Tue, 13 Mar 2001 10:04:28 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id f2DF4Ct19231; Tue, 13 Mar 2001 10:04:12 -0500 (EST) To: Patrik Kudo cc: pgsql-sql@postgresql.org Subject: Re: != and <> operators In-reply-to: References: Comments: In-reply-to Patrik Kudo message dated "Tue, 13 Mar 2001 08:17:21 +0100" Date: Tue, 13 Mar 2001 10:04:12 -0500 Message-ID: <19227.984495852@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200103/260 X-Sequence-Number: 1919 Patrik Kudo 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