Return-Path: postarch
Received: by postgres.Berkeley.EDU (5.61/1.29)
	id AA02807; Fri, 14 Feb 92 13:04:13 -0800
Message-Id: <9202142104.AA02807@postgres.Berkeley.EDU>
From: postarch (Postgres Mailing Archive)
Subject: follow up to: Some problems with Postgres features
To: postgres@postgres.berkeley.edu
Sender: pg_adm@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 13:04:02 PST


> > 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

I overlooked the intended action of the manual's postquel 
function.  It wanted a single set of employees whereas 
my function defines this set once for each employee.

The problem is that the support for postquel functions is incomplete.
Currently you must give the associated class as the first argument where
in this case you would like not to.  This type of function will be supported
in version 4.


Jeff Meredith
mer@postgres.berkeley.edu