aboutsummaryrefslogtreecommitdiff
path: root/src/backend/parser/parse_expr.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2002-03-16 22:47:13 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2002-03-16 22:47:13 +0000
commit0f2fbbbac167818496ab59fdc11b9660cff2e747 (patch)
treee1d0fab9c7766e9dd6b4cde10de7f2b702c238d9 /src/backend/parser/parse_expr.c
parent134fe5ec61cb280459a4782b6d465e115c5ac5a8 (diff)
downloadpostgresql-0f2fbbbac167818496ab59fdc11b9660cff2e747.tar.gz
postgresql-0f2fbbbac167818496ab59fdc11b9660cff2e747.zip
Try to make array_in's behavior a tad less bizarre. Leading whitespace
before a data item is now always skipped, rather than only sometimes. Backslashes not within double-quoted text are treated reasonably, as are multiple sequences of quoted text in a single data item. But it still seems rather prone to misbehavior if the input is not completely syntactically correct --- in particular, garbage following a right brace will be ignored.
Diffstat (limited to 'src/backend/parser/parse_expr.c')
0 files changed, 0 insertions, 0 deletions