Skip site navigation (1) Skip section navigation (2)

plproxy - plproxy: Make scanner accept dot as standalone symbol

From: mkz(at)pgfoundry(dot)org (User Mkz)
To: pgsql-committers(at)postgresql(dot)org
Subject: plproxy - plproxy: Make scanner accept dot as standalone symbol
Date: 2009-06-29 13:37:58
Message-ID: 20090629133758.48FA21072079@pgfoundry.org (view raw or flat)
Thread:
Lists: pgsql-committers
Log Message:
-----------
Make scanner accept dot as standalone symbol

Currently PL/Proxy fails to parse following query:

  select (ret_numtuple(1)).num, (ret_numtuple(1)).name;

The fix is to add "." to the SQLSYM rule in the lexer.  This should be OK
because an identifier chain will always be longer than a single dot, so flex
will prefer it over parsing the single dot.

Patch by Peter Eisentraut

Modified Files:
--------------
    plproxy/expected:
        plproxy_select.out (r1.3 -> r1.4)
        (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/plproxy/plproxy/expected/plproxy_select.out?r1=1.3&r2=1.4)
    plproxy/sql:
        plproxy_select.sql (r1.2 -> r1.3)
        (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/plproxy/plproxy/sql/plproxy_select.sql?r1=1.2&r2=1.3)
    plproxy/src:
        scanner.l (r1.14 -> r1.15)
        (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/plproxy/plproxy/src/scanner.l?r1=1.14&r2=1.15)

pgsql-committers by date

Next:From: User AndrewsnDate: 2009-06-29 15:17:54
Subject: ip4r - ip4r: changes for 8.4 gist interface mods
Previous:From: User MkzDate: 2009-06-29 13:32:29
Subject: plproxy - plproxy: Avoid parsing "SELECT (" as function call Currently

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group