Re: scan.l: check_escape_warning()
От | Andrew Dunstan |
---|---|
Тема | Re: scan.l: check_escape_warning() |
Дата | |
Msg-id | 4787A6E5.9000801@dunslane.net обсуждение исходный текст |
Ответ на | scan.l: check_escape_warning() (Michael Meskes <meskes@postgresql.org>) |
Список | pgsql-hackers |
Michael Meskes wrote: > Hi, > > could anyone please enlighten me whether this function is still needed? > AFAICT check_escape_warning() only has significant action if > warn_on_first_escape is true. This variable is set to true only on label > xqstart, but to false on xestart. However, check_escape_warning() and > check_string_escape_warning() btw. are only called in mode xe. Seems to > me that both are never called, or what am I missing? > What you are missing is that xqstart can lead to mode xe if standard_conforming_strings is false: {xqstart} { warn_on_first_escape = true; saw_high_bit = false; SET_YYLLOC(); if (standard_conforming_strings) BEGIN(xq); else BEGIN(xe); startlit(); } cheers andrew
В списке pgsql-hackers по дате отправления: