From: limr@yahoo.com
To: pgsql-sql@postgresql.org
Subject: Re: Escaping the $1 parameter in stored procedures
Date: 15 Oct 2003 07:12:44 -0700
Message-ID: <75f517f5.0310150612.106c5d78@posting.google.com> (raw)
References: <75f517f5.0310131218.3a2907e5@posting.google.com>
Found a solution:
-- my_constraint(0) = turn off constraint
-- my_constraint(1) = turn ON constraint
CREATE OR REPLACE FUNCTION my_constraint(INTEGER)
RETURNS VARCHAR
AS '
DECLARE
cmd VARCHAR;
BEGIN
IF $1 = 0
THEN
RAISE NOTICE ''Turning OFF constraints'';
cmd := ''ALTER TABLE $tName DROP CONSTRAINT "$1"'';
EXECUTE cmd;
cmd := ''ALTER TABLE $tName DROP CONSTRAINT "$2"'';
EXECUTE cmd;
ELSE
RAISE NOTICE ''Turning ON constraints'';
ALTER TABLE $tName
ADD FOREIGN KEY(key1) REFERENCES table1;
ALTER TABLE $tName
ADD FOREIGN KEY(key2) REFERENCES table2;
END IF;
RETURN ''OK'';
END;'
LANGUAGE plpgsql;"
limr@yahoo.com (robert) wrote in message news:<75f517f5.0310131218.3a2907e5@posting.google.com>...
> I'm running Postgres 7.3.2 in Redhat 9.0.
>
> I'm trying to execute a function below defined as a stored procedure
>
> ALTER TABLE tms_schedule DROP CONSTRAINT "$1";
>
> However, postgres thinks the "$1" is a parameter value. How do I tell
> postgres to treat it as a literal $1?
>
> TIA,
> Robert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: limr@yahoo.com
Subject: Re: Escaping the $1 parameter in stored procedures
In-Reply-To: <75f517f5.0310150612.106c5d78@posting.google.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox