From: | Gunnar Rønning <gunnar(at)polygnosis(dot)com> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | <andrea(dot)aime(at)comune(dot)modena(dot)it>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Ridicolus Postgresql review |
Date: | 2001-09-11 17:42:03 |
Message-ID: | m21yld7hg4.fsf@smaug.polygnosis.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
* Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
| server. PostgreSQL supports both of these things just fine. A whole
| 'nother thing is the ability to return result sets from functions.
|
| OK, other vendors may call the latter for "stored procedures", but that is
| terminological nonsense. And going out there writing an article claiming
| that in PostgreSQL "users do not have the ability to create their own
| stored procedures", without further qualification, is confusing at best.
That's not nonsense at all, you can't just go around and redefine the
language used in the database world at your own whims.
Everybody I know employed in the database arena thinks of a stored procedure
as something that may return result sets. In PostgreSQL it cannot and
does therefore not fit the term stored procedure.
What is confusing is the PostgreSQL use of the term "stored
procedure". To me it sounds like bad marketing, something we really
shouldn't need in the open source world.
--
Gunnar Rønning - gunnar(at)polygnosis(dot)com
Senior Consultant, Polygnosis AS, http://www.polygnosis.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Manuel Cabido | 2001-09-11 17:51:42 | Re: USA Disaster |
Previous Message | Lamar Owen | 2001-09-11 17:17:51 | Re: USA Disaster |