Bump h2 from 1.4.196 to 2.0.206

[dependabot]

Bumps h2 from 1.4.196 to 2.0.206.

Release notes

Sourced from h2's releases.

Version 2.0.206

Critical security issue with H2 console is fixed.

Also important changes included:

Version 2.0.204

Multilple regression fixes discovered after 2.0.202 release,

There are no persistence changes between 2.0.202 and 2.0.204, so jar file swap is enough, if database had been upgraded to 2.0.202 already, otherwise please read the message below:

Between version 1.4.200 and version 2.0.202 there have been considerable changes, such that a simple update is not possible. The official way to upgrade is to do a BACKUP of your existing database USING YOUR CURRENT VERSION OF H2. Then create a fresh database USING THE NEW VERSION OF H2, then perform a SCRIPT to load your data.

Version 2.0.202

Besides many dozens of fixed bugs, performance improvements, more adherence to a standard SQL syntax and type system, there are

Some new features:

• Complete re-work of INFORMATION_SCHEMA to be more in-line with the standard
• Support for new types: ARRAY, ROW, JAVA_OBJECT
• Numerous bit, string, array and system functions implemented
• Standard-based access to generated keys
• JDBC 4.2 compliance
• Support for JDK 7 is dropped
• PageStore is discontinued

MVStore changes:

• Descending MVMap and TransactionMap cursor
• Disk space reclamation algorithm improvements

Between version 1.4.200 and version 2.0.202 there have been considerable changes, such that a simple update is not possible. The official way to upgrade is to do a BACKUP of your existing database USING YOUR CURRENT VERSION OF H2. Then create a fresh database USING THE NEW VERSION OF H2, then perform a SCRIPT to load your data.

Version 1.4.200

Some new features:

• JSON data type; JSON_OBJECT, JSON_ARRAY, JSON_OBJECTAGG, and JSON_ARRAYAGG functions; JSON predicate
• TIME WITH TIME ZONE data type
• BITNOT, LSHIFT, and RSHIFT functions

... (truncated)

Commits

• 3d957a0 Release 2.0.206 preparation
• 2b6e303 Update changelog
• b24aa46 Check URL scheme
• 4a2e677 Get data types directly from linked tables from H2
• 69aff24 Fix ValueVarcharIgnoreCase.equals()
• 0ebf142 Fix group-sorted optimization for data types with different equal values
• 8aca5f4 Correct Date and Time part in tutorial.html
• 4bfd6f0 Add support of H2 2.0+ to source.html and sourceError.html
• 927c830 Update copyright years
• abac6c8 Next development version
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

[paulhoadley]

Looks like this is not going to be a drop-in replacement. Issues so far:

1. key is apparently a reserved word in 2.0.x, not in 1.4.x. Fine, but if you've got an attribute key anywhere (not reserved by PostgreSQL, for example), migrations will fail.
2. There seems to be an issue in _H2PlugIn.newPrimaryKeys():

2022-01-07 03:54:24.605 INFO  er.transaction.adaptor.Exceptions - Database Exception occured: Column "SEQUENCE_NAME" not found; SQL statement:
select SEQUENCE_NAME, COLUMN_DEFAULT from INFORMATION_SCHEMA.COLUMNS where UPPER(TABLE_NAME) = 'LS_AUDITTRAIL' and UPPER(COLUMN_NAME) = 'ID' [42122-206]at org.h2.message.DbException.getJdbcSQLException(DbException.java:521)

Item 2 is the killer. Indeed, there is a "new version of INFORMATION_SCHEMA for H2 2.0", and it doesn't contain SEQUENCE_NAME.

[paulhoadley]

On balance, I don't think this change is worth pursuing. Our use case for H2PlugIn.framework is isolated functional testing during CI, for example, for which 1.4.x is perfectly adequate. If someone is deploying H2 in production somewhere, they might be able to make a case for the work on _H2PlugIn that would be required. But this specific PR can be closed—it breaks H2PlugIn.

[paulhoadley]

As a bonus, the failure above seems to be intermittent. I now cannot reproduce it. If you do make it to the code path in the catch block in that method, it will definitely fail—as seen above. So it needs fixing, but I can't currently work out how to reliably trigger it.

[dependabot]

Superseded by #974.