Bump h2 from 1.3.171 to 2.0.202

[dependabot]

Bumps h2 from 1.3.171 to 2.0.202.

Release notes

Sourced from h2's releases.

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
• Named columns join (JOIN USING)
• Type predicate (IS OF)
• General logarithm function LOG(base, argument)
• UNKNOWN literal and truth value tests
• UNIQUE predicate
• CURRENT_SCHEMA and CURRENT_CATALOG functions
• Data change delta tables (OLD | NEW | FINAL TABLE)
• CURRENT VALUE FOR sequence
• EXECUTE IMMEDIATE command and QUOTE_IDENT function
• Time zone specification (AT TIME ZONE | LOCAL)
• ALTER TABLE tableName ALTER COLUMN IF EXISTS columnName
• READ UNCOMMITTED, REPEATABLE READ, and SNAPSHOT isolation levels with MVStore engine

Incompatible changes:

• MVCC setting (ignored since 1.4.198) now results in error
• MULTI_THREADED setting is removed, MVStore engine is always multi-threaded, PageStore engine is always single-threaded
• Statement.getGeneratedKeys() uses a FINAL TABLE semantics
• Proleptic Gregorian calendar is used as required by the Standard
• Cast from TIME to TIMESTAMP uses CURRENT_DATE for a date part as required by the Standard

Other changes:

... (truncated)

Commits

• See full diff 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.

[tfr42]

IT fails with:

[ERROR] Tests run: 7, Failures: 0, Errors: 7, Skipped: 0, Time elapsed: 2.967 s <<< FAILURE! - in org.deegree.feature.persistence.memory.MemoryFeatureStoreTest

[ERROR] testQueryAllCountries(org.deegree.feature.persistence.memory.MemoryFeatureStoreTest)  Time elapsed: 1.806 s  <<< ERROR!

org.deegree.feature.persistence.FeatureStoreException: 

Could not initialize H2 feature locking database: Table "LOCKS" not found; SQL statement:

CREATE TABLE LOCKED_FIDS (LOCK_ID INT REFERENCES LOCKS,FID VARCHAR(255) NOT NULL UNIQUE) [42102-202].

	at org.deegree.feature.persistence.memory.MemoryFeatureStoreTest.setUp(MemoryFeatureStoreTest.java:116)

Caused by: org.h2.jdbc.JdbcSQLSyntaxErrorException: 

Table "LOCKS" not found; SQL statement:

CREATE TABLE LOCKED_FIDS (LOCK_ID INT REFERENCES LOCKS,FID VARCHAR(255) NOT NULL UNIQUE) [42102-202]

	at org.deegree.feature.persistence.memory.MemoryFeatureStoreTest.setUp(MemoryFeatureStoreTest.java:116)


[ERROR] testQueryAllPlaces(org.deegree.feature.persistence.memory.MemoryFeatureStoreTest)  Time elapsed: 0.243 s  <<< ERROR!

org.deegree.feature.persistence.FeatureStoreException: 

Could not initialize H2 feature locking database: Table "LOCKS" not found; SQL statement:

CREATE TABLE LOCKED_FIDS (LOCK_ID INT REFERENCES LOCKS,FID VARCHAR(255) NOT NULL UNIQUE) [42102-202].

	at org.deegree.feature.persistence.memory.MemoryFeatureStoreTest.setUp(MemoryFeatureStoreTest.java:116)

Caused by: org.h2.jdbc.JdbcSQLSyntaxErrorException: 

Table "LOCKS" not found; SQL statement:

CREATE TABLE LOCKED_FIDS (LOCK_ID INT REFERENCES LOCKS,FID VARCHAR(255) NOT NULL UNIQUE) [42102-202]

	at org.deegree.feature.persistence.memory.MemoryFeatureStoreTest.setUp(MemoryFeatureStoreTest.java:116)


[ERROR] testQueryAllPhilosophers(org.deegree.feature.persistence.memory.MemoryFeatureStoreTest)  Time elapsed: 0.19 s  <<< ERROR!

org.deegree.feature.persistence.FeatureStoreException: 

Could not initialize H2 feature locking database: Table "LOCKS" not found; SQL statement:

CREATE TABLE LOCKED_FIDS (LOCK_ID INT REFERENCES LOCKS,FID VARCHAR(255) NOT NULL UNIQUE) [42102-202].

	at org.deegree.feature.persistence.memory.MemoryFeatureStoreTest.setUp(MemoryFeatureStoreTest.java:116)

Caused by: org.h2.jdbc.JdbcSQLSyntaxErrorException: 

Table "LOCKS" not found; SQL statement:

CREATE TABLE LOCKED_FIDS (LOCK_ID INT REFERENCES LOCKS,FID VARCHAR(255) NOT NULL UNIQUE) [42102-202]

	at org.deegree.feature.persistence.memory.MemoryFeatureStoreTest.setUp(MemoryFeatureStoreTest.java:116)


