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

postgres-lambda-diff

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Tom Lane authored
    Although the SQL/JSON tech report makes reference to ECMAScript which
    allows both single- and double-quoted strings, all the rest of the
    report speaks only of double-quoted string literals in jsonpaths.
    That's more compatible with JSON itself; moreover single-quoted strings
    are hard to use inside a jsonpath that is itself a single-quoted SQL
    literal.  So guess that the intent is to allow only double-quoted
    literals, and remove lexer support for single-quoted literals.
    It'll be less painful to add this again later if we're wrong, than to
    remove a shipped feature.
    
    Also, adjust the lexer so that unrecognized backslash sequences are
    treated as just meaning the escaped character, not as errors.  This
    change has much better support in the standards, as JSON, JavaScript
    and ECMAScript all make it plain that that's what's supposed to
    happen.
    
    Back-patch to v12.
    
    Discussion: https://postgr.es/m/CAPpHfdvDci4iqNF9fhRkTqhe-5_8HmzeLt56drH%2B_Rv2rNRqfg@mail.gmail.com
    5f3bec07
    History
    Name Last commit Last update