stored procedures

From: Alexander Lohse <al(at)humantouch(dot)de>
To: <pgsql-general(at)postgresql(dot)org>
Subject: stored procedures
Date: 2001-05-03 07:51:23
Message-ID: p05100300b716ba228008@[192.168.0.98]
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi,

I am very new to PgSQL and I am just trying to figure out what for to
use stored procedures.
What I read/tested up to now is that pl/pgsql seems to be a bit
clumsy to write. Possibly needing a lot of
trial & error.

So, I am not really sure what is the benefit of writing logic inside the DB.
Is there a performance benefit compared to processing via PHP?

I do not really see the use for me to separate logic from the other logic,
'cause then you'll have to worry about 2 sources!
(I usually have a DB only used by that specific application, and if
not it is at least the same language, so global function are stored
in shared code libraries.)

I see this is a powerful feature and it seems to make sense, but when
I scan across my apps, currently using MySQL, I am having a hard time
to imagine where I could use it.
As far as I figured now, the only thing I would put into DB-Logic
would be stuff like "deleting or updating related tables". But this
is what REFERENCES .... CASCADING does as well!

It would help me lot, if anyone could help me here to jump on that train.
Maybe one can tell me what he does with this opporunity.

Thank you very much in advance,

Alex
--
___________________________
Human Touch Medienproduktion GmbH
Am See 1
17440 Klein Jasedow

Alexander Lohse
Tel: (038374) 75211
Fax: (038374) 75223
eMail: al(at)humantouch(dot)de
http://www.humantouch.de

Responses

Browse pgsql-general by date

  From Date Subject
Next Message DaVinci 2001-05-03 07:53:34 Views and Rules again
Previous Message Diana Cionoiu 2001-05-03 07:39:10 troubles with postgresql 7.0.2