[ERROR] testGetObjectByIdGeometry1(org.deegree.feature.persistence.memory.MemoryFeatureStoreTest)  Time elapsed: 0.183 s  <<< ERROR!

org.deegree.feature.persistence.FeatureStoreException: 

Could not initialize H2 feature locking database: Table "LOCKS" not found; SQL statement:

CREATE TABLE LOCKED_FIDS (LOCK_ID INT REFERENCES LOCKS,FID VARCHAR(255) NOT NULL UNIQUE) [42102-202].

	at org.deegree.feature.persistence.memory.MemoryFeatureStoreTest.setUp(MemoryFeatureStoreTest.java:116)

Caused by: org.h2.jdbc.JdbcSQLSyntaxErrorException: 

Table "LOCKS" not found; SQL statement:

CREATE TABLE LOCKED_FIDS (LOCK_ID INT REFERENCES LOCKS,FID VARCHAR(255) NOT NULL UNIQUE) [42102-202]

	at org.deegree.feature.persistence.memory.MemoryFeatureStoreTest.setUp(MemoryFeatureStoreTest.java:116)


[ERROR] testGetObjectByIdGeometry2(org.deegree.feature.persistence.memory.MemoryFeatureStoreTest)  Time elapsed: 0.202 s  <<< ERROR!

org.deegree.feature.persistence.FeatureStoreException: 

Could not initialize H2 feature locking database: Table "LOCKS" not found; SQL statement:

CREATE TABLE LOCKED_FIDS (LOCK_ID INT REFERENCES LOCKS,FID VARCHAR(255) NOT NULL UNIQUE) [42102-202].

	at org.deegree.feature.persistence.memory.MemoryFeatureStoreTest.setUp(MemoryFeatureStoreTest.java:116)

Caused by: org.h2.jdbc.JdbcSQLSyntaxErrorException: 

Table "LOCKS" not found; SQL statement:

CREATE TABLE LOCKED_FIDS (LOCK_ID INT REFERENCES LOCKS,FID VARCHAR(255) NOT NULL UNIQUE) [42102-202]

	at org.deegree.feature.persistence.memory.MemoryFeatureStoreTest.setUp(MemoryFeatureStoreTest.java:116)


[ERROR] testQueryPhilosopherById(org.deegree.feature.persistence.memory.MemoryFeatureStoreTest)  Time elapsed: 0.155 s  <<< ERROR!

org.deegree.feature.persistence.FeatureStoreException: 

Could not initialize H2 feature locking database: Table "LOCKS" not found; SQL statement:

CREATE TABLE LOCKED_FIDS (LOCK_ID INT REFERENCES LOCKS,FID VARCHAR(255) NOT NULL UNIQUE) [42102-202].

	at org.deegree.feature.persistence.memory.MemoryFeatureStoreTest.setUp(MemoryFeatureStoreTest.java:116)

Caused by: org.h2.jdbc.JdbcSQLSyntaxErrorException: 

Table "LOCKS" not found; SQL statement:

CREATE TABLE LOCKED_FIDS (LOCK_ID INT REFERENCES LOCKS,FID VARCHAR(255) NOT NULL UNIQUE) [42102-202]

	at org.deegree.feature.persistence.memory.MemoryFeatureStoreTest.setUp(MemoryFeatureStoreTest.java:116)


[ERROR] testGetObjectByIdFeature(org.deegree.feature.persistence.memory.MemoryFeatureStoreTest)  Time elapsed: 0.154 s  <<< ERROR!

org.deegree.feature.persistence.FeatureStoreException: 

Could not initialize H2 feature locking database: Table "LOCKS" not found; SQL statement:

CREATE TABLE LOCKED_FIDS (LOCK_ID INT REFERENCES LOCKS,FID VARCHAR(255) NOT NULL UNIQUE) [42102-202].

	at org.deegree.feature.persistence.memory.MemoryFeatureStoreTest.setUp(MemoryFeatureStoreTest.java:116)

Caused by: org.h2.jdbc.JdbcSQLSyntaxErrorException: 

Table "LOCKS" not found; SQL statement:

CREATE TABLE LOCKED_FIDS (LOCK_ID INT REFERENCES LOCKS,FID VARCHAR(255) NOT NULL UNIQUE) [42102-202]

	at org.deegree.feature.persistence.memory.MemoryFeatureStoreTest.setUp(MemoryFeatureStoreTest.java:116)

[tfr42]

@dependabot rebase

[dependabot]

Looks like this PR is already up-to-date with master! If you'd still like to recreate it from scratch, overwriting any edits, you can request @dependabot recreate.

[dependabot]

Superseded by #1264.