Hi,
I'm diving more into depth of the features outside the typical table
stuff, which I usually need.
I wrote a trigger that fires a function written in PL/Python, both works
fine so far.
But as I browsed my database via pgAdmin3 I recognized that there is
also 'Procedures' under 'public'
On 7/19/06, Anastasios Hatzis [EMAIL PROTECTED] wrote:
Hi,
I'm diving more into depth of the features outside the typical table
stuff, which I usually need.
I wrote a trigger that fires a function written in PL/Python, both works
fine so far.
But as I browsed my database via pgAdmin3 I
Merlin Moncure wrote:
there are differences. PostgreSQL only really supports functions and
on the lists they are used interchangably. on the -hacker list about
a year back there was a good discussion about implementing true SP and
why they would be needed.
mainly, SP are not externally
I saw the same behavior with Functions and Procedures. At first, I could not tell what made one go into the Function folder and one go into the Procedure one.The one thing that clearly distinguishes a Procedure (to be placed into the Procedures folder in PgAdminIII) is if you include an OUT
