| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at> |
| Cc: | "Joe Conway" <joseph(dot)conway(at)home(dot)com>, "Alex Pilosov" <alex(at)acecape(dot)com>, "Lincoln Yeoh" <lyeoh(at)pop(dot)jaring(dot)my>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Re: Toast,bytea, Text -blob all confusing |
| Date: | 2001-09-03 23:08:11 |
| Message-ID: | 11817.999558491@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at> writes:
> I think actually the backend parser has no business changing
> constants, he is imho only allowed to parse it, so he knows
> where a constant begins, and where it ends.
How do you propose to handle embedded quote marks in literals,
if there is no parser-level escape convention?
Don't suggest a type-specific escape convention; at the time the
parser runs, it's impossible to know what type the literal will
turn out to be.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-09-04 00:10:19 | Re: Re: Escaping strings for inclusion into SQL queries |
| Previous Message | James Thornton | 2001-09-03 23:02:47 | Postgres is eating my CPU |