Re: Creating functions and triggers

My sincere aplogies,
    My email client must have scrolled one email before I hit reply. I was trying to answer a person who wanted a
certainword in database query to trigger a system call, executing programs external to the database. Somehow, I ended
upanswering your post instead. I'm terribly sorry. 

scott.marlowe wrote:
> Bzzzzzzzzt. WRONG.  But thanks for playing.
>
> Generally speaking, createing triggers and functions to go with
> them is a safer way of setting up access to your data than allowing Joe Q
> Programmer full update/insert/delete access.
>
> Paul, Bruce Momjian's postgresql book has a nice little section on writing
> triggers / functions in plpgsql and a few other languages, and there are
> some examples throughout the docs that show you how to, although they
> aren't all collected in one place (one example might be in the trigger
> section, the next in the plpgsql section.)
>
> So, Dennis, how do I write a PHP script that does the equivalent of firing
> an after trigger?
>
> On Wed, 7 May 2003, Dennis Gearon wrote:
>
>
>>HOLY S**T!
>>
>><rant>
>>You are basically setting yourself up for a MICROSOFT sized security
>>hole. Can you say, "Seeqwell Server?"
>>
>>You'd be MUCH better off using a PHP, PERL, ASP, JAVA, COLD FUSION, etc.
>>script for doing that. THOSE places are the focus for much work in
>>preventing the misuse of system resources from an end user perspective.
>>
>>DATABASES are for holding data, and their relationships.
>>
>></rant>
>>
>>"Fontenot, Paul" wrote:
>>
>>>Is there a good, hold your hand type of tutorial or howto on creating
>>>functions and triggers and using them together? I'm learning PostgreSQL
>>>after spending years with MySQL and the information at
>>>techdocs.postgresql.org - while good, is a little deep for me right now.
>>>Specificly I would like to be able to read something that will tell me
>>>how to create a function that will can run a shell script when certain
>>>words are entered into a record. Thanks for your time and guidance.
>>>
>>> ***PRIVILEGED & CONFIDENTIAL***
>>>Unless expressly stated otherwise, this message (and any attachment(s)
>>>thereto) is confidential and may be privileged. It is intended for the
>>>addressee(s) only. If you are not an addressee, any disclosure or
>>>copying of the contents of this e-mail or any action taken (or not
>>>taken) in reliance on it is strictly prohibited. If you are not an
>>>addressee, please inform sender immediately and delete this message from
>>>your system.
>>>
>>>---------------------------(end of broadcast)---------------------------
>>>TIP 5: Have you checked our extensive FAQ?
>>>
>>>http://www.postgresql.org/docs/faqs/FAQ.html
>>
>>
>>---------------------------(end of broadcast)---------------------------
>>TIP 2: you can get off all lists at once with the unregister command
>>    (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
>>
>
>
>