Hi Aleksandar, Luigi is working on it (using JavaCC). This is the branch: https://github.com/orientechnologies/orientdb/tree/javacc_parser
Our plan are to provide new parser syntax checking and optimizer in 2.1 (we're at good point), then provide new engine for 3.0. Lvc@ On 6 January 2015 at 04:50, Aleksandar Vidakovic <[email protected]> wrote: > Hi, > > ... does someone know if there is still any intention to implement an > ANTLR based SQL parser for OrientDB? > > I found an old thread ( > https://groups.google.com/forum/#!newtopic/orient-database/orient-database/eP3h0HsI2C0) > and there is a (abandoned?) branch on Github ( > https://github.com/orientechnologies/orientdb/blob/antlrparser)... > > I am just asking, because I tinkered around with OrientDB's SQL/command > parts (not knowing that there was already a previous effort) and created a > little proof of concept. The parser is just enough for a basic select > statement; I re-implemented OCommandExecutorSQLSelect without any calls to > the manual parser methods ("parseXXX"). Just wanted to see how much the > code reduction would be while still maintaining the same API. It's 15% less > for that class. > > Please correct if I am missing something... wouldn't it be nicer to > maintain the ANTLR grammar instead of the manual parser implementation? > Would there be demand/interest for such an implementation? > > My minimal example can be found here: > > https://github.com/vidakovic/orientdb-parser > > Cheers > > -- > > --- > You received this message because you are subscribed to the Google Groups > "OrientDB" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
