Stefan Halfpap

Thanks for pointing this out. Yes, the nullptr ckeck is fixed. I will add the proposed column definitions and then close this issue.

Yes, ```NOT``` should and is already supported in front of any expression as unary operator. However, ```ILIKE``` requires a value/attribute before and pattern after, and is, thus handled separately in...

@JoyBinY A simple fix (which is, however, not 100% correct) is changing -insert_statement : INSERT INTO table_name opt_column_list VALUES '(' literal_list ')' { +insert_statement : INSERT INTO table_name opt_column_list VALUES...

My first thought was option 1. Somehow, I discovered that inserts should support expressions, e.g., `insert into t values(1-(5*3), True OR False);`. That is why, I think we could maybe...

Full SQL-92 INSERT support is complex (see, e.g., [http://www.contrib.andrew.cmu.edu/~shadow/sql/sql1992.txt](http://www.contrib.andrew.cmu.edu/~shadow/sql/sql1992.txt), for full draft). I would be happy with a simple version of expressions and could maybe spend some time for a...

I recently saw that we do not use lower() on query strings. This is currently no issue, because query strings are generated with lower cases using the tpch/ds-kit. However, uppercase...