Received: from sapphire.albourne.com (root@sapphire.albourne.com [195.212.241.227]) by hub.org (8.9.3/8.9.3) with ESMTP id JAA59789 for ; Wed, 22 Sep 1999 09:38:33 -0400 (EDT) (envelope-from a.joubert@albourne.com) Received: from isadora.cy.albourne.com (akamas.albourne.com [195.212.241.254]) by sapphire.albourne.com (8.9.3/8.9.3/Albourne/CYS/1.6X) with ESMTP id QAA16390 for ; Wed, 22 Sep 1999 16:41:04 +0300 (EET DST) Received: from albourne.com (localhost [127.0.0.1]) by isadora.cy.albourne.com (8.9.3/8.9.3/Albourne/CYC/1.4) with ESMTP id QAA30071 for ; Wed, 22 Sep 1999 16:38:31 +0300 (EET DST) Sender: a.joubert@albourne.com Message-ID: <37E8DBD7.4E79A61E@albourne.com> Date: Wed, 22 Sep 1999 16:38:31 +0300 From: Adriaan Joubert Organization: APL Financial Services (Overseas) Ltd X-Mailer: Mozilla 4.61 [en] (X11; U; OSF1 V4.0 alpha) X-Accept-Language: en MIME-Version: 1.0 To: Postgresql Subject: Operator definitions Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I've got a big problem: I had an operator defined as follows: CREATE OPERATOR ^ ( leftarg = bit1, rightarg = bit1, procedure = bit1xor ); and this was fine until 6.5.1, but in 6.5.2 I get ERROR: parser: parse error at or near "^" I've got the same problem with CREATE OPERATOR | ( leftarg = bit1, rightarg = bit1, procedure = bit1or, commutator = | ); but at least that didn't work under 6.5.1 either. Can anybody give me a hint how to fix this? I know nothing about the parser, or lex or yacc so I don't even know where to start. I need to fix this rather urgently , as I have tons of plpgsql functions that make use of the ^ operator. At the moment I get a power for all of these which leads to pretty disastrous consequences :-(. If anybody can give me any hint at all, I'll have a go at fixing it. Much appreciated! Adriaan