| From: | "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at> |
|---|---|
| To: | "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> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | RE: Re: Toast,bytea, Text -blob all confusing |
| Date: | 2001-08-30 07:33:15 |
| Message-ID: | 46C15C39FEB2C44BA555E356FBCD6FA41EB38C@m0114.s-mxs.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > > >For bytea, follow this rule: to escape a null character, use
this:
> > > >'\\0'. To escape a backslash, use this: '\\\\'.
Can anybody explain in technical terms why this is implemented
so inconveniently ?
Since bytea is probably not very common among users yet
we could imho still change it to not do double escapes.
Imho we need to decide where to do the escaping,
eighter in the parser or in the input functions.
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.
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Francesco Casadei | 2001-08-30 09:05:23 | Re: [SQL] getting the oid for a new tuple in a BEFORE trigger |
| Previous Message | Stephan Szabo | 2001-08-30 04:05:55 | Re: Odd rule behavior? |