Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 901B44761A3 for ; Mon, 14 Oct 2002 10:44:50 -0400 (EDT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id D932B4760C9 for ; Mon, 14 Oct 2002 10:44:49 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.5/8.12.5) with ESMTP id g9EEirhR012330; Mon, 14 Oct 2002 10:44:53 -0400 (EDT) To: Constantin Teodorescu Cc: PostgreSQL Interfaces Subject: Re: What's wrong in this pltcl function ? In-reply-to: <3DAAD536.8030603@flex.ro> References: <3DAA8ADB.6060208@flex.ro> <12147.1034605407@sss.pgh.pa.us> <3DAAD536.8030603@flex.ro> Comments: In-reply-to Constantin Teodorescu message dated "Mon, 14 Oct 2002 17:31:18 +0300" Date: Mon, 14 Oct 2002 10:44:53 -0400 Message-ID: <12329.1034606693@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200210/37 X-Sequence-Number: 3199 Constantin Teodorescu writes: > I have replaced: > ... where id=\'\\$1\' > with > ... where id=\\$1 > and the error is now: > ERROR: Unable to identify an operator '=$' for types 'character > varying' and 'integer' Wup, you needed a space: ... where id = \\$1 BTW, if id is varchar it would be better to define the function as accepting varchar not bpchar, no? regards, tom lane