Re: encoding question
От | Christopher Kings-Lynne |
---|---|
Тема | Re: encoding question |
Дата | |
Msg-id | 0d2f01c35c88$9ecda210$2800a8c0@mars обсуждение исходный текст |
Ответ на | encoding question ("Christopher Kings-Lynne" <chriskl@familyhealth.com.au>) |
Список | pgsql-hackers |
I don't think you see what I mean :) I want to display the data on a webpage to the user. This means that a varchar containing the string "I don't want it", should not appear as "I don''t want it". So pg_escape_string isn't used there. bytea is different tho because the default display isn't terribly useful... Chris ----- Original Message ----- From: "Rod Taylor" <rbt@rbt.ca> To: "Christopher Kings-Lynne" <chriskl@familyhealth.com.au> Cc: "Hackers" <pgsql-hackers@postgresql.org> Sent: Thursday, August 07, 2003 9:46 AM Subject: Re: [HACKERS] encoding question > My other question is we play around with bytea fields to escape nulls and > chars < 32 and stuff so that when someone browses the table, they get > '\000<unknown>\000...', etc. However, are the other field types for which > we have to do this? Can you put nulls and stuff in text/varchar/char > fields? What about other fields? pg_escape_string pg_escape_bytea Escape everything :)
В списке pgsql-hackers по дате отправления: