Provides Standalone Mode implementations of hsqldb and apache/derby

[linghengqian]

Feature Request

For English only, other languages will not be accepted.

Please pay attention on issues you submitted, because we maybe need more details.
If no response anymore and we cannot make decision by current information, we will close it.

Please answer these questions before submitting your issue. Thanks!

Is your feature request related to a problem?

• Yes. The current issue is a wrap-up of shardingsphere H2database snyk issue #30656.

Describe the feature you would like.

• Provides Standalone Mode implementations of hsqldb and apache/derby. Just like com.h2database:h2. This involves testing three JDBC Drivers in org.apache.shardingsphere:shardingsphere-standalone-mode-repository-jdbc.

  • org.apache.derby.jdbc.EmbeddedDriver/org.apache.derby:derby
  • In order to use apache/derby in client/server mode, we may need to additionally implement the relevant xml of org.apache.derby.jdbc.ClientDriver. This requires org.apache.derby:derbyclient.
  • org.hsqldb.jdbc.JDBCDriver/org.hsqldb:hsqldb

• This actually alleviates somewhat the argument in fix(shardingsphere-standalone-mode-repository-provider): Load database driver from configuration file. #30835 that the so-called h2database driver class name may become obsolete in the future. And the so-called avoidance of the need to use h2database on shardingsphere jdbc without introducing third-party database middleware.

[linghengqian]

• I'm working on the current issue.

[github-actions]

There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale.