From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
---|---|
To: | "Rod Taylor" <rbt(at)rbt(dot)ca> |
Cc: | "Hackers" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: encoding question |
Date: | 2003-08-07 02:07:14 |
Message-ID: | 0d2f01c35c88$9ecda210$2800a8c0@mars |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)rbt(dot)ca>
To: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>
Cc: "Hackers" <pgsql-hackers(at)postgresql(dot)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 :)
From | Date | Subject | |
---|---|---|---|
Next Message | Barry Lind | 2003-08-07 02:10:07 | Re: encoding question |
Previous Message | Robert Creager | 2003-08-07 01:57:02 | 7.4 Beta1: variable not found in subplan target lists |