Return-Path: pg_adm@postgres.berkeley.edu
Received: by postgres.Berkeley.EDU (5.61/1.29)
	id AA13229; Thu, 13 Feb 92 06:11:08 -0800
Message-Id: <9202131411.AA13229@postgres.Berkeley.EDU>
From: orestes appel <oappel@copper.ucs.indiana.edu>
Subject: Some problems with Postgres features
To: postgres@postgres.berkeley.edu
Sender: pg_adm@postgres.berkeley.edu
To: postgres@postgres.Berkeley.EDU
Date: Thu, 13 Feb 92 9:11:37 EST
Cc: oappel@copper.ucs.indiana.edu (orestes appel)
X-Mailer: ELM [version 2.3 PL11]

We sent this message before, but we haven't got any reply yet.
We REALLY appreciate any hint on this.
-------------------- Original Message follows -------------------------------

 
 Hi everybody,
 
 We are having serious problems operating with strings. Comparisons involving
 this type don't work properly. Any idea?
 This is an script of a faling query:
   
   * retrieve (EMP.all) where EMP.name="Sam"
   
   \g
   
   Query sent to backend is "retrieve (EMP.all) where EMP.name="Sam"  "
   WARN:Feb 10 23:25:44:OperatorDef: no operator =
    
 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. Again, the script follows:
 
   
   * define function pay 
   (language = "postquel", returntype=EMP)
   as 
   retrieve (EMP.all) where EMP.salary > 1300.0
   \g
   
   Query sent to backend is "define function pay  (language = "postquel", retu   rntype = EMP) as  retrieve (EMP.all) where EMP.salary > 1300.0 "
   WARN:Feb 10 23:27:41:no zero argument postquel functions
 
 
 If anyone has any idea of what's going on, please reply to the list or
 in private.
 
 Thanks in advance.
 
 	Orestes Appel 
 	Dan Jacobson
 	Manoj Jain