No description provided.
Bumps [h2](https://github.com/h2database/h2database) from 1.3.174 to 2.0.206. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/h2database/h2database/releases">h2's releases</a>.</em></p> <blockquote> <h2>Version 2.0.206</h2> <p>Critical <a href="https://github.com/h2database/h2database/security/advisories/GHSA-h376-j262-vhq6">security issue</a> with H2 console is fixed.</p> <p>Also important changes included:</p> <!-- raw HTML omitted --> <h2>Version 2.0.204</h2> <p>Multilple regression fixes discovered after 2.0.202 release,</p> <p>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:</p> <p>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 <strong>USING YOUR CURRENT VERSION OF H2.</strong> Then create a fresh database <strong>USING THE NEW VERSION OF H2</strong>, then perform a SCRIPT to load your data.</p> <h2>Version 2.0.202</h2> <p>Besides many dozens of fixed bugs, performance improvements, more adherence to a standard SQL syntax and type system, there are</p> <p>Some new features:</p> <ul> <li>Complete re-work of INFORMATION_SCHEMA to be more in-line with the standard</li> <li>Support for new types: ARRAY, ROW, JAVA_OBJECT</li> <li>Numerous bit, string, array and system functions implemented</li> <li>Standard-based access to generated keys</li> <li>JDBC 4.2 compliance</li> <li>Support for JDK 7 is dropped</li> <li>PageStore is discontinued</li> </ul> <p>MVStore changes:</p> <ul> <li>Descending MVMap and TransactionMap cursor</li> <li>Disk space reclamation algorithm improvements</li> </ul> <p>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 <strong>USING YOUR CURRENT VERSION OF H2.</strong> Then create a fresh database <strong>USING THE NEW VERSION OF H2</strong>, then perform a SCRIPT to load your data.</p> <h2>Version 1.4.200</h2> <p>Some new features:</p> <ul> <li>JSON data type; JSON_OBJECT, JSON_ARRAY, JSON_OBJECTAGG, and JSON_ARRAYAGG functions; JSON predicate</li> <li>TIME WITH TIME ZONE data type</li> <li>BITNOT, LSHIFT, and RSHIFT functions</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/h2database/h2database/commits/version-2.0.206">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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](https://github.com/dumptruckman/PluginBase/network/alerts). </details>
This issue appears to be discussing a feature request or bug report related to the repository. Based on the content, it seems to be resolved. The issue was opened by dependabot[bot] and has received 1 comments.