Re: Passing a WHERE clause by trigger to a function

From: David Johnston <polobo(at)yahoo(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Passing a WHERE clause by trigger to a function
Date: 2013-06-04 12:47:12
Message-ID: 1370350032292-5757877.post@n5.nabble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Melvin Call wrote
> But I still have a question in that I'd like to know if I can pass the
> WHERE clause to the function so it can examine the query? Or will I have
> to
> test for the potential of acting on more than one row?

You can write a function that takes a text/varchar and builds a dynamic SQL
query that then is executed...but I highly advise against it. Basically you
open yourself to SQL injection attack vectors and passing in a where clause
to a function is a very non-intuitive and cumbersome API.

What you likely want are functions that do what you want and take a person
id as an input. Let the user decide the best way to obtain that person id.

David J.

--
View this message in context: http://postgresql.1045698.n5.nabble.com/Passing-a-WHERE-clause-by-trigger-to-a-function-tp5757825p5757877.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Andres Freund 2013-06-04 13:04:06 Re: More buffers used than a relation's relpages
Previous Message Melvin Call 2013-06-04 12:32:45 Re: Passing a WHERE clause by trigger to a function