Evgenij Ryazanov

> @katzyn is there something similar like in SQL SERVER `SELECT @@IDENTITY` for H2 2.1.210? It depends on compatibility mode of H2, in some modes there are various vendor-specific functions,...

> I'am currently using SQL Server compatibility mode. Do you know is there something what i can use for workaround, a function or select? ```SQL SELECT SCOPE_IDENTITY(); ``` (It works...

It happened again in the current `master`.

This check is absolutely necessary to avoid a security flaw, it prevents injection of malicious code. About the initial issue with CCE: 1.4.200 is an old unsupported version of H2...

Recursive CTEs are experimental in H2 according to documentation. De-facto non-recursive CTEs also have defective by design implementation and fixes for some edge cases sometimes produce new regressions. This particular...

I think H2 may require them according to the Standard. 7.17 ``, Syntax Rules: ``` j) If WC is potentially recursive, then: i) Every contained in WC shall contain a...

It is definitely simpler to require them for the parser and query compiler, but I have no idea are there other reasons or it was the only reason to include...

1. Non-standard `CREATE TABLE MYTEST(BLA VARCHAR(2000), BLUBB VARCHAR(2000)) AS …` 2. Standard-compliant `CREATE TABLE MYTEST AS SELECT CAST('' AS VARCHAR(2000)) BLA, …`

According to the ISO/IEC 9075-2:2016(E), section 4.5.2 “Comparison and assignment of booleans” boolean values are comparable with boolean values. You shouldn't assume that comparison with other data types can be...

H2 allows comparison between boolean and numeric values in `MSSQLServer` compatibility mode, so `1` and `0` can be used in this mode instead of standard `TRUE` and `FALSE` literals. https://h2database.com/html/features.html#compatibility...