Re: Do not use H2 parser for DDL

2017-02-03 Thread Sergi Vladykin
Nope, but we can add this to H2 to make it compatible with Oracle [1] and/or PostgreSQL [2]. [1] https://logicalread.com/oracle-11g-named-parameters-in-sql-function-calls-mc02 [2] https://www.postgresql.org/docs/9.1/static/sql-syntax-calling-funcs.html Sergi 2017-02-03 17:41 GMT+03:00 Vladimir

Re: Do not use H2 parser for DDL

2017-02-03 Thread Vladimir Ozerov
Sergi, Does H2 support naming for function parameters? E.g. NEW_CACHE(backups: 1, mode: PARTITIONED) On Fri, Feb 3, 2017 at 4:28 PM, Sergi Vladykin wrote: > Actually we do not support FULLTEXT indexes in SQL right now. Thus I think > we will have to postpone this

Re: Do not use H2 parser for DDL

2017-01-29 Thread Dmitriy Setrakyan
On Fri, Jan 27, 2017 at 8:51 PM, Alexander Paschenko < alexander.a.pasche...@gmail.com> wrote: > Guys, > > And what would you say if I suggested that we implement custom grammar > support with ANTLR? It allows you to describe pretty much any grammar > in a declarative way, generates lexer and

Re: Do not use H2 parser for DDL

2017-01-27 Thread Alexander Paschenko
Guys, And what would you say if I suggested that we implement custom grammar support with ANTLR? It allows you to describe pretty much any grammar in a declarative way, generates lexer and parser and then allows to easily process parsed commands by implementing few (generated) interfaces.

Re: Do not use H2 parser for DDL

2017-01-27 Thread Vladimir Ozerov
My point was that we can avoid dependency on 3rd party developers for this relatively simple logic. On Fri, Jan 27, 2017 at 8:07 PM, Dmitriy Setrakyan wrote: > On Fri, Jan 27, 2017 at 5:45 AM, Sergi Vladykin > wrote: > > > H2 to some extent

Re: Do not use H2 parser for DDL

2017-01-27 Thread Dmitriy Setrakyan
On Fri, Jan 27, 2017 at 5:45 AM, Sergi Vladykin wrote: > H2 to some extent supports syntax (and quirks) from other databases. For > example you can start it with MODE=MySQL and it will allow some MySQL > specific syntax to be handled. > > Having said that, IMO the most

Re: Do not use H2 parser for DDL

2017-01-27 Thread Sergi Vladykin
H2 to some extent supports syntax (and quirks) from other databases. For example you can start it with MODE=MySQL and it will allow some MySQL specific syntax to be handled. Having said that, IMO the most correct way to handle non-standard syntax is to introduce H2 MODE=ApacheIgnite and put the

Re: Do not use H2 parser for DDL

2017-01-27 Thread Alexey Kuznetsov
We should care about statements like this: /* bla-bla */ CREATE TABLE So naive "startsWith(...)" will not work in some scenarios. :) On Fri, Jan 27, 2017 at 7:06 PM, Vladimir Ozerov wrote: > Folks, > > H2 has nice and powerful SQL parser, and we pass all incoming SQL

Do not use H2 parser for DDL

2017-01-27 Thread Vladimir Ozerov
Folks, H2 has nice and powerful SQL parser, and we pass all incoming SQL commands through it. However it doesn't support custom SQL syntax, which we are likely to need in DDL at some point in future. As DDL statements are relatively easy to parse comparing to SELECTs and they do not involve