I am using postgres 9.0.4 . I can actually use EXEC in psql which seem to be throwing some error in Craig's case. Also I am able to create procedure and execute them in pgadmin and psql. This piece of code was migrated from Oracle database (MS-SQL to Oracle then Oracle to Postgres). Nevertheless I am able to create independently a procedure also. Only In the ASP environmnet I am facing issue.
Below is the piece of code which I executed in Psql. edb=# EXEC employeedetailinsert( '529','55','Mamatha','Chandrashekar','0 9','03','9677756894','mamatha...@dell.com','12/10/2010','','7','Active','','Bang alore','IG','206','Muralikrishna','TG-DBA','TPDB','TPDB','No','',''); EDB-SPL Procedure successfully completed -----Original Message----- From: Alban Hertroys [mailto:haram...@gmail.com] Sent: Wednesday, December 07, 2011 2:56 PM To: Chan, Mamatha Kagathi Cc: ring...@ringerc.id.au; pgsql-general@postgresql.org Subject: Re: [GENERAL] [pgadmin-support] Help for Migration On 7 December 2011 10:08, <mamatha_kagathi_c...@dell.com> wrote: > The procedure definition is > CREATE OR REPLACE PROCEDURE > -- So I am not calling a function but a procedure. I don't think CREATE PROCEDURE is actually a valid command in Postgres. The 9.0 documentation seems to confirm that (http://www.postgresql.org/docs/9.0/static/sql-commands.html). In Postgres, "procedures" are void-returning functions - there's no difference. It's just a naming convention. Perhaps you're using some 3rd party code for MS-SQL compatibility? I imagine CREATE PROCEDURE would then be a simple wrapper around CREATE FUNCTION ... RETURNING void. Heh, didn't know you could define DEFAULT argument values like that, but it seems you can! -- If you can't see the forest for the trees, Cut the trees and you'll see there is no forest. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
