aboutsummaryrefslogtreecommitdiff
path: root/src/backend/parser/parse_oper.c
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2003-07-18 03:45:06 +0000
committerBruce Momjian <bruce@momjian.us>2003-07-18 03:45:06 +0000
commitfd4c775481f402dda989131edd28d365914cd528 (patch)
tree20bf9114a9986bb014a9c2ddf0aa300bcfa31e77 /src/backend/parser/parse_oper.c
parent5ea214b590f626154d11a28214ca7c774d9f8cb3 (diff)
downloadpostgresql-fd4c775481f402dda989131edd28d365914cd528.tar.gz
postgresql-fd4c775481f402dda989131edd28d365914cd528.zip
Stephen Robert Norris wrote:
> Well, no. What it says is that certain values must be escaped (but > doesn't say which ones). Then it says there are alternate escape > sequences for some values, which it lists. > > It doesn't say "The following table contains the characters which must > be escaped:", which would be much clearer (and actually useful). Attached documentation patch updates the wording for bytea input escaping, per complaint by Stephen Norris above. Joe Conway
Diffstat (limited to 'src/backend/parser/parse_oper.c')
0 files changed, 0 insertions, 0 deletions