From: | Bret Stern <bret_stern(at)machinemanagement(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Stored Procedure table/column args |
Date: | 2013-09-03 01:40:55 |
Message-ID: | 1378172455.3581.16.camel@centos-dev.machinemanagement.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, 2013-09-02 at 18:20 -0700, Adrian Klaver wrote:
> On 09/02/2013 06:06 PM, Bret Stern wrote:
> > 'psuedo
> >
> > Can you create stored procedures that are built from parameters as
> > below, or does this defeat the pre-compiled purpose of an SP?
> >
> > create function item_exists (tbl character varying, col character
> > varying, col_val character varying)
> >
> > DECLARE
> > x integer;
> >
> > PERFORM col FROM tbl
> > WHERE col="'" + col_val + "'"
> > IF FOUND THEN
> > x := 1;
> > else
> > x := 0;
> > end if;
> >
> > RETURN x;
> >
> > ....
> >
> > left out some syntax, but should deliver the idea
> >
> > trying to build build a generic "check for existing", that's not
> > specific to a specific table/column without returning recordset
> > object overhead
> >
> > any better ways
>
> http://www.postgresql.org/docs/9.2/interactive/plpgsql-statements.html#PLPGSQL-STATEMENTS-EXECUTING-DYN
It's all there. Regards. B stern
>
> > thanks
> >
> >
> >
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | David Johnston | 2013-09-03 02:01:55 | Re: ALTER TABLE transaction isolation problem |
Previous Message | Adrian Klaver | 2013-09-03 01:20:29 | Re: Stored Procedure table/column args |