RE: SQL99 functions - Mailing list pgsql-hackers

From Peter Mount
Subject RE: SQL99 functions
Date
Msg-id 1B3D5E532D18D311861A00600865478CF1AF9A@exchange1.nt.maidstone.gov.uk
Whole thread Raw
In response to SQL99 functions  (Thomas Lockhart <lockhart@alumni.caltech.edu>)
List pgsql-hackers
Not knowing much on this side of things but in JDBC, CallableStatement
mentions things like IN, OUT & INOUT args - not sure about INOUT, but IN &
OUT are there. Perhaps OUT are not valid for selects, but are in stored
procedures?

Peter

--
Peter Mount
Enterprise Support
Maidstone Borough Council
Any views stated are my own, and not those of Maidstone Borough Council


-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Tuesday, June 27, 2000 9:51 AM
To: Thomas Lockhart
Cc: Hackers List
Subject: Re: [HACKERS] SQL99 functions 


Thomas Lockhart <lockhart@alumni.caltech.edu> writes:
> I see mention in SQL99 of function definitions which can have IN, OUT,
> and INOUT arguments. Any thoughts on how this could be supported in
> Postgres?

I noticed that but haven't quite figured out how it's supposed to fit
into the SQL worldview at all.  SurelySELECT foo(x) FROM table
shouldn't silently mutate into an UPDATE depending on how foo() is
declared.  Exactly where is a function with OUT args useful in SQL?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Philip Warner
Date:
Subject: Re: Proposal: More flexible backup/restore via pg_dump
Next
From: Giles Lean
Date:
Subject: Re: Proposal: More flexible backup/restore via pg_dump