Re: BUG #15632: Correctly escaped strings are mishandled in function

Поиск
Список
Период
Сортировка
От David G. Johnston
Тема Re: BUG #15632: Correctly escaped strings are mishandled in function
Дата
Msg-id CAKFQuwbECjX1NFh=9zfji7+7peDHEmjyCty=69tEO+rP57fuRA@mail.gmail.com
обсуждение исходный текст
Ответ на RE: BUG #15632: Correctly escaped strings are mishandled in function  (Kaleb Akalework <kaleb.akalework@asg.com>)
Список pgsql-bugs
On Mon, Feb 11, 2019 at 11:47 AM Kaleb Akalework
<kaleb.akalework@asg.com> wrote:
> To be clear what I want is to send in 'SOLD''' in the function so in the query it can be used as is to store the
finalstring as SOLD'. IF I use the functions you mention it will just "" or add more quotes.
 

Please don't top-post.

The methods mentioned work perfectly; any failure to do what you are
desiring is from improper usage.  Mistakes cannot be pointed out
unless you show them but here is one that does work.

create or replace function echo(in_str text)
returns text
language plpgsql
AS $func$
DECLARE qry text; res text;
BEGIN
--qry = 'SELECT ' || quote_literal(in_str) || ';';
--qry = format('SELECT %L', in_str);
--EXECUTE qry INTO res;
qry = 'SELECT $1';
EXECUTE qry INTO res USING  in_str;
RETURN res;
END;
$func$
;
SELECT echo($in$SOLD'$in$);
-> SOLD'

A combination of "format" (for identifiers) and "execute using" (for
literals) is arguably the best solution.

David J.


В списке pgsql-bugs по дате отправления:

Предыдущее
От: Kaleb Akalework
Дата:
Сообщение: RE: BUG #15632: Correctly escaped strings are mishandled in function
Следующее
От: Tom Lane
Дата:
Сообщение: Re: BUG #15631: Generated as identity field in a temporary table with on commit drop corrupts system catalogs