Re: Parser extensions (maybe for 10?) - Mailing list pgsql-hackers

From Tsunakawa, Takayuki
Subject Re: Parser extensions (maybe for 10?)
Date
Msg-id 0A3221C70F24FB45833433255569204D1F54C336@G01JPEXMBYT05
Whole thread Raw
In response to Parser extensions (maybe for 10?)  (Arcadiy Ivanov <arcadiy@gmail.com>)
Responses Re: Parser extensions (maybe for 10?)
List pgsql-hackers
<div class="WordSection1"><p class="MsoNormal"><b><font color="black" face="Tahoma" size="2"><span lang="EN-US"
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext;font-weight:bold">From:</span></font></b><font
color="black"face="Tahoma" size="2"><span lang="EN-US"
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">pgsql-hackers-owner@postgresql.org
[mailto:pgsql-hackers-owner@postgresql.org]<b> <span style="font-weight:bold">On Behalf Of </span></b>Arcadiy Ivanov<br
/><br/></span></font><p class="MsoNormal" style="margin-left:5.25pt"><font color="black" face="Verdana" size="3"><span
lang="EN-US"style="font-size:12.0pt;font-family:"Verdana","sans-serif"">Currently the parser and lexer are fully fixed
atcompile-time and not amenable to the extensions - extensions are only capable of introducing functions etc. <br /><br
/>There is, however, an advantage to being able if not add or alter complete statements (which would be nice), but to
atleast augment portions of syntax for existing ones in some places. <br /><br /></span></font><span
lang="EN-US"></span><pclass="MsoNormal"><font color="#1f497d" face="Arial" size="2"><span lang="EN-US"
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D"> </span></font><pclass="MsoNormal"><font
color="#1f497d"face="Arial" size="2"><span lang="EN-US"
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D">Isaw the following discussion in the past, but
Ihaven’t read it:</span></font><p class="MsoNormal"><font color="#1f497d" face="Arial" size="2"><span lang="EN-US"
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D"> </span></font><pclass="MsoNormal"><font
color="#1f497d"face="Arial" size="2"><span lang="EN-US"
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D">PluggableParser</span></font><p
class="MsoNormal"><fontcolor="#1f497d" face="Arial" size="2"><span lang="EN-US"
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D">http://www.postgresql.org/message-id/BF2827DCCE55594C8D7A8F7FFD3AB77159878C2A@szxeml521-mbs.china.huawei.com</span></font><p
class="MsoNormal"><fontcolor="#1f497d" face="Arial" size="2"><span lang="EN-US"
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D"> </span></font><pclass="MsoNormal"><font
color="#1f497d"face="Arial" size="2"><span lang="EN-US"
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D">I’minterested in the pluggable, extensible
parserfor two purposes.  One is to add compatibility for other databases.</span></font><p class="MsoNormal"><font
color="#1f497d"face="Arial" size="2"><span lang="EN-US"
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D"> </span></font><pclass="MsoNormal"><font
color="#1f497d"face="Arial" size="2"><span lang="EN-US"
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D">Theother is for the ODBC (and possibly JDBC)
driver.</span></font><pclass="MsoNormal"><font color="#1f497d" face="Arial" size="2"><span lang="EN-US"
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D">TheODBC/JDBC specs require some unique syntax
constructs,e.g. {? = call funcname(arguments)} to call stored procs/functions.  Currently, the ODBC/JDBC drivers are
forcedto parse and convert SQL statements.  It is ideal for PostgreSQL itself to understand the ODBC/JDBC syntax, and
eliminatethe burdon of parsing statements from the JDBC/ODBC drivers.</span></font><p class="MsoNormal"><font
color="#1f497d"face="Arial" size="2"><span lang="EN-US"
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D"> </span></font><pclass="MsoNormal"><font
color="#1f497d"face="Arial" size="2"><span lang="EN-US"
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D">Regards</span></font><pclass="MsoNormal"><font
color="#1f497d"face="Arial" size="2"><span lang="EN-US"
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D">TakayukiTsunakawa</span></font><p
class="MsoNormal"><fontcolor="#1f497d" face="Arial" size="2"><span lang="EN-US"
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D"> </span></font><pclass="MsoNormal"><font
color="#1f497d"face="Arial" size="2"><span lang="EN-US"
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D"> </span></font><pclass="MsoNormal"><font
color="#1f497d"face="Arial" size="2"><span lang="EN-US"
style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D"> </span></font><pre><fontcolor="black" face="MS
ゴシック"size="3"><span lang="EN-US" style="font-size:12.0pt"> </span></font></pre></div> 

pgsql-hackers by date:

Previous
From: Craig Ringer
Date:
Subject: Re: Parser extensions (maybe for 10?)
Next
From: Andres Freund
Date:
Subject: Re: [COMMITTERS] pgsql: Allow Pin/UnpinBuffer to operate in a lockfree manner.