Re: Re: [BUGS] BUG #4027: backslash escaping not disabled inplpgsql
От | Bruce Momjian |
---|---|
Тема | Re: Re: [BUGS] BUG #4027: backslash escaping not disabled inplpgsql |
Дата | |
Msg-id | 200904091618.n39GIWi25074@momjian.us обсуждение исходный текст |
Ответ на | Re: Re: [BUGS] BUG #4027: backslash escaping not disabled inplpgsql (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Re: [BUGS] BUG #4027: backslash escaping not disabled inplpgsql
|
Список | pgsql-hackers |
Tom Lane wrote: > "Kevin Grittner" <Kevin.Grittner@wicourts.gov> writes: > > Bruce Momjian <bruce@momjian.us> wrote: > >> I think the big issue is that having standard_conforming_strings > >> affect function behavior introduces the same problems we have had in > >> the past of having a GUC affect function behavior. > > > Can't that be managed with this CREATE FUNCTION option?: > > SET configuration_parameter { TO value | = value | FROM CURRENT } > > It can be, the question is whether we're prepared to break everything > under the sun until people add that. I think we would first have to agree to issue escape_string_warning warnings for code in PL/pgSQL functions, then think about having standard_conforming_strings control PL/pgSQL behavior; this is what we did with SQL and it seems to have worked. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. +
В списке pgsql-hackers по дате отправления: