Return-Path: postarch
Received: by postgres.Berkeley.EDU (5.61/1.29)
	id AA01295; Fri, 14 Feb 92 11:36:33 -0800
Message-Id: <9202141936.AA01295@postgres.Berkeley.EDU>
From: postarch (Postgres Mailing Archive)
Subject: Re: Some problems with Postgres features
To: postgres@postgres.berkeley.edu
Sender: pg_adm@postgres.berkeley.edu
Reply-To: mer@postgres.berkeley.edu
In-Reply-To: Your message of "Wed, 12 Feb 92 10:19:14 PST."
             <9202121819.AA00277@postgres.Berkeley.EDU> 
Date: Fri, 14 Feb 92 11:36:16 PST

you write:

> We are having serious problems operating with strings. Comparisons involving
> this type don't work properly. Any idea?
>   
>   * retrieve (EMP.all) where EMP.name="Sam"
>   
>   Query sent to backend is "retrieve (EMP.all) where EMP.name="Sam"  "
>   WARN:Feb 10 23:25:44:OperatorDef: no operator =

This error message indicates that there is no operator = with the left
argument type of EMP.name.  Assuming that EMP.name is of type char16 or
text, my first guess would be that someone has been messing around with
the system catalogs.

> Defining Postquel functions don't work either for us. We are following
> the syntax indicated in the user's manual (page 9). Actually it's the
> example used there.
> 
>   
>   * define function pay 
>   (language = "postquel", returntype=EMP)
>   as 
>   retrieve (EMP.all) where EMP.salary 1300.0
>   \g

The manual syntax is incorrect.  It should be:

	define function pay (language = "postquel", returntype=EMP)
	arg is (EMP)
	as retrieve (EMP.all) where EMP.salary = 1300.0


Jeff Meredith
mer@postgres.berkeley.edu