Re: Allow COMMENT ON to accept an expression rather than just a string - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Allow COMMENT ON to accept an expression rather than just a string
Date
Msg-id 3973.1239475479@sss.pgh.pa.us
Whole thread Raw
In response to Re: Allow COMMENT ON to accept an expression rather than just a string  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: Allow COMMENT ON to accept an expression rather than just a string  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
Pavel Stehule <pavel.stehule@gmail.com> writes:
> But the proc
> CREATE OR REPLACE FUNCTION some_proc(tabname varchar)
> RETURNS void AS $$
> BEGIN
>   EXECUTE 'CREATE TABLE $1(a integer)' USING tabname;

> is more readable than EXECUTE 'CREATE TABLE ' || tabname || '(....

I was intentionally excluding the idea of substituting parameters for
names as opposed to constants.  For one thing it's fundamentally
ambiguous --- given
string_var := 'foo';
EXECUTE 'SELECT $1 FROM bar' USING string_var;

is that supposed to mean SELECT 'foo' FROM bar or SELECT foo FROM bar?

The other problem is that if you allow name substitution it becomes
entirely impossible to do any planning or even validity checking before
the parameter values are available.  So while string assembly is kind
of a pain in the rear when you really do need a dynamic name reference,
I think we should keep it firmly separate from parameter substitution.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Allow COMMENT ON to accept an expression rather than just a string
Next
From: Pavel Stehule
Date:
Subject: Re: Allow COMMENT ON to accept an expression rather than just a string