Thank you for your reply ! The problem with "If you would like to write something that turns the output of that parser into a syntax tree in your preferred format, go ahead. Should be interesting." is that it's duplicated work that can/will go out of sync with sqlite repository.
For the concern that you raise about been a feature not useful for general use cases I agree with you and also point that probably there is already features that are not useful for general use cases. One way to solve this is to hide those features behind a preprocessor macro like SQLITE_USEFUL_EXTRA_API this way we can have small code size when minimal features are desired. The potential for automation/validation would be a lot easier with such a feature !? Cheers ! > Mon Jan 18 2016 1:38:52 pm CET CET from "Simon Slavin" ><slavins at bigfraud.org> Subject: Re: [sqlite] Wish list: allow developers >use >the power ofsqliteparser > > On 18 Jan 2016, at 11:51am, Domingo Alvarez Duarte ><sqlite-mail at dev.dadbiz.es> wrote: > > >>The idea is to have a way to get a syntax tree of a sql string through the >> sqlite parser: synatx_tree sqlite3_sql_syntax_tree(const char *zSql); >> >> > The vast majority of copies of SQLite don't run on normal computers, >they're embedded inside mobile phones, TV recorders, SatNav devices, etc.. So >there would be no point in SQLite having the feature you requested as part of >the standard installation of SQLite. > > SQLite uses the Lemon parser to parse the SQL statement. Details on it can >be found here: > > <http://www.hwaci.com/sw/lemon/> > > If you would like to write something that turns the output of that parser >into a syntax tree in your preferred format, go ahead. Should be interesting. > _______________________________________________ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > > > ?
