> This may be too simplistic an answer, but can't you just have the function
> return a text string and return the message you want to deliver back to
the
> client?
Thanks for your reply. However, this won't work because the INFO messages
are not the result or the function. They are a notification
>>>
I wrote something like:
CREATE sp_getuser(name, pass) RETURNS record AS
$body$
DECLARE
retval RECORD;
BEGIN
SELECT INTO retval * FROM Users WHERE userid=name AND passwd=pass;
IF NOT FOUND THEN
RETURN NULL;
ELSE
RETURN retval;
END;
$body$
LANGUAGE plpgsql;
What
> I'm desparately seeking for a simple way to send messages to the client
> during the execution of large stored procedures.
>
> RAISE INFO 'Now Processing %', thisCustomer;
>
> Doesn't do it, because the client console is cluttered with verbose
context
> information (e.g. backtrace). It's imposs
I'm desparately seeking for a simple way to send messages to the client
during the execution of large stored procedures.
RAISE INFO 'Now Processing %', thisCustomer;
Doesn't do it, because the client console is cluttered with verbose context
information (e.g. backtrace). It's impossible to foll
Hi,
I'm moving from Sybase to pgsql but have problems with stored procedures.
The typical procedure uses
a) named parameters,
b) local variable declarations and assignments
c) transactions
d) cursors, views, etc.
I can't seem to find these things in the Postgres function syntax.
Procedures can b
<[EMAIL PROTECTED]> schrieb im Newsbeitrag
news:[EMAIL PROTECTED]
> > CREATE PROCEDURE do_something
> > @song_id int,
> > @user_id int,
> > @method int,
> > @length int = 0,
> > @date_exact datetime,
> > @default_country int = null
> > AS
> >-- temporary variables
> >
"Joshua D. Drake" wrote:
> Andre Schnoor wrote:
> > Hi,
> >
> > I am moving from Sybase to pgsql but have problems with stored procedures.
> > The typical procedure uses
> >
> > a) named parameters,
> > b) local variable declarations and ass
Hi,
I am moving from Sybase to pgsql but have problems with stored procedures.
The typical procedure uses
a) named parameters,
b) local variable declarations and assignments
c) transactions
d) cursors, views, etc.
I can't seem to find these things in the Postgres function syntax.
Procedures can
