Evgenij Ryazanov

Normal standard command looks like ```SQL ALTER TABLE student ALTER COLUMN id SET GENERATED BY DEFAULT; ``` But H2 has a bug with primary key columns (#3859), it will be...

Compatibility mode can be changed on the fly with [`SET MODE`](https://h2database.com/html/commands.html#set_mode) command. Current compatibility mode can be retrieved with ```SQL SELECT SETTING_VALUE FROM INFORMATION_SCHEMA.SETTINGS WHERE SETTING_NAME = 'MODE'; ```

Original URL with settings may not be exposed as is, because it can contain passwords or possibly other sensitive information.

Unfortunately, people who approve vulnerability reports don't use common sense these days and such change is a very likely candidate for a brand new report. And H2 is a different...

Unfortunately, JDBC metadata is an entirely unreliable source of information. It isn't described in JDBC Specification and incompatible, incomplete and missing implementations in different drivers are common enough. As you...

`java.sql.ResultSet.getLong(String)` defines its parameters in the following way: > the label for the column specified with the SQL AS clause. If the SQL AS clause was not specified, then the...

@lukaseder Thanks for opinion. From my point of view: 1. If there is an alias in the list of select expressions (`SELECT columnName columnAlias …`), only `columnAlias` should work. 2....

@grandinj Is it OK to completely remove `tableName.columnName` (`LINK.ID`) support from `ResultSet` when table has an alias and can't be referenced by own name from SQL?

Additional accepted variant of parameters isn't documented anywhere and from my point of view shouldn't be considered as a feature; but this variant will be preserved for queries without table...

There is a bug in `Alias` and `Format`: they don't implement `getSchemaName()` and return `null` instead of it. Our compatibility settings also create a mess, as always. We have `aliasColumnName`...