Return-Path: pg_adm@postgres.berkeley.edu
Received: by postgres.Berkeley.EDU (5.61/1.29)
	id AA06496; Sat, 5 Dec 92 09:55:05 -0800
Message-Id: <9212051755.AA06496@postgres.Berkeley.EDU>
From: "Manoj K. Jain" <mjain@bronze.ucs.indiana.edu>
Subject: Fast Path .. again
To: postgres@postgres.berkeley.edu
Sender: pg_adm@postgres.berkeley.edu
To: postgres@postgres.berkeley.edu
Date: Sat, 5 Dec 1992 12:56:32 -0500 (EST)
X-Mailer: ELM [version 2.4 PL13]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 557       

The fast path facility works if it is used with the retrieve.
For example, this works:

* retrieve (retval = sal_lookup("Joe"::text)) \g

Query sent to backend is "retrieve (retval = sal_lookup("Joe"::text)) "
---------------
| retval      |
---------------
| 1200        |
---------------

*
But shouldn't it work the other way also, since the function sal_lookup
is defined as a retrieve?
* sal_lookup("Joe"::text) \g

Query sent to backend is "sal_lookup("Joe"::text) "
WARN:Dec  5 12:46:45:parser: syntax error at or near "sal_lookup"

Thanks,
-- Manoj