aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeProjectSet.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2018-11-13 12:57:52 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2018-11-13 12:57:52 -0500
commitec937d0805b205e5b33ed4f3cb54f40230a826e3 (patch)
tree79bdb4c84952b7dc08f8d8d0e25d8dd96d9c39e5 /src/backend/executor/nodeProjectSet.c
parentd20dceaf50ea093234ef6a66bb2dae485468bea2 (diff)
downloadpostgresql-ec937d0805b205e5b33ed4f3cb54f40230a826e3.tar.gz
postgresql-ec937d0805b205e5b33ed4f3cb54f40230a826e3.zip
Align ECPG lexer more closely with the core and psql lexers.
Make a bunch of basically-cosmetic changes to reduce the diffs between the flex rules in scan.l, psqlscan.l, and pgc.l. Reorder some code, adjust a lot of whitespace, sync some comments, make use of flex start condition scopes to do that. There are a few non-cosmetic changes in the ECPG lexer: * Bring over the decimalfail rule (and support function process_integer_literal) so that ECPG will lex "1..10" into the same tokens as the backend would. I'm not sure this makes any visible difference to users, but I'm not sure it doesn't, either. * <xdc><<EOF>> gets its own rule so as to produce a more on-point error message. * Remove duplicate <SQL>{xdstart} rule. John Naylor, with a few additional changes by me Discussion: https://postgr.es/m/CAJVSVGWGqY9YBs2EwtRUkbNv=hXkN8yRPOoD1wxE6COgvvrz5g@mail.gmail.com
Diffstat (limited to 'src/backend/executor/nodeProjectSet.c')
0 files changed, 0 insertions, 0 deletions