2 MySQL supports linked MySQL tables under the name ‘federated tables’. 3 Connection.execute 1c support for roles based security and password checking as an option.
4 Derby only supports global temporary tables. 5 The default H2 jar file contains debug information, jar files for other databases do not. 7 Derby only supports updatable result sets if the query is not sorted. 8 Derby doesn’t support standard compliant information schema tables. 10 Derby and HSQLDB don’t hide data patterns well. 11 The MULTI_THREADED option is not enabled by default, and with version 1. 12 Derby doesn’t support the EXPLAIN statement, but it supports runtime statistics and retrieving statement execution plans.
13 Derby doesn’t support the syntax LIMIT . This is the fastest and easiest connection mode. As in all modes, both persistent and in-memory databases are supported. There is no limit on the number of database open concurrently, or on the number of open connections. This is achieved using different database URLs. Settings in the URLs are not case sensitive. If no or only a relative path is used, then the current working directory is used as a starting point.
This database supports the in-memory mode, where the data is not persisted. In some cases, only one connection to a in-memory database is required. This means the database to be opened is private. Sometimes multiple connections to the same in-memory database are required.
In this case, the database URL must include a name. Accessing the same database using this URL only works within the same virtual machine and class loader environment. By default, closing the last connection to a database closes the database. For an in-memory database, this means the content is lost. XTEA” – the 32 round version.