Skip to content
Snippets Groups Projects
Select Git revision
  • benchmark-tools
  • postgres-lambda
  • master default
  • REL9_4_25
  • REL9_5_20
  • REL9_6_16
  • REL_10_11
  • REL_11_6
  • REL_12_1
  • REL_12_0
  • REL_12_RC1
  • REL_12_BETA4
  • REL9_4_24
  • REL9_5_19
  • REL9_6_15
  • REL_10_10
  • REL_11_5
  • REL_12_BETA3
  • REL9_4_23
  • REL9_5_18
  • REL9_6_14
  • REL_10_9
  • REL_11_4
23 results

scan.l

Blame
    • Tom Lane's avatar
      61446e09
      Improve lexer's error reporting. You get the whole token mentioned now · 61446e09
      Tom Lane authored
      in parse error messages, not just the part scanned by the last flex rule.
      For example,
      	select "foo" "bar";
      used to draw
      	ERROR:  parser: parse error at or near """
      which was rather unhelpful.  Now it gives
      	ERROR:  parser: parse error at or near ""bar""
      Also, error messages concerning bitstring literals and suchlike will
      quote the source text at you, not the processed internal form of the literal.
      61446e09
      History
      Improve lexer's error reporting. You get the whole token mentioned now
      Tom Lane authored
      in parse error messages, not just the part scanned by the last flex rule.
      For example,
      	select "foo" "bar";
      used to draw
      	ERROR:  parser: parse error at or near """
      which was rather unhelpful.  Now it gives
      	ERROR:  parser: parse error at or near ""bar""
      Also, error messages concerning bitstring literals and suchlike will
      quote the source text at you, not the processed internal form of the literal.