Skip site navigation (1) Skip section navigation (2)

Re: Stored procedures - Oracle vs postgresql

From: Andreas Pflug <pgadmin(at)pse-consulting(dot)de>
To: Suresh Tri <trisuresh(at)yahoo(dot)co(dot)in>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Stored procedures - Oracle vs postgresql
Date: 2004-07-26 12:58:13
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Suresh Tri wrote:
> Hi all,
> I am currently trying to estimate the effort required
> to implement Oracle type stored procedure in
> PostgreSQL. As I understood Oracle supports both
> functions and procedures, but postgres only functions.
> ALso there are no OUT parameter in postgres.
> I got some info from 

Please be careful taking information from other websites as given. The 
view described there is Oracle-centric, and doesn't necessarily reflect 
PostgreSQL's need.

After a quick glance, just one aspect:
PostgreSQL indeed does not have default values for function parameters, 
but there are overloaded functions.
so instead of
function foo(bar text, nextbar text='someDefault')

you have
function foo(bar text, nextbar text)
function foo(bar text)
as 'select function(bar, 'someDefault')

which gives the same result. That's why PostgreSQL doesn't need default 

Stored procedures:
There actually is a way to return multiple values from a function, using 
a set. So procedure foo(bar int IN, result1 text OUT, result2 text OUT)
can be converted to a function foo(bar) RETURNS record

which can be retrieved as
SELECT result1, result2 FROM foo(bar) AS prc(result1 text, result2 text)

This might be supportable by wrapping it syntactically.

Some weeks ago we had a discussion about Oracle syntax support (or 
"loadable personality" support). The thread is named "LinuxTag wrapup" 
and started July 3rd, you might want to review it.


In response to

pgsql-hackers by date

Next:From: Andrew DunstanDate: 2004-07-26 13:06:51
Subject: Re: CVS web interface error
Previous:From: Gaetano MendolaDate: 2004-07-26 09:13:05
Subject: Re: Sketch of extending error handling for subtransactions

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group