Re: quoting psql varible as identifier
От | Pavel Stehule |
---|---|
Тема | Re: quoting psql varible as identifier |
Дата | |
Msg-id | 162867791001040244x7b2a729fm6b8fdb0c490d2c6b@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: quoting psql varible as identifier (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: quoting psql varible as identifier
Re: quoting psql varible as identifier |
Список | pgsql-hackers |
hello 2010/1/2 Tom Lane <tgl@sss.pgh.pa.us>: > Pavel Stehule <pavel.stehule@gmail.com> writes: >> here is patch > > I looked at this patch a bit, and I think the real problem with it is > that it's not multibyte safe. You've copied backend code that is > allowed to assume it's in a safe encoding (ie, one where multibyte > characters can't contain non-high-bit-set bytes). This is not okay > on the client side, see SJIS and similar encodings. > > Where you need to start out is by cloning PQescapeStringConn, which does > a similar type of transformation correctly even in unsafe encodings. > I think we'd agreed upthread that libpq should provide > PQescapeIdentifier functionality anyhow. > I am looking on psql directory. Now I found, so in this directory is linked dumputil.c - It could little bit to help us. I have one question. If I understand well, the function fmtId isn't multibyte safe? So why is possible to use it in pg_dump? Pavel > Once you've actually read that code, you'll realize that it's okay to > treat the error result as a warning, which resolves the other point > of concern. Just print the message and use the result anyway. > > regards, tom lane >
В списке pgsql-hackers по дате отправления: