From: | "Grigoriy G(dot) Vovk" <grigoriy(dot)vovk(at)linustech(dot)com(dot)cy> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | Chris Ruprecht <chrup999(at)yahoo(dot)com>, pgsql <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: Functions returning more than one value |
Date: | 2001-08-08 17:21:51 |
Message-ID: | 20010808201943.O574-100000@callisto.internal.linustech.com.cy |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
May be, in a far future, will be better to have a stored procedures which
will able to accept input arguments and output arguments?
Aug 8, 09:26 -0700, Josh Berkus wrote:
> Chris,
>
> > The called function (test2() in the example) will MODIFY the two
> > arguments
> > and then return a true value. After test2() has run, the value of the
> > two
> > arguments 'has changed' to what test2() has assigned to them.
>
> I understand, now. You're trying to replicate the functionality
> provided in programming languages using By Reference arguments.
>
> I could suggest a number of workarounds. However, I think rather that
> you should give serious consideration to *not* doing this in PL/pgSQL
> but doing it in a full-featured procedural (and/or Object Oriented)
> language instead. Java, Python, Perl and even 4GL would provide you
> with more robust functionality.
>
> For example, what you want is easily done in Java just by passing the
> input parameters as By Reference.
>
> Opinions on Middleware languages, anyone?
>
> -Josh Berkus
>
>
my best regards,
----------------
Grigoriy G. Vovk
From | Date | Subject | |
---|---|---|---|
Next Message | Grigoriy G. Vovk | 2001-08-08 17:26:33 | Re: REFERENCES constraint |
Previous Message | Josh Berkus | 2001-08-08 16:30:43 | Re: REFERENCES constraint |