Re: How to ensure column names are double quoted while using execute format when building a stored procedure?

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Shaozhong SHI <shishaozhong(at)gmail(dot)com>
Cc: pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: How to ensure column names are double quoted while using execute format when building a stored procedure?
Date: 2021-12-16 20:24:24
Message-ID: CAKFQuwbGYaCzAhyqu2FMB6xVYMNBjWEGRiGz873AnzMysF9a5w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Dec 16, 2021 at 1:21 PM Shaozhong SHI <shishaozhong(at)gmail(dot)com>
wrote:

> The following command runs but does not produce results as expected.
>
> Execute Format('insert into stats select %L as id, %2$L as checks,
> count(%3$s) from %4$s where %5$s is null', i, 'count of nulls in '||col,
> col, t_name, col);
>
> All columns have got capital letters in. How to ensure that the columns
> are double-quote when they are fed in as variables.
>
>
Quoting the relevant doc section:

https://www.postgresql.org/docs/current/functions-string.html#FUNCTIONS-STRING-FORMAT

type (required)
The type of format conversion to use to produce the format specifier's
output. The following types are supported:

s formats the argument value as a simple string. A null value is treated as
an empty string.

I treats the argument value as an SQL identifier, double-quoting it if
necessary. It is an error for the value to be null (equivalent to
quote_ident).

L quotes the argument value as an SQL literal. A null value is displayed as
the string NULL, without quotes (equivalent to quote_nullable).

David J.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Bryn Llewellyn 2021-12-16 20:36:22 Re: Packages, inner subprograms, and parameterizable anonymous blocks for PL/pgSQL
Previous Message Shaozhong SHI 2021-12-16 20:21:23 How to ensure column names are double quoted while using execute format when building a stored procedure?