提交 6d50ee90 authored 作者: Thomas Mueller's avatar Thomas Mueller

--no commit message

--no commit message
上级 48ed8c60
......@@ -1127,1087 +1127,1093 @@ Change Log
Next Version (unreleased)
@changelog_1002_li
When using the auto-server mode, and if the lock file was modified in the future, the wrong exception was thrown ('Connection is broken' instead of 'Error opening database: Lock file modified in the future').
@changelog_1003_h2
Version 1.1.105 (2008-12-19)
@changelog_1004_li
The setting STORAGE=TEXT is no longer supported.
@changelog_1003_li
@changelog_1005_li
Deleting a database using the tool DeleteDbFiles deleted LOB files of other databases in the same directory.
@changelog_1004_li
@changelog_1006_li
When used in a subquery, LIKE and IN(..) did not work correctly sometimes.
@changelog_1005_li
@changelog_1007_li
The fulltext search documentation has been improved.
@changelog_1006_li
@changelog_1008_li
ARRAY_GET returned the wrong data type (ARRAY). Now it returns VARCHAR.
@changelog_1007_li
@changelog_1009_li
Natural join: the joined columns are not repeated any more when using SELECT *.
@changelog_1008_li
@changelog_1010_li
User defined aggregate functions: the method getType expected internal data types instead of SQL types.
@changelog_1009_li
@changelog_1011_li
User defined aggregate functions did not work if there was no group by expression.
@changelog_1010_li
@changelog_1012_li
MySQL compatibility: support for := assignment as in @sum:=@sum+x
@changelog_1011_li
@changelog_1013_li
INSERT INTO TEST(SELECT * FROM TEST) is now supported.
@changelog_1012_li
@changelog_1014_li
Each session threw an invisible exception when garbage collected.
@changelog_1013_li
@changelog_1015_li
Foreign key constraints that refer to a quoted column did not work.
@changelog_1014_li
@changelog_1016_li
New meta data column INFORMATION_SCHEMA.TABLES.LAST_MODIFICATION to get the table modification counter.
@changelog_1015_li
@changelog_1017_li
Shell: line comments didn't work correctly.
@changelog_1016_li
@changelog_1018_li
H2 Console: Columns are now listed for up to 500 tables instead of 100.
@changelog_1017_li
@changelog_1019_li
H2 Console: Cmd+Enter executes the current statement, Alt+Space for autocomplete.
@changelog_1018_li
@changelog_1020_li
JaQu: the maximum length of a column can now be defined using maxLength. For an example, see Product.java (maxLength(category, 255)).
@changelog_1019_li
@changelog_1021_li
R&\#305;dvan A&\#287;ar has completed the Turkish translation of the H2 Console. Thanks a lot!
@changelog_1020_h2
@changelog_1022_h2
Version 1.1.104 (2008-11-28)
@changelog_1021_li
@changelog_1023_li
If a query that was used like a table contained group by and was ordered by an expression that is not in the column list, an exception was thrown.
@changelog_1022_li
@changelog_1024_li
JaQu: tables are now auto-created when running a query.
@changelog_1023_li
@changelog_1025_li
The optimizer had problems with function tables (for example CSVREAD and FTL_SEARCH). A new system property h2.estimatedFunctionTableRows (default 1000) defines how many rows can be expected in the table.
@changelog_1024_li
@changelog_1026_li
The function SUM could overflow when using large values. It returns now a data type that is safe.
@changelog_1025_li
@changelog_1027_li
The function AVG could overflow when using large values. Fixed.
@changelog_1026_li
@changelog_1028_li
The emergency reserve file has been removed. It didn't provide an appropriate solution for the problem. It is still possible for an application to detect and deal with the low disk space problem (deleting temporary files for example) using DatabaseEventListener.diskSpaceIsLow, but this method is now always called with stillAvailable=0.
@changelog_1027_li
@changelog_1029_li
Build: JAVA_HOME is now automatically detected on Mac OS X.
@changelog_1028_li
@changelog_1030_li
Testing for local connections was very slow on some systems.
@changelog_1029_li
@changelog_1031_li
The cache memory usage calculation is more conservative.
@changelog_1030_li
@changelog_1032_li
Allocating space got slower and slower the larger the database.
@changelog_1031_li
@changelog_1033_li
ALTER TABLE ALTER COLUMN could throw the wrong exception in the last version (Table not found).
@changelog_1032_li
@changelog_1034_li
Updatable result sets: the key columns can now be updated.
@changelog_1033_li
@changelog_1035_li
The H2DatabaseProvider for ActiveObjects is now included in the tools section.
@changelog_1034_li
@changelog_1036_li
The H2Platform for Oracle Toplink Essential has been improved a bit.
@changelog_1035_li
@changelog_1037_li
The Windows service to start H2 didn't work in version 1.1.
@changelog_1036_li
@changelog_1038_li
File systems with a maximum file size (for example FAT) are now supported using the file prefix 'split:'. In this case the files are split in parts of 1 GB. Example URL: jdbc:h2:split:~/db/test. If you want to split into parts of 1 MB, use jdbc:h2:split:20:~/db/test (the part size is 1 << x, the default is 30 meaning 1 GB).
@changelog_1037_li
@changelog_1039_li
The database now tries to detect if the classloader or virtual machine has almost shut down by checking if static final variables are set to null. This should help reduce exceptions when stopping the web application.
@changelog_1038_li
@changelog_1040_li
Compatibility for MS SQL Server DATEDIFF(YYYY, .., ..)
@changelog_1039_li
@changelog_1041_li
ResultSet.getObject for CLOB or BLOB will return a java.sql.Clob / java.sql.Blob object instead of a java.io.Reader / java.io.InputStream as in version 1.0. This behavior can be changed using the system property h2.returnLobObjects (true by default for version 1.1).
@changelog_1040_li
@changelog_1042_li
The interface CloseListener has a new method 'remove' that is called when the trigger is dropped.
@changelog_1041_li
@changelog_1043_li
Fulltext search: there was a memory leak when creating and dropping fulltext indexes in a loop.
@changelog_1042_h2
@changelog_1044_h2
Version 1.1.103 (2008-11-07)
@changelog_1043_li
@changelog_1045_li
Could not order by a formula when the formula was in the group by list but not in the select list.
@changelog_1044_li
@changelog_1046_li
Date values that match the daylight saving time end were not allowed in times zones were the daylight saving time ends at midnight, for years larger than 2037. Example: timezone Brasilia, date 2042-10-12. This is a problem of Java, however a workaround is implemented in H2 that solves most problems (except the problems of java.util.Date itself).
@changelog_1045_li
@changelog_1047_li
ALTER TABLE used a lot of memory when using multi-version concurrency.
@changelog_1046_li
@changelog_1048_li
Referential integrity for in-memory databases didn't work in some cases in version 1.1.102.
@changelog_1047_li
@changelog_1049_li
New column INFORMATION_SCHEMA.COLUMNS.SEQUENCE_NAME to get the name of the sequence for auto-increment columns.
@changelog_1048_li
@changelog_1050_li
Aliases for built-in data types (such as MEDIUMBLOB which is an alias for BLOB) can now be re-mapped to another data type using CREATE DOMAIN. However main built-in data types (such as INTEGER) can not be re-mapped.
@changelog_1049_li
@changelog_1051_li
The Japanese translation has been completed by Masahiro Ikemoto. Thanks a lot!
@changelog_1050_li
@changelog_1052_li
Improved PostgreSQL compatibility for NEXTVAL and CURRVAL.
@changelog_1051_li
@changelog_1053_li
Less heap memory is needed when multiple databases are open at the same time: The memory reserve (used to rollback after out of memory) is now global and no longer allocated for each database separately.
@changelog_1052_li
@changelog_1054_li
New system property h2.browser to set the browser to use.
@changelog_1053_li
@changelog_1055_li
To start the browser, java.awt.Desktop.browse is now used if available.
@changelog_1054_h2
@changelog_1056_h2
Version 1.1.102 (2008-10-24)
@changelog_1055_li
@changelog_1057_li
The French translation of the H2 Console has been improved by Olivier Parent. Thanks a lot!
@changelog_1056_li
@changelog_1058_li
There was a memory leak when creating and dropping tables and indexes in a loop (persistent database only).
@changelog_1057_li
@changelog_1059_li
SET LOG 2 was not effective if executed after opening the database.
@changelog_1058_li
@changelog_1060_li
Translating the H2 Console is now simpler.
@changelog_1059_li
@changelog_1061_li
Common exception (error code 23*) are no longer written to the .trace.db file by default.
@changelog_1060_li
@changelog_1062_li
In-memory databases don't write LOBs to files any longer.
@changelog_1061_li
@changelog_1063_li
Self referencing constraints didn't restrict deleting rows that reference itself if there is another row that references it.
@changelog_1062_li
@changelog_1064_li
ResultSetMetaData.getColumnName now returns the alias name except for columns.
@changelog_1063_li
@changelog_1065_li
Temporary files are now deleted when the database is closed, even if they were not garbage collected so far.
@changelog_1064_h2
@changelog_1066_h2
Version 1.1.101 (2008-10-17)
@changelog_1065_li
@changelog_1067_li
Errors with code 42000 - 42999 are no longer written to the trace file by default.
@changelog_1066_li
@changelog_1068_li
Queries with more than 10 tables are now faster.
@changelog_1067_li
@changelog_1069_li
Opening a connection with AUTO_SERVER=TRUE is now fast when the database is already open in another process (less than 0.01 seconds instead of 2 seconds).
@changelog_1068_li
@changelog_1070_li
IF [NOT] EXISTS is supported for named constraints in ALTER TABLE ... ADD/DROP CONSTRAINT.
@changelog_1069_li
@changelog_1071_li
The error messages have been translated to Spanish by Dario V. Fassi. Thanks a lot!
@changelog_1070_li
@changelog_1072_li
Linked tables: the automatic connection sharing didn't work. Actually the system property h2.shareLinkedConnections was working in the opposite direction: it was disabled when set to true. Now it works as expected.
@changelog_1071_li
@changelog_1073_li
Opening large database is now faster.
@changelog_1072_li
@changelog_1074_li
New system property h2.socketConnectTimeout, the timeout in milliseconds to connect to a server. The default is 2000 (2 seconds).
@changelog_1073_li
@changelog_1075_li
The wrong parameters were bound to subqueries with parameters, specially when using IN(SELECT ...) and IN(...).
@changelog_1074_li
@changelog_1076_li
Unset parameters were not detected when the query was re-compiled.
@changelog_1075_li
@changelog_1077_li
New functions ISO_YEAR, ISO_WEEK, ISO_DAY_OF_WEEK. Thanks a lot to Robert Rathsack for implementing those!
@changelog_1076_li
@changelog_1078_li
The date functions DAYOFYEAR, DAYOFMONTH, DAYOFWEEK are now called DAY_OF_YEAR, DAY_OF_MONTH, DAY_OF_WEEK (the old names still work).
@changelog_1077_li
@changelog_1079_li
An out of memory error while deleting or updating many rows could result in a strange exception.
@changelog_1078_li
@changelog_1080_li
Linked tables: compatibility with MS SQL Server has been improved.
@changelog_1079_li
@changelog_1081_li
Renaming tables that have foreign keys with cascade didn't work correctly.
@changelog_1080_li
@changelog_1082_li
The auto-reconnect feature didn't work when using the auto-server mode. Fixed.
@changelog_1081_li
@changelog_1083_li
Fulltext search: new method FT_DROP_INDEX.
@changelog_1082_li
@changelog_1084_li
The optimization to group using an index didn't work in some cases in version 1.1 (see also system property h2.optimizeGroupSorted).
@changelog_1083_li
@changelog_1085_li
OSGi meta data is included in the manifest file. An OSGi BundleActivator is included: it loads the database driver when starting the bundle, and unloads it when stopping the bundle.
@changelog_1084_li
@changelog_1086_li
The default value for MAX_MEMORY_UNDO is now 50000.
@changelog_1085_li
@changelog_1087_li
For alias columns, ResultSetMetaData.getTableName() and getColumnName() now return the real table and column name in the default mode.
@changelog_1086_li
@changelog_1088_li
In SQL scripts created with SCRIPT TO, schemas are now only created if they don't exist yet.
@changelog_1087_li
@changelog_1089_li
After re-connecting to a database, the database event listener (if set) is informed about it.
@changelog_1088_li
@changelog_1090_li
Local temporary tables now support indexes. Thanks a lot to Matt Roy!
@changelog_1089_li
@changelog_1091_li
RUNSCRIPT no longer uses a temporary file.
@changelog_1090_li
@changelog_1092_li
New system table INFORMATION_SCHEMA.SESSION_STATE containing the SQL statements that make up the session state. The list currently contains variables (SET @..) and local temporary tables (without data).
@changelog_1091_li
@changelog_1093_li
After an automatic re-connect, part of the session state stays (the part that is stored in the SESSION_STATE table).
@changelog_1092_li
@changelog_1094_li
The build didn't work if the directory temp didn't exist before.
@changelog_1093_li
@changelog_1095_li
New system property h2.maxReconnect (default 3) to limit the number of re-connects for the same SQL statement (this is usually only important for SHUTDOWN).
@changelog_1094_li
@changelog_1096_li
WHERE .. IN (SELECT ...) could throw a NullPointerException.
@changelog_1095_li
@changelog_1097_li
Improved Glassfish / Toplink support in H2Platform thanks to Marcio Borges from Brazil. Thanks a lot!
@changelog_1096_h2
@changelog_1098_h2
Version 1.1.100 (2008-10-04)
@changelog_1097_li
@changelog_1099_li
In version 1.1, the following system properties are now enabled by default: h2.lobFilesInDirectories, h2.optimizeGroupSorted, h2.optimizeInJoin, h2.shareLinkedConnections
@changelog_1098_li
@changelog_1100_li
The H2 Console tool now works with the JDBC-ODBC bridge.
@changelog_1099_li
@changelog_1101_li
The H2 Console tool now supports command line options to start things separately.
@changelog_1100_li
@changelog_1102_li
Large objects did not work for in-memory databases in server mode in Linux.
@changelog_1101_li
@changelog_1103_li
Connections from a local address other than 'localhost' were not allowed if remote connections were disabled. This was always a problem, but only got visible in the last release because the server no longer connects to 'localhost' if networked.
@changelog_1102_li
@changelog_1104_li
The h2console.war can now be built using the Java build.
@changelog_1103_li
@changelog_1105_li
By default, databases are shared in the same process. For read-only databases this causes unnecessary synchronization, but safes memory. If you want that each connection opens its own database, append ;OPEN_NEW=TRUE to the database URL.
@changelog_1104_li
@changelog_1106_li
New auto-reconnect feature will cause the JDBC driver to reconnect to the database if the connection is lost. To enable, append ;AUTO_RECONNECT=TRUE to the database URL. This is specially helpful when using AUTO_SERVER. AUTO_SERVER automatically uses auto-reconnect.
@changelog_1105_li
@changelog_1107_li
CreateCluster: the property 'serverlist' is now called 'serverList'.
@changelog_1106_li
@changelog_1108_li
The ConvertTraceFile tool could not parse some files because the trace mechanism did not encode prepared statement parameters.
@changelog_1107_li
@changelog_1109_li
Databases names can now be one character long (the minimum size used to be 2 characters).
@changelog_1108_h2
@changelog_1110_h2
Version 1.0.79 (2008-09-26)
@changelog_1109_li
@changelog_1111_li
Linked tables that point to the same database can now share the connection within the same database. Access to the same connection is serialized. To enable this feature, set the system property h2.shareLinkedConnections to true.
@changelog_1110_li
@changelog_1112_li
Multiple processes can now access the same database without having to explicitly start the server. To do that, append ;AUTO_SERVER=TRUE to the database URL. In this case, the server is started automatically if the connection is in embedded mode, and the server mode is used if a server is running. If the process that opened the first connection is closed, the other client need to reconnect (there is no automatic re-connect so far). Remote connections are allowed, but only to this database.
@changelog_1111_li
@changelog_1113_li
The server tool now displays the correct IP address if networked.
@changelog_1112_li
@changelog_1114_li
Can now start a TCP server with port 0 (automatically select a port).
@changelog_1113_li
@changelog_1115_li
Result sets with just a unique index can now be updated (previously a primary key was required).
@changelog_1114_li
@changelog_1116_li
LINKED TABLE: the schema name can now be set. When multiple tables exist in different schema, and the schema name is not set, an exception is thrown.
@changelog_1115_li
@changelog_1117_li
LINKED TABLE: worked around a bug in Oracle with the CHAR data type.
@changelog_1116_li
@changelog_1118_li
Faster hash code calculation for large binary arrays.
@changelog_1117_li
@changelog_1119_li
Faster storage re-use algorithm thanks to Greg Dhuse from cleversafe.com.
@changelog_1118_li
@changelog_1120_li
The database supports the SHOW command for better MySQL and PostgreSQL compatibility.
@changelog_1119_li
@changelog_1121_li
The H2 Console now abbreviates large texts in results.
@changelog_1120_li
@changelog_1122_li
Multiple UNION queries could not be used in derived tables.
@changelog_1121_li
@changelog_1123_li
Linked tables can now be read-only.
@changelog_1122_li
@changelog_1124_li
Temporary linked tables are now supported.
@changelog_1123_li
@changelog_1125_li
It was possible to create tables in read-only databases.
@changelog_1124_li
@changelog_1126_li
SET SCHEMA_SEARCH_PATH is now documented.
@changelog_1125_li
@changelog_1127_li
SET SCHEMA did not work for views.
@changelog_1126_li
@changelog_1128_li
Row level locking for MVCC is now enabled. The exception 'Concurrent update in table ...' is still thrown, but only after the lock timeout.
@changelog_1127_li
@changelog_1129_li
The maximum log file size setting was ignored for large databases.
@changelog_1128_li
@changelog_1130_li
Multi-Version Concurrency (MVCC) may no longer be used when using the multi-threaded kernel feature (MULTI_THREADED). An exception is thrown when trying to connect with both settings. Additional synchronization is required before those features can be used together.
@changelog_1129_li
@changelog_1131_li
The data type JAVA_OBJECT could not be used in updatable result sets.
@changelog_1130_li
@changelog_1132_li
The system property h2.optimizeInJoin did not work correctly.
@changelog_1131_li
@changelog_1133_li
Conditions such as ID=? AND ID>? were slow.
@changelog_1132_h2
@changelog_1134_h2
Version 1.0.78 (2008-08-28)
@changelog_1133_li
@changelog_1135_li
The documentation no longer uses a frameset (except the Javadocs).
@changelog_1134_li
@changelog_1136_li
When using DB_CLOSE_DELAY, sometimes a NullPointerException is thrown when the database is opened almost at the same time as it is closed automatically. Thanks a lot to Dmitry Pekar for finding this!
@changelog_1135_li
@changelog_1137_li
Java methods with variable number of parameters can now be used (for Java 1.5 or newer).
@changelog_1136_li
@changelog_1138_li
The Japanese translation has been improved by Masahiro Ikemoto. Thanks a lot!
@changelog_1137_li
@changelog_1139_li
The H2 Console replaced an empty user name with a single space.
@changelog_1138_li
@changelog_1140_li
The build target 'build jarSmall' now includes the embedded database.
@changelog_1139_li
@changelog_1141_li
JdbcDataSource now keeps the password in a char array where possible.
@changelog_1140_li
@changelog_1142_li
ResultSet.absolute did not always work with large result sets.
@changelog_1141_li
@changelog_1143_li
Column aliases can now be used in GROUP BY and HAVING.
@changelog_1142_li
@changelog_1144_li
Jason Brittain has contributed MySQL date functions. Thanks a lot! They are not in the h2.jar file currently, but in src/tools/org/h2/mode/FunctionsMySQL.java. To install, add this class to the classpath and call FunctionsMySQL.register(conn) in the Java code.
@changelog_1143_h2
@changelog_1145_h2
Version 1.0.77 (2008-08-16)
@changelog_1144_li
@changelog_1146_li
JaQu is now using prepared statements and supports Date, Time, Timestamp.
@changelog_1145_li
@changelog_1147_li
When using remote in-memory databases, large LOB objects did not work.
@changelog_1146_li
@changelog_1148_li
Timestamp columns such as TIMESTAMP(6) were not compatible to other database.
@changelog_1147_li
@changelog_1149_li
Opening a large database was slow if there was a problem opening the previous time.
@changelog_1148_li
@changelog_1150_li
NOT IN(SELECT ...) was incorrect if the subquery returns no rows.
@changelog_1149_li
@changelog_1151_li
CREATE TABLE AS SELECT did not work correctly in the multi-version concurrency mode.
@changelog_1150_li
@changelog_1152_li
Support a comma before closing a list, as in: create table test(id int,)
@changelog_1151_li
@changelog_1153_li
MySQL compatibility: linked tables had lower case column names on some systems.
@changelog_1152_li
@changelog_1154_li
DB2 compatibility: the DB2 fetch-first-clause is supported.
@changelog_1153_li
@changelog_1155_li
Oracle compatibility: old style outer join syntax using (+) did work correctly sometimes.
@changelog_1154_li
@changelog_1156_li
ResultSet.setFetchSize is now supported.
@changelog_1155_li
@changelog_1157_li
It has been reported that when using Install4j on some Linux systems and enabling the 'pack200' option, the h2.jar becomes corrupted by the install process, causing application failure. A workaround is to add an empty file h2.jar.nopack next to the h2.jar file. The reason for this problem is not known.
@changelog_1156_h2
@changelog_1158_h2
Version 1.0.76 (2008-07-27)
@changelog_1157_li
@changelog_1159_li
The comment of a domain (user defined data type) is now used as the default column comment when creating a column with this domain.
@changelog_1158_li
@changelog_1160_li
Invalid database names are now detected and a better error message is thrown.
@changelog_1159_li
@changelog_1161_li
ResultSetMetaData.getColumnClassName now returns the correct class name for BLOB and CLOB.
@changelog_1160_li
@changelog_1162_li
Fixed the Oracle mode: Oracle allows multiple rows only where all columns of the unique index are NULL.
@changelog_1161_li
@changelog_1163_li
There is a problem with Hibernate when using Boolean columns. A patch for Hibernate has been submitted at http://opensource.atlassian.com/projects/hibernate/browse/HHH-3401
@changelog_1162_li
@changelog_1164_li
ORDER BY on tableName.columnName didn't work correctly if the column name was also used as an alias.
@changelog_1163_li
@changelog_1165_li
H2 Console: The progress display when opening a database has been improved.
@changelog_1164_li
@changelog_1166_li
The error message when the server doesn't start has been improved.
@changelog_1165_li
@changelog_1167_li
Key values can now be changed in updatable result sets.
@changelog_1166_li
@changelog_1168_li
Changes in updatable result sets are now visible even when resetting the result set.
@changelog_1167_li
@changelog_1169_li
Temporary files were sometimes deleted too late when executing large insert, update, or delete operations.
@changelog_1168_li
@changelog_1170_li
The database file was growing after deleting many rows, and after large update operations.
@changelog_1169_h2
@changelog_1171_h2
Version 1.0.75 (2008-07-14)
@changelog_1170_li
@changelog_1172_li
Multi version concurrency (MVCC): when a row was updated or deleted, but this change was rolled back, the row was not visible by other sessions if no index was used to access it. Fixed.
@changelog_1171_li
@changelog_1173_li
Views with multiple joined tables (where one was an outer join) couldn't be used in some cases. Fixed.
@changelog_1172_li
@changelog_1174_li
The CSVREAD method did not process NULL correctly when using a whitespace field separator.
@changelog_1173_li
@changelog_1175_li
Fixed the Oracle mode: Oracle allows multiple rows with NULL in a unique index.
@changelog_1174_li
@changelog_1176_li
Running out of memory could result in incomplete transactions or corrupted databases. Fixed.
@changelog_1175_li
@changelog_1177_li
When using order by in a query that uses the same table multiple times, the order could be incorrect. Fixed.
@changelog_1176_li
@changelog_1178_li
Referential constraint checking improvement: now the constraint is only checked if the key column values change.
@changelog_1177_li
@changelog_1179_li
Some database metadata calls returned the wrong data type for DATA_TYPE columns.
@changelog_1178_li
@changelog_1180_li
The Lucene fulltext index was empty when opening a database with fulltext index enabled, and re-indexing it didn't work. Fixed.
@changelog_1179_li
@changelog_1181_li
The character '$' could not be used in identifier names (table name, column names and so on). Fixed.
@changelog_1180_li
@changelog_1182_li
The new method org.h2.tools.Server.startWebServer(conn) starts the H2 Console to inspect a database while debugging.
@changelog_1181_li
@changelog_1183_li
Stopping a WebServer didn't always work. Fixed.
@changelog_1182_h2
@changelog_1184_h2
Version 1.0.74 (2008-06-21)
@changelog_1183_li
@changelog_1185_li
Work on row level locking has been started (but there is nothing usable yet).
@changelog_1184_li
@changelog_1186_li
JaQu (Java Query), a tool similar to LINQ (Language Integrated Query; from Microsoft) is now included under src/tools/org/h2/jaqu. A small sample application is included under src/test/org/h2/test/jaqu.
@changelog_1185_li
@changelog_1187_li
The source code is now switched to Java 1.6 by default. To switch back to Java 1.4, run 'build compile'. The h2.jar file is still Java 1.4.
@changelog_1186_li
@changelog_1188_li
The ChangePassword tool is now called ChangeFileEncryption.
@changelog_1187_li
@changelog_1189_li
It is no longer allowed to create columns with the data type NULL. Also, it is no longer allowed to convert a column to the data type NULL. This was possible before but caused data loss.
@changelog_1188_li
@changelog_1190_li
When using computed columns or default values with a different data type than the column data type, a class cast exception could occur. Fixed.
@changelog_1189_li
@changelog_1191_li
Opening databases larger than 1 GB was sometimes very slow if a lot of data was deleted previously. Fixed.
@changelog_1190_li
@changelog_1192_li
RUNSCRIPT could throw a NullPointerException if the script name was an expression.
@changelog_1191_li
@changelog_1193_li
Improved compatibility. New compatibility modes for Oracle and Derby. New compatibility flag uniqueIndexNullDistinct to only allow one row with 'NULL' in a unique index. This flag is enabled for Derby, Oracle, MSSQLServer, and HSQLDB.
@changelog_1192_li
@changelog_1194_li
Linked tables: To view the statements that are executed against the target table, set the trace level to 3.
@changelog_1193_li
@changelog_1195_li
RunScript tool: new options to show and check the results of queries.
@changelog_1194_li
@changelog_1196_li
Deadlocks are now detected. One transaction is rolled back automatically.
@changelog_1195_li
@changelog_1197_li
The Lucene fulltext index was always re-created when opening a database with fulltext index enabled.
@changelog_1196_li
@changelog_1198_li
Support for overloaded Java methods. A user defined function can now be bound to multiple Java methods, if the Java methods have the same name but a different number of parameters. Thanks to Gary Tong for providing a patch!
@changelog_1197_h2
@changelog_1199_h2
Version 1.0.73 (2008-05-31)
@changelog_1198_li
@changelog_1200_li
ParameterMetaData now returns the right data type for most conditions, as in WHERE ID=?.
@changelog_1199_li
@changelog_1201_li
The table SYSTEM_RANGE now supports expressions and parameters.
@changelog_1200_li
@changelog_1202_li
New column INFORMATION_SCHEMA.CONSTRAINTS.UNIQUE_INDEX_NAME that contains the name of the unique index used to enforce this constraint, if there is such an index.
@changelog_1201_li
@changelog_1203_li
SET QUERY_TIMEOUT and Statement.setQueryTimeout no longer commits a transaction. The same applies to SET @VARIABLE, SET LOCK_TIMEOUT, SET TRACE_LEVEL_*, SET THROTTLE, and SET PATH.
@changelog_1202_li
@changelog_1204_li
The SCRIPT command does now emit IF NOT EXISTS for CREATE ROLE.
@changelog_1203_li
@changelog_1205_li
MySQL compatibility: auto_increment column are no longer automatically converted to primary key columns.
@changelog_1204_li
@changelog_1206_li
PostgreSQL compatibility: support for BOOL_OR and BOOL_AND aggregate functions.
@changelog_1205_li
@changelog_1207_li
Negative scale values for DECIMAL or NUMBER columns are now supported in regular tables and in linked tables.
@changelog_1206_li
@changelog_1208_li
A role or right can now be granted or revoked multiple times without getting an exception.
@changelog_1207_li
@changelog_1209_li
Infinite numbers in SQL scripts are listed as POWER(0, -1)), negative infinite as (-POWER(0, -1)), and NaN (not a number) as SQRT(-1).
@changelog_1208_li
@changelog_1210_li
The special double and float values 'NaN' (not a number) did not work correctly when sorting or comparing.
@changelog_1209_li
@changelog_1211_li
The fulltext search did not support CLOB data types.
@changelog_1210_li
@changelog_1212_li
If the drive with the database files was disconnected or unmounted while writing, sometimes a stack overflow exception was thrown instead of a IO exception.
@changelog_1211_li
@changelog_1213_li
The H2 Console could not be shut down from within the tool if the browser supports keepAlive (most browsers do).
@changelog_1212_li
@changelog_1214_li
If the password was passed as a char array, it was kept in an internal buffer longer than required. Theoretically the password could have been stolen if the main memory was swapped to disk before the garbage collection was run.
@changelog_1213_h2
@changelog_1215_h2
Version 1.0.72 (2008-05-10)
@changelog_1214_li
@changelog_1216_li
Some databases could not be opened when appending ;RECOVER=1 to the database URL.
@changelog_1215_li
@changelog_1217_li
The Japanese translation of the error messages and the H2 Console has been completed by Masahiro Ikemoto (Arizona Design Inc.)
@changelog_1216_li
@changelog_1218_li
Updates made to updatable rows are now visible within the same result set. DatabaseMetaData.ownUpdatesAreVisible now returns true.
@changelog_1217_li
@changelog_1219_li
ParameterMetaData now returns the correct data for INSERT and UPDATE statements.
@changelog_1218_li
@changelog_1220_li
H2 Shell: DESCRIBE now supports an schema name.
@changelog_1219_li
@changelog_1221_li
A subset of the PostgreSQL 'dollar quoting' feature is now supported.
@changelog_1220_li
@changelog_1222_li
SLF4J is now supported by using adding TRACE_LEVEL_FILE=4 to the database URL.
@changelog_1221_li
@changelog_1223_li
The recovery tool did not work if the table name contained spaces or if there was a comment on the table.
@changelog_1222_li
@changelog_1224_li
Triggers are no longer executed when changing the table structure (ALTER TABLE).
@changelog_1223_li
@changelog_1225_li
When setting BLOB or CLOB values larger than 65 KB using a remote connection, temporary files were kept on the client longer than required (until the connection was closed or the object is garbage collected). Now they are removed as soon as the PreparedStatement is closed, or when the value is overwritten.
@changelog_1224_li
@changelog_1226_li
Statements can now be canceled remotely (when using remote connections).
@changelog_1225_li
@changelog_1227_li
The Shell tool now uses java.io.Console to read the password when using JDK 1.6
@changelog_1226_li
@changelog_1228_li
When using read-only databases and setting LOG=2, an exception was written to the trace file when closing the database. Fixed.
@changelog_1227_h2
@changelog_1229_h2
Version 1.0.71 (2008-04-25)
@changelog_1228_li
@changelog_1230_li
H2 is now dual-licensed under the Eclipse Public License (EPL) and the old 'H2 License' (which is basically MPL).
@changelog_1229_li
@changelog_1231_li
Sometimes an exception 'File ID mismatch' or 'try to add a record twice' occurred after large records (8 KB or larger) are updated or deleted. See also http://code.google.com/p/h2database/issues/detail?id=22
@changelog_1230_li
@changelog_1232_li
H2 Console: The tools can now be translated (it didn't work in the last release).
@changelog_1231_li
@changelog_1233_li
New traditional Chinese translation. Thanks a lot to Derek Chao!
@changelog_1232_li
@changelog_1234_li
Indexes were not used when enabling the optimization for IN(SELECT...) (system property h2.optimizeInJoin).
@changelog_1233_h2
@changelog_1235_h2
Version 1.0.70 (2008-04-20)
@changelog_1234_li
@changelog_1236_li
The plan is to dual-license H2. The additional license is EPL (Eclipse Public License). The current license (MPL, Mozilla Public License) will stay. Current users are not affected because they can keep MPL. EPL is very similar to MPL, the only bigger difference is related to patents (EPL is a bit more business friendly in this regard). See also http://opensource.org/licenses/eclipse-1.0.php, http://www.eclipse.org/legal/eplfaq.php (FAQ), http://blogs.zdnet.com/Burnette/?p=131
@changelog_1235_li
@changelog_1237_li
Multi version concurrency (MVCC): when a row was updated, and the updated column was not indexed, this update was visible sometimes for other sessions even if it was not committed.
@changelog_1236_li
@changelog_1238_li
Calling SHUTDOWN on one connection and starting a query on another connection concurrently could result in a Java level deadlock.
@changelog_1237_li
@changelog_1239_li
New system property h2.enableAnonymousSSL (default: true) to enable anonymous SSL connections.
@changelog_1238_li
@changelog_1240_li
The precision if SUBSTR is now calculated if possible.
@changelog_1239_li
@changelog_1241_li
The autocomplete in the H2 Console has been improved a bit.
@changelog_1240_li
@changelog_1242_li
The tools in the H2 Console are now translatable.
@changelog_1241_li
@changelog_1243_li
The servlet and lucene jar files are now automatically downloaded when building.
@changelog_1242_li
@changelog_1244_li
The code switch tool has been replaced by a simpler tool called SwitchSource that just uses find and replace.
@changelog_1243_li
@changelog_1245_li
Started to write a Ant replacement ('JAnt') that uses pure Java build definitions. Advantages: ability to debug the build, extensible, flexible, no XML, a bit faster. Future plan: support creating custom h2 distributions (for embedded use). Maybe create a new project 'Jant' or 'Javen' if other people are interested.
@changelog_1244_li
@changelog_1246_li
The jar file is now about 10% smaller because the variable debugging info is no longer included. The source file and line number debugging info is still included. If required, the jar file size of the full version can be further reduced to about 720 KB using 'build jarSmall' or even more by removing unneeded components.
@changelog_1245_li
@changelog_1247_li
Added shell scripts run.sh and build.sh. chmod +x is required, but otherwise it should work. Feedback or improvements are welcome!
@changelog_1246_li
@changelog_1248_li
Databases in zip files: large queries are now supported. Temp files are created in the temp directory if required. The documentation how to create the zip file has been corrected.
@changelog_1247_li
@changelog_1249_li
Invalid inline views threw confusing SQL exceptions.
@changelog_1248_li
@changelog_1250_li
The Japanese translation of the error messages and the H2 Console has been improved. Thanks a lot to Masahiro IKEMOTO.
@changelog_1249_li
@changelog_1251_li
Optimization for MIN() and MAX() when using MVCC.
@changelog_1250_li
@changelog_1252_li
To protect against remote brute force password attacks, the delay after each unsuccessful login now gets double as long. New system properties h2.delayWrongPasswordMin and h2.delayWrongPasswordMax.
@changelog_1251_li
@changelog_1253_li
After setting the query timeout and then resetting it, the next query would still timeout. Fixed.
@changelog_1252_li
@changelog_1254_li
Adding a IDENTITY column to a table with data threw a lock timeout.
@changelog_1253_li
@changelog_1255_li
OutOfMemoryError could occur when using EXISTS or IN(SELECT ..).
@changelog_1254_li
@changelog_1256_li
The built-in connection pool is not called JdbcConnectionPool. The API and documentation has been changed.
@changelog_1255_li
@changelog_1257_li
The ConvertTraceFile tool now generates SQL statement statistics at the end of the SQL script file (similar to the profiling data generated when using java -Xrunhprof).
@changelog_1256_li
@changelog_1258_li
Nested joins are now supported (A JOIN B JOIN C ON .. ON ..)
@changelog_1257_h2
@changelog_1259_h2
Version 1.0.69 (2008-03-29)
@changelog_1258_li
@changelog_1260_li
Most command line tools can now be called from within the H2 Console.
@changelog_1259_li
@changelog_1261_li
A new Shell tools is now included (org.h2.tools.Shell) to query a database from the command line.
@changelog_1260_li
@changelog_1262_li
The command line options in the tools have changed: instead of '-log true' now '-trace' is used. Also, '-ifExists', '-tcpSSL' and '-tcpAllowOthers' and so on have changed: now the 'true' is no longer needed. The old behavior is still supported.
@changelog_1261_li
@changelog_1263_li
New system property h2.sortNullsHigh to invert the default sorting behavior for NULL. The default didn't change.
@changelog_1262_li
@changelog_1264_li
Performance was very slow when using LOG=2 and deleting or updating all rows of a table in a loop. Fixed.
@changelog_1263_li
@changelog_1265_li
ALTER TABLE or CREATE TABLE now support parameters for the password field.
@changelog_1264_li
@changelog_1266_li
The linear hash has been removed. It was always slower than the b-tree index, and there were some bugs that would be hard to fix.
@changelog_1265_li
@changelog_1267_li
TRACE_LEVEL_ settings are no longer persistent. This was a problem when database initialization code caused a lot of trace output.
@changelog_1266_li
@changelog_1268_li
Fulltext search (native implementation): The words table is no longer an in-memory table because this caused memory problems in some cases.
@changelog_1267_li
@changelog_1269_li
It was possible to create a role with the name as an existing user (but not vice versa). This is not allowed any more.
@changelog_1268_li
@changelog_1270_li
The recovery tool didn't work correctly for tables without rows.
@changelog_1269_li
@changelog_1271_li
For years below 1, the YEAR method didn't return the correct value, and the conversion from date and timestamp to varchar was incorrect.
@changelog_1270_li
@changelog_1272_li
CSVWRITE caused a NullPointerException when not specifying a nullString.
@changelog_1271_li
@changelog_1273_li
When a log file switch occurred just after a truncate table or drop table statement, the database could not be started normally (RECOVER=1 was required). Fixed.
@changelog_1272_li
@changelog_1274_li
When a log file switch occurred in the middle of a sequence flush (sequences are only flushed every 32 values by default), the sequence value was lost. Fixed.
@changelog_1273_li
@changelog_1275_li
Altering a sequence didn't unlock the system table when autocommit switched off.
@changelog_1274_h2
@changelog_1276_h2
Version 1.0.68 (2008-03-18)
@changelog_1275_li
@changelog_1277_li
Very large SELECT DISTINCT and UNION EXCEPT queries are now supported, however this feature is disabled by default. To enable it, set the system property h2.maxMemoryRowsDistinct to a lower value, for example 10000.
@changelog_1276_li
@changelog_1278_li
A error is now thrown when trying to call a method inside a trigger that implicitly commits the current transaction, if an object is locked.
@changelog_1277_li
@changelog_1279_li
Unused LOB files were deleted much too late. Now they are deleted if no longer referenced in memory.
@changelog_1278_li
@changelog_1280_li
ALTER SEQUENCE and ALTER TABLE ALTER COLUMN RESTART can now be used inside a transaction.
@changelog_1279_li
@changelog_1281_li
New system property h2.aliasColumnName. When enabled, aliased columns (as in SELECT ID AS I FROM TEST) return the real table and column name in ResultSetMetaData.getTableName() and getColumnName(). This is disabled by default for compatibility with other databases (HSQLDB, Apache Derby, PostgreSQL, some version of MySQL). In version 1.1 this setting will be enabled.
@changelog_1280_li
@changelog_1282_li
When using encrypted databases, and using the wrong file password, the log file was renamed if the database was not already open. Fixed.
@changelog_1281_li
@changelog_1283_li
Improved performance when using lob files in directories (however this is still disabled by default)
@changelog_1282_li
@changelog_1284_li
H2 Console: autocomplete didn't work with very large scripts. Fixed.
@changelog_1283_li
@changelog_1285_li
Fulltext search: new method SEARCH_DATA that returns the column names and primary keys as arrays.
@changelog_1284_li
@changelog_1286_li
New experimental optimization for GROUP BY queries if an index can be used that matches the group by columns. To enable this optimization, set the system property h2.optimizeGroupSorted to true.
@changelog_1285_li
@changelog_1287_li
When using multi-version concurrency (MVCC=TRUE), duplicate rows could appear in the result set when running queries with uncommitted changes in the same session.
@changelog_1286_li
@changelog_1288_li
H2 Console: remote connections were very slow because getHostName/getRemoteHost was used. Fixed (now using getHostAddress/getRemoteAddr.
@changelog_1287_li
@changelog_1289_li
H2 Console: on Linux, Firefox, Konqueror, or Opera (in this order) are now started if available. This has been tested on Ubuntu.
@changelog_1288_li
@changelog_1290_li
H2 Console: the start window works better with IKVM
@changelog_1289_li
@changelog_1291_li
H2 Console: improved compatibility with Safari (Safari requires keep-alive)
@changelog_1290_li
@changelog_1292_li
Random: the process didn't stop if generating the random seed using the standard way (SecureRandom.generateSeed) was very slow. Now using a daemon thread to avoid this problem.
@changelog_1291_li
@changelog_1293_li
SELECT UNION with a different number of ORDER BY columns did throw an ArrayIndexOutOfBoundsException.
@changelog_1292_li
@changelog_1294_li
When using a view, the column precision was changed to the default scale for some data types.
@changelog_1293_li
@changelog_1295_li
CSVWRITE now supports a 'null string' that is used for parsing and writing NULL.
@changelog_1294_li
@changelog_1296_li
Some long running queries could not be canceled.
@changelog_1295_li
@changelog_1297_li
Queries with many outer join tables were very slow. Fixed.
@changelog_1296_li
@changelog_1298_li
The performance of text comparison has been improved when using locale sensitive string comparison (SET COLLATOR). Now CollationKey is used with a LRU cache. The default cache size is 10000, and can be changed using the system property h2.collatorCacheSize. Use 0 to disable the cache.
@changelog_1297_li
@changelog_1299_li
UPDATE SET column=DEFAULT is now supported.
@changelog_1298_h2
@changelog_1300_h2
Version 1.0.67 (2008-02-22)
@changelog_1299_li
@changelog_1301_li
New function FILE_READ to read a file or from an URL. Both binary and text data is supported.
@changelog_1300_li
@changelog_1302_li
CREATE TABLE AS SELECT now supports specifying the column list and data types.
@changelog_1301_li
@changelog_1303_li
Connecting to a TCP server and at shutting it down at the same time could cause a Java level deadlock.
@changelog_1302_li
@changelog_1304_li
A user now has all rights on his own local temporary tables.
@changelog_1303_li
@changelog_1305_li
The CSV tool now supports a custom lineSeparator.
@changelog_1304_li
@changelog_1306_li
When using multiple connections, empty space was reused too early sometimes. This could corrupt the database when recovering.
@changelog_1305_li
@changelog_1307_li
The H2 Console has been translated to Dutch. Thanks a lot to Remco Schoen!
@changelog_1306_li
@changelog_1308_li
Databases can now be opened even if trigger classes are not in the classpath. The exception is thrown when trying to fire the trigger.
@changelog_1307_li
@changelog_1309_li
Opening databases with ACCESS_MODE_DATA=r is now supported. In this case the database is read-only, but the files don't not need to be read-only.
@changelog_1308_li
@changelog_1310_li
Security: The database now waits 200 ms before throwing an exception if the user name or password don't match, to slow down dictionary attacks.
@changelog_1309_li
@changelog_1311_li
The value cache is now a soft reference cache. This should help save memory.
@changelog_1310_li
@changelog_1312_li
CREATE INDEX on a table with many rows could run out of memory. Fixed.
@changelog_1311_li
@changelog_1313_li
Large result sets are now a bit faster.
@changelog_1312_li
@changelog_1314_li
ALTER TABLE ALTER COLUMN RESTART and ALTER SEQUENCE now support parameters (any expressions).
@changelog_1313_li
@changelog_1315_li
When setting the base directory on the command line, the user directory prefix ('~') was ignored.
@changelog_1314_li
@changelog_1316_li
The DbStarter servlet didn't start the TCP listener even if configured.
@changelog_1315_li
@changelog_1317_li
Statement.setQueryTimeout() is now supported.
@changelog_1316_li
@changelog_1318_li
New session setting QUERY_TIMEOUT, and new system property h2.maxQueryTimeout.
@changelog_1317_li
@changelog_1319_li
Changing the transaction log level (SET LOG) is now written to the trace file by default.
@changelog_1318_li
@changelog_1320_li
In a SQL script, primary key constraints are now ordered before foreign key constraints.
@changelog_1319_li
@changelog_1321_li
It was not possible to create a referential constraint to a table in a different schema in some situations.
@changelog_1320_li
@changelog_1322_li
The H2 Console was slow when the database contains many tables. Now the column names are not shown in this case.
@changelog_1321_h2
@changelog_1323_h2
Version 1.0.66 (2008-02-02)
@changelog_1322_li
@changelog_1324_li
There is a new online error analyzer tool.
@changelog_1323_li
@changelog_1325_li
H2 Console: stack traces are now links to the source code in the source repository (H2 database only).
@changelog_1324_li
@changelog_1326_li
CHAR data type equals comparison was case insensitive instead of case sensitive.
@changelog_1325_li
@changelog_1327_li
The exception 'Value too long for column' now includes the data.
@changelog_1326_li
@changelog_1328_li
The table name was missing in the documentation of CREATE INDEX.
@changelog_1327_li
@changelog_1329_li
Better support for IKVM (www.ikvm.net): the H2 Console now opens a browser window.
@changelog_1328_li
@changelog_1330_li
The cache size was not correctly calculated for tables with large objects (specially if compression is used). This could lead to out-of-memory exceptions.
@changelog_1329_li
@changelog_1331_li
The exception "Hexadecimal string contains non-hex character" was not always thrown when it should have been. Fixed.
@changelog_1330_li
@changelog_1332_li
The H2 Console now provides a link to the documentation when an error occurs (H2 databases only so far).
@changelog_1331_li
@changelog_1333_li
The acting as PostgreSQL server, when a base directory was set, and the H2 Console was started as well, the base directory was applied twice.
@changelog_1332_li
@changelog_1334_li
Calling EXTRACT(HOUR FROM ...) or EXTRACT(HH FROM ...) returned the wrong values (0 to 11 instead of 0 to 23). All other tested databases return values from 0 to 23. Please check if your application relies on the old behavior before upgrading.
@changelog_1333_li
@changelog_1335_li
For compatibility with other databases the column default (COLUMN_DEF) for columns without default is now null (it was an empty string).
@changelog_1334_li
@changelog_1336_li
Statements that contain very large subqueries (where the subquery result does not fit in memory) are now faster.
@changelog_1335_li
@changelog_1337_li
Variables: large objects (CLOB and BLOB) that don't fit in memory did not work correctly when used as variables.
@changelog_1336_li
@changelog_1338_li
Fulltext search is now supported in named in-memory databases.
@changelog_1337_li
@changelog_1339_li
H2 Console: multiple consecutive spaces in the setting name did not work. Fixed.
@changelog_1338_h2
@changelog_1340_h2
Version 1.0.65 (2008-01-18)
@changelog_1339_li
@changelog_1341_li
The build (ant) now automatically switches the source code to the correct version (JDK 1.4/1.5 or 1.6).
@changelog_1340_li
@changelog_1342_li
A recovery bug has been fixed. With older versions, it was necessary to add ;RECOVER=1 to the database URL in cases where it should not have been required.
@changelog_1341_li
@changelog_1343_li
The performance for DROP and DROP ALL OBJECTS has been improved.
@changelog_1342_li
@changelog_1344_li
The ChangePassword API has been improved.
@changelog_1343_li
@changelog_1345_li
User defined variables are now supported. Examples: SET @VAR=10;CALL @VAR. This can be used for running totals as in: select x, set(@t, ifnull(@t, 0) + x) from system_range(1, 10)
@changelog_1344_li
@changelog_1346_li
The Ukrainian translation has been improved.
@changelog_1345_li
@changelog_1347_li
CALL statements can now be used in batch updates and called using Statement.executeUpdate.
@changelog_1346_li
@changelog_1348_li
New read-only setting CREATE_BUILD (the build number of the database engine that created the database).
@changelog_1347_li
@changelog_1349_li
The optimizer did not use multi column indexes for range queries in some cases. Fixed.
@changelog_1348_li
@changelog_1350_li
The H2 Console now calls DataSource.getConnection() instead of DataSource.getConnection(user, password) when user name and password are not specified.
@changelog_1349_li
@changelog_1351_li
The bind IP address can now be set when using multi-homed host (if multiple network adapters are available) using the system property h2.bindAddress.
@changelog_1350_li
@changelog_1352_li
Batch update: Calling BatchUpdateException.printStackTrace() could result in out of memory. Fixed.
@changelog_1351_li
@changelog_1353_li
Indexes of unique or foreign constraints where not dropped when the constraint was dropped after altering the table (for example dropping a column). Fixed.
@changelog_1352_li
@changelog_1354_li
The performance for large result sets in the server mode has been improved.
@changelog_1353_li
@changelog_1355_li
The setting h2.serverSmallResultSetSize has been renamed to h2.serverResultSetFetchSize.
@changelog_1354_li
@changelog_1356_li
The SCRIPT command now uses multi-row insert statements to save space except if the option SIMPLE is used.
@changelog_1355_li
@changelog_1357_li
The SCRIPT command did not split up CLOB data correctly. Fixed.
@changelog_1356_li
@changelog_1358_li
Optimization for single column distinct queries with an index: select distinct name from test. Can be disabled by setting the system property h2.optimizeDistinct to false.
@changelog_1357_li
@changelog_1359_li
DROP ALL OBJECTS did not drop user defined aggregate functions and domains.
@changelog_1358_li
@changelog_1360_li
PostgreSQL compatibility: COUNT(T.*) is now supported.
@changelog_1359_li
@changelog_1361_li
LIKE comparisons are now faster.
@changelog_1360_li
@changelog_1362_li
Encrypted databases are now faster.
@download_1000_h1
Downloads
@download_1001_h3
Version 1.1.104 (2008-11-28, Beta)
Version 1.1.105 (2008-12-19, Beta)
@download_1002_a
Windows Installer
......@@ -2612,7 +2618,7 @@ ORDER BY, GROUP BY, HAVING, UNION, LIMIT, TOP
Collation support, users, roles
@features_1062_li
Compatibility modes for HSQLDB, MySQL and PostgreSQL
Compatibility modes for IBM DB2, Apache Derby, HSQLDB, MS SQL Server, MySQL, Oracle, and PostgreSQL.
@features_1063_h3
Security Features
......@@ -3830,366 +3836,375 @@ Compatibility Modes
For certain features, this database can emulate the behavior of specific databases. Not all features or differences of those databases are implemented. Here is the list of currently supported modes and the difference to the regular mode:
@features_1468_h3
PostgreSQL Compatibility Mode
DB2 Compatibility Mode
@features_1469_p
To use the PostgreSQL mode, use the database URL <code>jdbc:h2:~/test;MODE=PostgreSQL</code> or the SQL statement <code>SET MODE PostgreSQL</code> .
To use the IBM DB2 mode, use the database URL <code>jdbc:h2:~/test;MODE=DB2</code> or the SQL statement <code>SET MODE DB2</code> .
@features_1470_li
Concatenation of a NULL with another value results in NULL. Usually, the NULL is treated as an empty string if only one of the operators is NULL, and NULL is only returned if both values are NULL.
For aliased columns, ResultSetMetaData.getColumnName() returns the alias name and getTableName() returns null.
@features_1471_li
When converting a floating point number to a integer, the fractional digits should not be truncated, but the value should be rounded.
Support for the syntax [OFFSET .. ROW] [FETCH ... ONLY] as an alternative syntax for LIMIT .. OFFSET.
@features_1472_li
The system columns 'CTID' and 'OID' should be supported.
@features_1472_h3
Derby Compatibility Mode
@features_1473_li
For aliased columns, ResultSetMetaData.getColumnName() returns the alias name and getTableName() returns null.
@features_1473_p
To use the Apache Derby mode, use the database URL <code>jdbc:h2:~/test;MODE=Derby</code> or the SQL statement <code>SET MODE Derby</code> .
@features_1474_h3
MySQL Compatibility Mode
@features_1474_li
For aliased columns, ResultSetMetaData.getColumnName() returns the alias name and getTableName() returns null.
@features_1475_p
To use the MySQL mode, use the database URL <code>jdbc:h2:~/test;MODE=MySQL</code> or the SQL statement <code>SET MODE MySQL</code> .
@features_1475_li
For unique indexes, NULL is distinct. That means only one row with NULL in one of the columns is allowed.
@features_1476_li
When inserting data, if a column is defined to be NOT NULL and NULL is inserted, then a 0 (or empty string, or the current timestamp for timestamp columns) value is used. Usually, this operation is not allowed and an exception is thrown.
@features_1476_h3
HSQLDB Compatibility Mode
@features_1477_li
When converting a floating point number to a integer, the fractional digits should not be truncated, but the value should be rounded.
@features_1477_p
To use the HSQLDB mode, use the database URL <code>jdbc:h2:~/test;MODE=HSQLDB</code> or the SQL statement <code>SET MODE HSQLDB</code> .
@features_1478_li
The identifiers should be returned in lower case.
For aliased columns, ResultSetMetaData.getColumnName() returns the alias name and getTableName() returns null.
@features_1479_li
Creating indexes in the CREATE TABLE statement should be supported.
When converting the scale of decimal data, the number is only converted if the new scale is smaller then current scale. Usually, the scale is converted and 0s are added if required.
@features_1480_li
For aliased columns, ResultSetMetaData.getColumnName() and getTableName() return the real column and table name.
Concatenation of a NULL with another value results in NULL. Usually, the NULL is treated as an empty string if only one of the operators is NULL, and NULL is only returned if both values are NULL.
@features_1481_h3
HSQLDB Compatibility Mode
@features_1481_li
For unique indexes, NULL is distinct. That means only one row with NULL in one of the columns is allowed.
@features_1482_p
To use the HSQLDB mode, use the database URL <code>jdbc:h2:~/test;MODE=HSQLDB</code> or the SQL statement <code>SET MODE HSQLDB</code> .
@features_1482_h3
MS SQL Server Compatibility Mode
@features_1483_li
Concatenation of a NULL with another value results in NULL. Usually, the NULL is treated as an empty string if only one of the operators is NULL, and NULL is only returned if both values are NULL.
@features_1483_p
To use the MS SQL Server mode, use the database URL <code>jdbc:h2:~/test;MODE=MSSQLServer</code> or the SQL statement <code>SET MODE MSSQLServer</code> .
@features_1484_li
When converting the scale of decimal data, the number is only converted if the new scale is smaller then current scale. Usually, the scale is converted and 0s are added if required.
For aliased columns, ResultSetMetaData.getColumnName() returns the alias name and getTableName() returns null.
@features_1485_li
When using unique indexes, multiple rows with NULL in one of the columns are allowed by default. However many databases view NULL as distinct in this regard and only allow one row with NULL.
Identifiers may be quoted using square brackets as in [Test].
@features_1486_li
For aliased columns, ResultSetMetaData.getColumnName() returns the alias name and getTableName() returns null.
For unique indexes, NULL is distinct. That means only one row with NULL in one of the columns is allowed.
@features_1487_h3
MS SQL Server Compatibility Mode
MySQL Compatibility Mode
@features_1488_p
To use the MS SQL Server mode, use the database URL <code>jdbc:h2:~/test;MODE=MSSQLServer</code> or the SQL statement <code>SET MODE MSSQLServer</code> .
To use the MySQL mode, use the database URL <code>jdbc:h2:~/test;MODE=MySQL</code> or the SQL statement <code>SET MODE MySQL</code> .
@features_1489_li
Identifiers may be quoted using square brackets as in [Test].
When inserting data, if a column is defined to be NOT NULL and NULL is inserted, then a 0 (or empty string, or the current timestamp for timestamp columns) value is used. Usually, this operation is not allowed and an exception is thrown.
@features_1490_li
When using unique indexes, multiple rows with NULL in one of the columns are allowed by default. However many databases view NULL as distinct in this regard and only allow one row with NULL.
Creating indexes in the CREATE TABLE statement should be supported.
@features_1491_li
For aliased columns, ResultSetMetaData.getColumnName() returns the alias name and getTableName() returns null.
The identifiers should be returned in lower case.
@features_1492_h3
Derby Compatibility Mode
@features_1492_li
When converting a floating point number to a integer, the fractional digits should not be truncated, but the value should be rounded.
@features_1493_p
To use the Derby mode, use the database URL <code>jdbc:h2:~/test;MODE=Derby</code> or the SQL statement <code>SET MODE Derby</code> .
@features_1493_h3
Oracle Compatibility Mode
@features_1494_li
When using unique indexes, multiple rows with NULL in one of the columns are allowed by default. However many databases view NULL as distinct in this regard and only allow one row with NULL.
@features_1494_p
To use the Oracle mode, use the database URL <code>jdbc:h2:~/test;MODE=Oracle</code> or the SQL statement <code>SET MODE Oracle</code> .
@features_1495_li
For aliased columns, ResultSetMetaData.getColumnName() returns the alias name and getTableName() returns null.
@features_1496_h3
Oracle Compatibility Mode
@features_1496_li
When using unique indexes, multiple rows with NULL in all columns are allowed, however it is not allowed to have multiple rows with the same values otherwise.
@features_1497_p
To use the Oracle mode, use the database URL <code>jdbc:h2:~/test;MODE=Oracle</code> or the SQL statement <code>SET MODE Oracle</code> .
@features_1497_h3
PostgreSQL Compatibility Mode
@features_1498_li
When using unique indexes, multiple rows with NULL in one of the columns are allowed by default. However many databases view NULL as distinct in this regard and only allow one row with NULL.
@features_1498_p
To use the PostgreSQL mode, use the database URL <code>jdbc:h2:~/test;MODE=PostgreSQL</code> or the SQL statement <code>SET MODE PostgreSQL</code> .
@features_1499_li
For aliased columns, ResultSetMetaData.getColumnName() returns the alias name and getTableName() returns null.
@features_1500_h2
@features_1500_li
Concatenation of a NULL with another value results in NULL. Usually, the NULL is treated as an empty string if only one of the operators is NULL, and NULL is only returned if both values are NULL.
@features_1501_li
When converting a floating point number to a integer, the fractional digits should not be truncated, but the value should be rounded.
@features_1502_li
The system columns 'CTID' and 'OID' should be supported.
@features_1503_h2
Auto-Reconnect
@features_1501_p
@features_1504_p
The auto-reconnect feature causes the JDBC driver to reconnect to the database if the connection is lost. The automatic re-connect only occurs when auto-commit is enabled; if auto-commit is disabled, an exception is thrown.
@features_1502_p
@features_1505_p
Re-connecting will open a new session. After an automatic re-connect, variables and local temporary tables definitions (excluding data) are re-created. The contents of the system table INFORMATION_SCHEMA.SESSION_STATE contains all client side state that is re-created.
@features_1503_h2
@features_1506_h2
Automatic Mixed Mode
@features_1504_p
@features_1507_p
Multiple processes can access the same database without having to explicitly start the server. To do that, append <code>;AUTO_SERVER=TRUE</code> to the database URL. In this case, the first connection to the database is made in embedded mode, and additionally a server is started. If the database is already open in another process, the server mode is used.
@features_1505_p
@features_1508_p
When using this feature, auto-reconnect is enabled as well.
@features_1506_p
@features_1509_p
The application that opens the first connection to the database uses the embedded mode, which is faster than the server mode. Therefore the main application should open the database first if possible. A server is started on a random port. This server allows remote connections, however only to this database. In addition to the user name and password, the client sends the random key that is stored in .lock.db file to the server.
@features_1507_h2
@features_1510_h2
Using the Trace Options
@features_1508_p
@features_1511_p
To find problems in an application, it is sometimes good to see what database operations where executed. This database offers the following trace features:
@features_1509_li
@features_1512_li
Trace to System.out and/or a file
@features_1510_li
@features_1513_li
Support for trace levels OFF, ERROR, INFO, and DEBUG
@features_1511_li
@features_1514_li
The maximum size of the trace file can be set
@features_1512_li
@features_1515_li
The Java code generation is possible
@features_1513_li
@features_1516_li
Trace can be enabled at runtime by manually creating a file
@features_1514_h3
@features_1517_h3
Trace Options
@features_1515_p
@features_1518_p
The simplest way to enable the trace option is setting it in the database URL. There are two settings, one for System.out (TRACE_LEVEL_SYSTEM_OUT) tracing, and one for file tracing (TRACE_LEVEL_FILE). The trace levels are 0 for OFF, 1 for ERROR (the default), 2 for INFO and 3 for DEBUG. A database URL with both levels set to DEBUG is:
@features_1516_p
@features_1519_p
The trace level can be changed at runtime by executing the SQL command <code>SET TRACE_LEVEL_SYSTEM_OUT level</code> (for System.out tracing) or <code>SET TRACE_LEVEL_FILE level</code> (for file tracing). Example:
@features_1517_h3
@features_1520_h3
Setting the Maximum Size of the Trace File
@features_1518_p
@features_1521_p
When using a high trace level, the trace file can get very big quickly. The size of the file can be limited by executing the SQL statement <code>SET TRACE_MAX_FILE_SIZE maximumFileSizeInMB</code> . If the log file exceeds the limit, the file is renamed to .old and a new file is created. If another .old file exists, it is deleted. The default setting is 16 MB. Example:
@features_1519_h3
@features_1522_h3
Java Code Generation
@features_1520_p
@features_1523_p
When setting the trace level to INFO or DEBUG, Java source code is generated as well, so that problem can be reproduced more easily. The trace file looks like this:
@features_1521_p
@features_1524_p
You need to filter out the lines without /**/ to get the Java source code. In Windows, a simple way to do that is:
@features_1522_p
@features_1525_p
Afterwards, you need to complete the file Trace.java before it can be compiled, for example with:
@features_1523_p
@features_1526_p
Also, the user name and password needs to be set, because they are not listed in the trace file.
@features_1524_h3
@features_1527_h3
Enabling the Trace Option at Runtime by Manually Creating a File
@features_1525_p
@features_1528_p
Sometimes, you can't or don't want to change the application or database URL. There is still a way to enable the trace mode in these cases, even at runtime (while the database connection is open). You only need to create a special file in the directory where the database files are stored. The database engine checks every 4 seconds if this file exists (only while executing a statement). The file name is the database name plus '.trace.db.start'. This feature is disabled if the database is encrypted.
@features_1526_p
@features_1529_p
Example: if a database is called 'test', then the file to start tracing is 'test.trace.db.start'. The database engine tries to delete this file when it detects it. If trace is enabled using the start file, the trace level is not persistent to the database, and trace is switched back to the level that was set before when connecting to the database. However, if the start file is read only, the database engine cannot delete the file and will always enable the trace mode when connecting.
@features_1527_h2
@features_1530_h2
Using Other Logging APIs
@features_1528_p
@features_1531_p
By default, this database uses its own native 'trace' facility. This facility is called 'trace' and not 'log' within this database to avoid confusion with the transaction log. Trace messages can be written to both file and System.out. In most cases, this is sufficient, however sometimes it is better to use the same facility as the application, for example Log4j. To do that, this database support SLF4J.
@features_1529_a
@features_1532_a
SLF4J
@features_1530_p
@features_1533_p
is a simple facade for various logging APIs and allows to plug in the desired implementation at deployment time. SLF4J supports implementations such as Logback, Log4j, Jakarta Commons Logging (JCL), JDK 1.4 logging, x4juli, and Simple Log.
@features_1531_p
@features_1534_p
To enable SLF4J, set the file trace level to 4 in the database URL:
@features_1532_p
@features_1535_p
Changing the log mechanism is not possible after the database is open, that means executing the SQL statement SET TRACE_LEVEL_FILE 4 when the database is already open will not have the desired effect. To use SLF4J, all required jar files need to be in the classpath. If it does not work, check in the file &lt;database&gt;.trace.db for error messages.
@features_1533_h2
@features_1536_h2
Read Only Databases
@features_1534_p
@features_1537_p
If the database files are read-only, then the database is read-only as well. It is not possible to create new tables, add or modify data in this database. Only SELECT statements are allowed. To create a read-only database, close the database so that the log file gets smaller. Do not delete the log file. Then, make the database files read-only using the operating system. When you open the database now, it is read-only. There are two ways an application can find out a database is read-only: By calling Connection.isReadOnly() or by executing the SQL statement CALL READONLY().
@features_1535_h2
@features_1538_h2
Read Only Databases in Zip or Jar File
@features_1536_p
@features_1539_p
To create a read-only database in a zip, first create a regular persistent database, and then create a backup. If you are using a database named 'test', an easy way to do that is using the Backup tool or the BACKUP SQL statement:
@features_1537_p
@features_1540_p
The database must not have pending changes, that means you need to close all connections to the database, open one single connection, and then execute the statement. Afterwards, you can log out, and directly open the database in the zip file using the following database URL:
@features_1538_p
@features_1541_p
Databases in a zip file are read-only. The performance for some queries will be slower than when using a regular database, because random access in zip files is not supported (only streaming). How much this affects the performance depends on the queries and the data. The database is not read in memory; so large databases are supported as well. The same indexes are used than when using a regular database.
@features_1539_h2
@features_1542_h2
Graceful Handling of Low Disk Space Situations
@features_1540_p
@features_1543_p
The database is able to deal with situations where the disk space available is running low. Whenever the database starts, an 'emergency space' file is created (size is 1 MB), and if there is no more space available, the file will shrink. If the space available is lower than 128 KB, the database will go into a special read only mode, where writing operations are no longer allowed: All writing operations will throw the exception 'No disk space available' from this point on. To go back to the normal operating mode, all connections to the database need to be closed first, and space needs to be freed up.
@features_1541_p
@features_1544_p
It is possible to install a database event listener to detect low disk space situations early on (when only 1 MB if space is available). To do this, use the SQL statement SET DATABASE_EVENT_LISTENER. The listener can also be set at connection time, using an URL of the form jdbc:h2:~/test;DATABASE_EVENT_LISTENER='com.acme.DbListener' (the quotes around the class name are required). See also the DatabaseEventListener API.
@features_1542_h3
@features_1545_h3
Opening a Corrupted Database
@features_1543_p
@features_1546_p
If a database cannot be opened because the boot info (the SQL script that is run at startup) is corrupted, then the database can be opened by specifying a database event listener. The exceptions are logged, but opening the database will continue.
@features_1544_h2
@features_1547_h2
Computed Columns / Function Based Index
@features_1545_p
@features_1548_p
Function indexes are not directly supported by this database, but they can be easily emulated by using computed columns. For example, if an index on the upper-case version of a column is required, just create a computed column with the upper-case version of the original column, and index this column:
@features_1546_p
@features_1549_p
When inserting data, it is not required (better: not allowed) to specify a value for the upper-case version of the column, because the value is generated. But you can use the column when querying the table:
@features_1547_h2
@features_1550_h2
Multi-Dimensional Indexes
@features_1548_p
@features_1551_p
A tool is provided to execute efficient multi-dimension (spatial) range queries. This database does not support a specialized spatial index (R-Tree or similar). Instead, the B-Tree index is used. For each record, the multi-dimensional key is converted (mapped) to a single dimensional (scalar) value. This value specifies the location on a space-filling curve.
@features_1549_p
@features_1552_p
Currently, Z-order (also called N-order or Morton-order) is used; Hilbert curve could also be used, but the implementation is more complex. The algorithm to convert the multi-dimensional value is called bit-interleaving. The scalar value is indexed using a B-Tree index (usually using a computed column).
@features_1550_p
@features_1553_p
The method can result in a drastic performance improvement over just using an index on the first column. Depending on the data and number of dimensions, the improvement is usually higher than factor 5. The tool generates a SQL query from a specified multi-dimensional range. The method used is not database dependent, and the tool can easily be ported to other databases. For an example how to use the tool, please have a look at the sample code provided in TestMultiDimension.java.
@features_1551_h2
@features_1554_h2
Using Passwords
@features_1552_h3
@features_1555_h3
Using Secure Passwords
@features_1553_p
@features_1556_p
Remember that weak passwords can be broken no matter of the encryption and security protocol. Don't use passwords that can be found in a dictionary. Also appending numbers does not make them secure. A way to create good passwords that can be remembered is, take the first letters of a sentence, use upper and lower case characters, and creatively include special characters. Example:
@features_1554_p
@features_1557_p
i'sE2rtPiUKtT (it's easy to remember this password if you know the trick)
@features_1555_h3
@features_1558_h3
Passwords: Using Char Arrays instead of Strings
@features_1556_p
@features_1559_p
Java Strings are immutable objects and cannot be safely 'destroyed' by the application. After creating a String, it will remain in the main memory of the computer at least until it is garbage collected. The garbage collection cannot be controlled by the application, and even if it is garbage collected the data may still remain in memory. It might also be possible that the part of memory containing the password is swapped to disk (because not enough main memory is available).
@features_1557_p
@features_1560_p
An attacker might have access to the swap file of the operating system. It is therefore a good idea to use char arrays instead of Strings to store passwords. Char arrays can be cleared (filled with zeros) after use, and therefore the password will not be stored in the swap file.
@features_1558_p
@features_1561_p
This database supports using char arrays instead of String to pass user and file passwords. The following code can be used to do that:
@features_1559_p
@features_1562_p
In this example, the password is hard code in the application, which is not secure of course. However, Java Swing supports a way to get passwords using a char array (JPasswordField).
@features_1560_h3
@features_1563_h3
Passing the User Name and/or Password in the URL
@features_1561_p
@features_1564_p
Instead of passing the user name as a separate parameter as in <code>Connection conn = DriverManager. getConnection("jdbc:h2:~/test", "sa", "123");</code> the user name (and/or password) can be supplied in the URL itself: <code>Connection conn = DriverManager. getConnection("jdbc:h2:~/test;USER=sa;PASSWORD=123");</code> The settings in the URL override the settings passed as a separate parameter.
@features_1562_h2
@features_1565_h2
User-Defined Functions and Stored Procedures
@features_1563_p
@features_1566_p
In addition to the built-in functions, this database supports user-defined Java functions. In this database, Java functions can be used as stored procedures as well. A function must be declared (registered) before it can be used. Only static Java methods are supported; both the class and the method must be public. Example Java method:
@features_1564_p
@features_1567_p
The Java function must be registered in the database by calling CREATE ALIAS:
@features_1565_p
@features_1568_p
For a complete sample application, see src/test/org/h2/samples/Function.java.
@features_1566_h3
@features_1569_h3
Function Data Type Mapping
@features_1567_p
@features_1570_p
Functions that accept non-nullable parameters such as 'int' will not be called if one of those parameters is NULL. In this case, the value NULL is used as the result. If the function should be called in this case, you need to use 'java.lang.Integer' instead of 'int'.
@features_1568_h3
@features_1571_h3
Functions that require a Connection
@features_1569_p
@features_1572_p
If the first parameter in a Java function is a java.sql.Connection, then the connection to database is provided. This connection does not need to be closed before returning.
@features_1570_h3
@features_1573_h3
Functions throwing an Exception
@features_1571_p
@features_1574_p
If a function throws an Exception, then the current statement is rolled back and the exception is thrown to the application.
@features_1572_h3
@features_1575_h3
Functions returning a Result Set
@features_1573_p
@features_1576_p
Functions may returns a result set. Such a function can be called with the CALL statement:
@features_1574_h3
@features_1577_h3
Using SimpleResultSet
@features_1575_p
@features_1578_p
A function that returns a result set can create this result set from scratch using the SimpleResultSet tool:
@features_1576_h3
@features_1579_h3
Using a Function as a Table
@features_1577_p
@features_1580_p
A function returning a result set can be like a table. However, in this case the function is called at least twice: First while parsing the statement to collect the column names (with parameters set to null where not known at compile time). And then, while executing the statement to get the data (may be repeatedly if this is a join). If the function is called just to get the column list, the URL of the connection passed to the function is jdbc:columnlist:connection. Otherwise, the URL of the connection is jdbc:default:connection.
@features_1578_h2
@features_1581_h2
Triggers
@features_1579_p
@features_1582_p
This database supports Java triggers that are called before or after a row is updated, inserted or deleted. Triggers can be used for complex consistency checks, or to update related data in the database. It is also possible to use triggers to simulate materialized views. For a complete sample application, see src/test/org/h2/samples/TriggerSample.java. A Java trigger must implement the interface org.h2.api.Trigger:
@features_1580_p
@features_1583_p
The connection can be used to query or update data in other tables. The trigger then needs to be defined in the database:
@features_1581_p
@features_1584_p
The trigger can be used to veto a change, by throwing a SQL Exception.
@features_1582_h2
@features_1585_h2
Compacting a Database
@features_1583_p
@features_1586_p
Empty space in the database file is re-used automatically. To re-build the indexes, the simplest way is to delete the .index.db file while the database is closed. However in some situations (for example after deleting a lot of data in a database), one sometimes wants to shrink the size of the database (compact a database). Here is a sample function to do this:
@features_1584_p
@features_1587_p
See also the sample application org.h2.samples.Compact. The commands SCRIPT / RUNSCRIPT can be used as well to create a backup of a database and re-build the database from the script.
@features_1585_h2
@features_1588_h2
Cache Settings
@features_1586_p
@features_1589_p
The database keeps most frequently used data and index pages in the main memory. The amount of memory used for caching can be changed using the setting CACHE_SIZE. This setting can be set in the database connection URL (jdbc:h2:~/test;CACHE_SIZE=131072), or it can be changed at runtime using SET CACHE_SIZE size.
@features_1587_p
@features_1590_p
This database supports two cache page replacement algorithms: LRU (the default) and 2Q. For LRU, the pages that were least frequently used are removed from the cache if it becomes full. The 2Q algorithm is a bit more complicated: basically two queues are used. The 2Q algorithm is more resistant to table scans, however the overhead is a bit higher compared to the LRU. To use the cache algorithm 2Q, use a database URL of the form jdbc:h2:~/test;CACHE_TYPE=TQ. The cache algorithm cannot be changed once the database is open.
@features_1588_p
@features_1591_p
To get information about page reads and writes, and the current caching algorithm in use, call SELECT * FROM INFORMATION_SCHEMA.SETTINGS. The number of pages read / written is listed for the data and index file.
@fragments_1000_b
......@@ -5726,7 +5741,7 @@ Small footprint: around 1 MB jar file size
Download Beta
@mainWeb_1007_td
Version 1.1.104 (2008-11-28):
Version 1.1.105 (2008-12-19):
@mainWeb_1008_a
Windows Installer (3.1 MB)
......
......@@ -1129,1087 +1129,1093 @@ Centralリポジトリの利用
#Next Version (unreleased)
@changelog_1002_li
#When using the auto-server mode, and if the lock file was modified in the future, the wrong exception was thrown ('Connection is broken' instead of 'Error opening database: Lock file modified in the future').
@changelog_1003_h2
#Version 1.1.105 (2008-12-19)
@changelog_1004_li
#The setting STORAGE=TEXT is no longer supported.
@changelog_1003_li
@changelog_1005_li
#Deleting a database using the tool DeleteDbFiles deleted LOB files of other databases in the same directory.
@changelog_1004_li
@changelog_1006_li
#When used in a subquery, LIKE and IN(..) did not work correctly sometimes.
@changelog_1005_li
@changelog_1007_li
#The fulltext search documentation has been improved.
@changelog_1006_li
@changelog_1008_li
#ARRAY_GET returned the wrong data type (ARRAY). Now it returns VARCHAR.
@changelog_1007_li
@changelog_1009_li
#Natural join: the joined columns are not repeated any more when using SELECT *.
@changelog_1008_li
@changelog_1010_li
#User defined aggregate functions: the method getType expected internal data types instead of SQL types.
@changelog_1009_li
@changelog_1011_li
#User defined aggregate functions did not work if there was no group by expression.
@changelog_1010_li
@changelog_1012_li
#MySQL compatibility: support for := assignment as in @sum:=@sum+x
@changelog_1011_li
@changelog_1013_li
#INSERT INTO TEST(SELECT * FROM TEST) is now supported.
@changelog_1012_li
@changelog_1014_li
#Each session threw an invisible exception when garbage collected.
@changelog_1013_li
@changelog_1015_li
#Foreign key constraints that refer to a quoted column did not work.
@changelog_1014_li
@changelog_1016_li
#New meta data column INFORMATION_SCHEMA.TABLES.LAST_MODIFICATION to get the table modification counter.
@changelog_1015_li
@changelog_1017_li
#Shell: line comments didn't work correctly.
@changelog_1016_li
@changelog_1018_li
#H2 Console: Columns are now listed for up to 500 tables instead of 100.
@changelog_1017_li
@changelog_1019_li
#H2 Console: Cmd+Enter executes the current statement, Alt+Space for autocomplete.
@changelog_1018_li
@changelog_1020_li
#JaQu: the maximum length of a column can now be defined using maxLength. For an example, see Product.java (maxLength(category, 255)).
@changelog_1019_li
@changelog_1021_li
#R&\#305;dvan A&\#287;ar has completed the Turkish translation of the H2 Console. Thanks a lot!
@changelog_1020_h2
@changelog_1022_h2
#Version 1.1.104 (2008-11-28)
@changelog_1021_li
@changelog_1023_li
#If a query that was used like a table contained group by and was ordered by an expression that is not in the column list, an exception was thrown.
@changelog_1022_li
@changelog_1024_li
#JaQu: tables are now auto-created when running a query.
@changelog_1023_li
@changelog_1025_li
#The optimizer had problems with function tables (for example CSVREAD and FTL_SEARCH). A new system property h2.estimatedFunctionTableRows (default 1000) defines how many rows can be expected in the table.
@changelog_1024_li
@changelog_1026_li
#The function SUM could overflow when using large values. It returns now a data type that is safe.
@changelog_1025_li
@changelog_1027_li
#The function AVG could overflow when using large values. Fixed.
@changelog_1026_li
@changelog_1028_li
#The emergency reserve file has been removed. It didn't provide an appropriate solution for the problem. It is still possible for an application to detect and deal with the low disk space problem (deleting temporary files for example) using DatabaseEventListener.diskSpaceIsLow, but this method is now always called with stillAvailable=0.
@changelog_1027_li
@changelog_1029_li
#Build: JAVA_HOME is now automatically detected on Mac OS X.
@changelog_1028_li
@changelog_1030_li
#Testing for local connections was very slow on some systems.
@changelog_1029_li
@changelog_1031_li
#The cache memory usage calculation is more conservative.
@changelog_1030_li
@changelog_1032_li
#Allocating space got slower and slower the larger the database.
@changelog_1031_li
@changelog_1033_li
#ALTER TABLE ALTER COLUMN could throw the wrong exception in the last version (Table not found).
@changelog_1032_li
@changelog_1034_li
#Updatable result sets: the key columns can now be updated.
@changelog_1033_li
@changelog_1035_li
#The H2DatabaseProvider for ActiveObjects is now included in the tools section.
@changelog_1034_li
@changelog_1036_li
#The H2Platform for Oracle Toplink Essential has been improved a bit.
@changelog_1035_li
@changelog_1037_li
#The Windows service to start H2 didn't work in version 1.1.
@changelog_1036_li
@changelog_1038_li
#File systems with a maximum file size (for example FAT) are now supported using the file prefix 'split:'. In this case the files are split in parts of 1 GB. Example URL: jdbc:h2:split:~/db/test. If you want to split into parts of 1 MB, use jdbc:h2:split:20:~/db/test (the part size is 1 &lt;&lt; x, the default is 30 meaning 1 GB).
@changelog_1037_li
@changelog_1039_li
#The database now tries to detect if the classloader or virtual machine has almost shut down by checking if static final variables are set to null. This should help reduce exceptions when stopping the web application.
@changelog_1038_li
@changelog_1040_li
#Compatibility for MS SQL Server DATEDIFF(YYYY, .., ..)
@changelog_1039_li
@changelog_1041_li
#ResultSet.getObject for CLOB or BLOB will return a java.sql.Clob / java.sql.Blob object instead of a java.io.Reader / java.io.InputStream as in version 1.0. This behavior can be changed using the system property h2.returnLobObjects (true by default for version 1.1).
@changelog_1040_li
@changelog_1042_li
#The interface CloseListener has a new method 'remove' that is called when the trigger is dropped.
@changelog_1041_li
@changelog_1043_li
#Fulltext search: there was a memory leak when creating and dropping fulltext indexes in a loop.
@changelog_1042_h2
@changelog_1044_h2
#Version 1.1.103 (2008-11-07)
@changelog_1043_li
@changelog_1045_li
#Could not order by a formula when the formula was in the group by list but not in the select list.
@changelog_1044_li
@changelog_1046_li
#Date values that match the daylight saving time end were not allowed in times zones were the daylight saving time ends at midnight, for years larger than 2037. Example: timezone Brasilia, date 2042-10-12. This is a problem of Java, however a workaround is implemented in H2 that solves most problems (except the problems of java.util.Date itself).
@changelog_1045_li
@changelog_1047_li
#ALTER TABLE used a lot of memory when using multi-version concurrency.
@changelog_1046_li
@changelog_1048_li
#Referential integrity for in-memory databases didn't work in some cases in version 1.1.102.
@changelog_1047_li
@changelog_1049_li
#New column INFORMATION_SCHEMA.COLUMNS.SEQUENCE_NAME to get the name of the sequence for auto-increment columns.
@changelog_1048_li
@changelog_1050_li
#Aliases for built-in data types (such as MEDIUMBLOB which is an alias for BLOB) can now be re-mapped to another data type using CREATE DOMAIN. However main built-in data types (such as INTEGER) can not be re-mapped.
@changelog_1049_li
@changelog_1051_li
#The Japanese translation has been completed by Masahiro Ikemoto. Thanks a lot!
@changelog_1050_li
@changelog_1052_li
#Improved PostgreSQL compatibility for NEXTVAL and CURRVAL.
@changelog_1051_li
@changelog_1053_li
#Less heap memory is needed when multiple databases are open at the same time: The memory reserve (used to rollback after out of memory) is now global and no longer allocated for each database separately.
@changelog_1052_li
@changelog_1054_li
#New system property h2.browser to set the browser to use.
@changelog_1053_li
@changelog_1055_li
#To start the browser, java.awt.Desktop.browse is now used if available.
@changelog_1054_h2
@changelog_1056_h2
#Version 1.1.102 (2008-10-24)
@changelog_1055_li
@changelog_1057_li
#The French translation of the H2 Console has been improved by Olivier Parent. Thanks a lot!
@changelog_1056_li
@changelog_1058_li
#There was a memory leak when creating and dropping tables and indexes in a loop (persistent database only).
@changelog_1057_li
@changelog_1059_li
#SET LOG 2 was not effective if executed after opening the database.
@changelog_1058_li
@changelog_1060_li
#Translating the H2 Console is now simpler.
@changelog_1059_li
@changelog_1061_li
#Common exception (error code 23*) are no longer written to the .trace.db file by default.
@changelog_1060_li
@changelog_1062_li
#In-memory databases don't write LOBs to files any longer.
@changelog_1061_li
@changelog_1063_li
#Self referencing constraints didn't restrict deleting rows that reference itself if there is another row that references it.
@changelog_1062_li
@changelog_1064_li
#ResultSetMetaData.getColumnName now returns the alias name except for columns.
@changelog_1063_li
@changelog_1065_li
#Temporary files are now deleted when the database is closed, even if they were not garbage collected so far.
@changelog_1064_h2
@changelog_1066_h2
#Version 1.1.101 (2008-10-17)
@changelog_1065_li
@changelog_1067_li
#Errors with code 42000 - 42999 are no longer written to the trace file by default.
@changelog_1066_li
@changelog_1068_li
#Queries with more than 10 tables are now faster.
@changelog_1067_li
@changelog_1069_li
#Opening a connection with AUTO_SERVER=TRUE is now fast when the database is already open in another process (less than 0.01 seconds instead of 2 seconds).
@changelog_1068_li
@changelog_1070_li
#IF [NOT] EXISTS is supported for named constraints in ALTER TABLE ... ADD/DROP CONSTRAINT.
@changelog_1069_li
@changelog_1071_li
#The error messages have been translated to Spanish by Dario V. Fassi. Thanks a lot!
@changelog_1070_li
@changelog_1072_li
#Linked tables: the automatic connection sharing didn't work. Actually the system property h2.shareLinkedConnections was working in the opposite direction: it was disabled when set to true. Now it works as expected.
@changelog_1071_li
@changelog_1073_li
#Opening large database is now faster.
@changelog_1072_li
@changelog_1074_li
#New system property h2.socketConnectTimeout, the timeout in milliseconds to connect to a server. The default is 2000 (2 seconds).
@changelog_1073_li
@changelog_1075_li
#The wrong parameters were bound to subqueries with parameters, specially when using IN(SELECT ...) and IN(...).
@changelog_1074_li
@changelog_1076_li
#Unset parameters were not detected when the query was re-compiled.
@changelog_1075_li
@changelog_1077_li
#New functions ISO_YEAR, ISO_WEEK, ISO_DAY_OF_WEEK. Thanks a lot to Robert Rathsack for implementing those!
@changelog_1076_li
@changelog_1078_li
#The date functions DAYOFYEAR, DAYOFMONTH, DAYOFWEEK are now called DAY_OF_YEAR, DAY_OF_MONTH, DAY_OF_WEEK (the old names still work).
@changelog_1077_li
@changelog_1079_li
#An out of memory error while deleting or updating many rows could result in a strange exception.
@changelog_1078_li
@changelog_1080_li
#Linked tables: compatibility with MS SQL Server has been improved.
@changelog_1079_li
@changelog_1081_li
#Renaming tables that have foreign keys with cascade didn't work correctly.
@changelog_1080_li
@changelog_1082_li
#The auto-reconnect feature didn't work when using the auto-server mode. Fixed.
@changelog_1081_li
@changelog_1083_li
#Fulltext search: new method FT_DROP_INDEX.
@changelog_1082_li
@changelog_1084_li
#The optimization to group using an index didn't work in some cases in version 1.1 (see also system property h2.optimizeGroupSorted).
@changelog_1083_li
@changelog_1085_li
#OSGi meta data is included in the manifest file. An OSGi BundleActivator is included: it loads the database driver when starting the bundle, and unloads it when stopping the bundle.
@changelog_1084_li
@changelog_1086_li
#The default value for MAX_MEMORY_UNDO is now 50000.
@changelog_1085_li
@changelog_1087_li
#For alias columns, ResultSetMetaData.getTableName() and getColumnName() now return the real table and column name in the default mode.
@changelog_1086_li
@changelog_1088_li
#In SQL scripts created with SCRIPT TO, schemas are now only created if they don't exist yet.
@changelog_1087_li
@changelog_1089_li
#After re-connecting to a database, the database event listener (if set) is informed about it.
@changelog_1088_li
@changelog_1090_li
#Local temporary tables now support indexes. Thanks a lot to Matt Roy!
@changelog_1089_li
@changelog_1091_li
#RUNSCRIPT no longer uses a temporary file.
@changelog_1090_li
@changelog_1092_li
#New system table INFORMATION_SCHEMA.SESSION_STATE containing the SQL statements that make up the session state. The list currently contains variables (SET @..) and local temporary tables (without data).
@changelog_1091_li
@changelog_1093_li
#After an automatic re-connect, part of the session state stays (the part that is stored in the SESSION_STATE table).
@changelog_1092_li
@changelog_1094_li
#The build didn't work if the directory temp didn't exist before.
@changelog_1093_li
@changelog_1095_li
#New system property h2.maxReconnect (default 3) to limit the number of re-connects for the same SQL statement (this is usually only important for SHUTDOWN).
@changelog_1094_li
@changelog_1096_li
#WHERE .. IN (SELECT ...) could throw a NullPointerException.
@changelog_1095_li
@changelog_1097_li
#Improved Glassfish / Toplink support in H2Platform thanks to Marcio Borges from Brazil. Thanks a lot!
@changelog_1096_h2
@changelog_1098_h2
#Version 1.1.100 (2008-10-04)
@changelog_1097_li
@changelog_1099_li
#In version 1.1, the following system properties are now enabled by default: h2.lobFilesInDirectories, h2.optimizeGroupSorted, h2.optimizeInJoin, h2.shareLinkedConnections
@changelog_1098_li
@changelog_1100_li
#The H2 Console tool now works with the JDBC-ODBC bridge.
@changelog_1099_li
@changelog_1101_li
#The H2 Console tool now supports command line options to start things separately.
@changelog_1100_li
@changelog_1102_li
#Large objects did not work for in-memory databases in server mode in Linux.
@changelog_1101_li
@changelog_1103_li
#Connections from a local address other than 'localhost' were not allowed if remote connections were disabled. This was always a problem, but only got visible in the last release because the server no longer connects to 'localhost' if networked.
@changelog_1102_li
@changelog_1104_li
#The h2console.war can now be built using the Java build.
@changelog_1103_li
@changelog_1105_li
#By default, databases are shared in the same process. For read-only databases this causes unnecessary synchronization, but safes memory. If you want that each connection opens its own database, append ;OPEN_NEW=TRUE to the database URL.
@changelog_1104_li
@changelog_1106_li
#New auto-reconnect feature will cause the JDBC driver to reconnect to the database if the connection is lost. To enable, append ;AUTO_RECONNECT=TRUE to the database URL. This is specially helpful when using AUTO_SERVER. AUTO_SERVER automatically uses auto-reconnect.
@changelog_1105_li
@changelog_1107_li
#CreateCluster: the property 'serverlist' is now called 'serverList'.
@changelog_1106_li
@changelog_1108_li
#The ConvertTraceFile tool could not parse some files because the trace mechanism did not encode prepared statement parameters.
@changelog_1107_li
@changelog_1109_li
#Databases names can now be one character long (the minimum size used to be 2 characters).
@changelog_1108_h2
@changelog_1110_h2
#Version 1.0.79 (2008-09-26)
@changelog_1109_li
@changelog_1111_li
#Linked tables that point to the same database can now share the connection within the same database. Access to the same connection is serialized. To enable this feature, set the system property h2.shareLinkedConnections to true.
@changelog_1110_li
@changelog_1112_li
#Multiple processes can now access the same database without having to explicitly start the server. To do that, append ;AUTO_SERVER=TRUE to the database URL. In this case, the server is started automatically if the connection is in embedded mode, and the server mode is used if a server is running. If the process that opened the first connection is closed, the other client need to reconnect (there is no automatic re-connect so far). Remote connections are allowed, but only to this database.
@changelog_1111_li
@changelog_1113_li
#The server tool now displays the correct IP address if networked.
@changelog_1112_li
@changelog_1114_li
#Can now start a TCP server with port 0 (automatically select a port).
@changelog_1113_li
@changelog_1115_li
#Result sets with just a unique index can now be updated (previously a primary key was required).
@changelog_1114_li
@changelog_1116_li
#LINKED TABLE: the schema name can now be set. When multiple tables exist in different schema, and the schema name is not set, an exception is thrown.
@changelog_1115_li
@changelog_1117_li
#LINKED TABLE: worked around a bug in Oracle with the CHAR data type.
@changelog_1116_li
@changelog_1118_li
#Faster hash code calculation for large binary arrays.
@changelog_1117_li
@changelog_1119_li
#Faster storage re-use algorithm thanks to Greg Dhuse from cleversafe.com.
@changelog_1118_li
@changelog_1120_li
#The database supports the SHOW command for better MySQL and PostgreSQL compatibility.
@changelog_1119_li
@changelog_1121_li
#The H2 Console now abbreviates large texts in results.
@changelog_1120_li
@changelog_1122_li
#Multiple UNION queries could not be used in derived tables.
@changelog_1121_li
@changelog_1123_li
#Linked tables can now be read-only.
@changelog_1122_li
@changelog_1124_li
#Temporary linked tables are now supported.
@changelog_1123_li
@changelog_1125_li
#It was possible to create tables in read-only databases.
@changelog_1124_li
@changelog_1126_li
#SET SCHEMA_SEARCH_PATH is now documented.
@changelog_1125_li
@changelog_1127_li
#SET SCHEMA did not work for views.
@changelog_1126_li
@changelog_1128_li
#Row level locking for MVCC is now enabled. The exception 'Concurrent update in table ...' is still thrown, but only after the lock timeout.
@changelog_1127_li
@changelog_1129_li
#The maximum log file size setting was ignored for large databases.
@changelog_1128_li
@changelog_1130_li
#Multi-Version Concurrency (MVCC) may no longer be used when using the multi-threaded kernel feature (MULTI_THREADED). An exception is thrown when trying to connect with both settings. Additional synchronization is required before those features can be used together.
@changelog_1129_li
@changelog_1131_li
#The data type JAVA_OBJECT could not be used in updatable result sets.
@changelog_1130_li
@changelog_1132_li
#The system property h2.optimizeInJoin did not work correctly.
@changelog_1131_li
@changelog_1133_li
#Conditions such as ID=? AND ID>? were slow.
@changelog_1132_h2
@changelog_1134_h2
#Version 1.0.78 (2008-08-28)
@changelog_1133_li
@changelog_1135_li
#The documentation no longer uses a frameset (except the Javadocs).
@changelog_1134_li
@changelog_1136_li
#When using DB_CLOSE_DELAY, sometimes a NullPointerException is thrown when the database is opened almost at the same time as it is closed automatically. Thanks a lot to Dmitry Pekar for finding this!
@changelog_1135_li
@changelog_1137_li
#Java methods with variable number of parameters can now be used (for Java 1.5 or newer).
@changelog_1136_li
@changelog_1138_li
#The Japanese translation has been improved by Masahiro Ikemoto. Thanks a lot!
@changelog_1137_li
@changelog_1139_li
#The H2 Console replaced an empty user name with a single space.
@changelog_1138_li
@changelog_1140_li
#The build target 'build jarSmall' now includes the embedded database.
@changelog_1139_li
@changelog_1141_li
#JdbcDataSource now keeps the password in a char array where possible.
@changelog_1140_li
@changelog_1142_li
#ResultSet.absolute did not always work with large result sets.
@changelog_1141_li
@changelog_1143_li
#Column aliases can now be used in GROUP BY and HAVING.
@changelog_1142_li
@changelog_1144_li
#Jason Brittain has contributed MySQL date functions. Thanks a lot! They are not in the h2.jar file currently, but in src/tools/org/h2/mode/FunctionsMySQL.java. To install, add this class to the classpath and call FunctionsMySQL.register(conn) in the Java code.
@changelog_1143_h2
@changelog_1145_h2
#Version 1.0.77 (2008-08-16)
@changelog_1144_li
@changelog_1146_li
#JaQu is now using prepared statements and supports Date, Time, Timestamp.
@changelog_1145_li
@changelog_1147_li
#When using remote in-memory databases, large LOB objects did not work.
@changelog_1146_li
@changelog_1148_li
#Timestamp columns such as TIMESTAMP(6) were not compatible to other database.
@changelog_1147_li
@changelog_1149_li
#Opening a large database was slow if there was a problem opening the previous time.
@changelog_1148_li
@changelog_1150_li
#NOT IN(SELECT ...) was incorrect if the subquery returns no rows.
@changelog_1149_li
@changelog_1151_li
#CREATE TABLE AS SELECT did not work correctly in the multi-version concurrency mode.
@changelog_1150_li
@changelog_1152_li
#Support a comma before closing a list, as in: create table test(id int,)
@changelog_1151_li
@changelog_1153_li
#MySQL compatibility: linked tables had lower case column names on some systems.
@changelog_1152_li
@changelog_1154_li
#DB2 compatibility: the DB2 fetch-first-clause is supported.
@changelog_1153_li
@changelog_1155_li
#Oracle compatibility: old style outer join syntax using (+) did work correctly sometimes.
@changelog_1154_li
@changelog_1156_li
#ResultSet.setFetchSize is now supported.
@changelog_1155_li
@changelog_1157_li
#It has been reported that when using Install4j on some Linux systems and enabling the 'pack200' option, the h2.jar becomes corrupted by the install process, causing application failure. A workaround is to add an empty file h2.jar.nopack next to the h2.jar file. The reason for this problem is not known.
@changelog_1156_h2
@changelog_1158_h2
#Version 1.0.76 (2008-07-27)
@changelog_1157_li
@changelog_1159_li
#The comment of a domain (user defined data type) is now used as the default column comment when creating a column with this domain.
@changelog_1158_li
@changelog_1160_li
#Invalid database names are now detected and a better error message is thrown.
@changelog_1159_li
@changelog_1161_li
#ResultSetMetaData.getColumnClassName now returns the correct class name for BLOB and CLOB.
@changelog_1160_li
@changelog_1162_li
#Fixed the Oracle mode: Oracle allows multiple rows only where all columns of the unique index are NULL.
@changelog_1161_li
@changelog_1163_li
#There is a problem with Hibernate when using Boolean columns. A patch for Hibernate has been submitted at http://opensource.atlassian.com/projects/hibernate/browse/HHH-3401
@changelog_1162_li
@changelog_1164_li
#ORDER BY on tableName.columnName didn't work correctly if the column name was also used as an alias.
@changelog_1163_li
@changelog_1165_li
#H2 Console: The progress display when opening a database has been improved.
@changelog_1164_li
@changelog_1166_li
#The error message when the server doesn't start has been improved.
@changelog_1165_li
@changelog_1167_li
#Key values can now be changed in updatable result sets.
@changelog_1166_li
@changelog_1168_li
#Changes in updatable result sets are now visible even when resetting the result set.
@changelog_1167_li
@changelog_1169_li
#Temporary files were sometimes deleted too late when executing large insert, update, or delete operations.
@changelog_1168_li
@changelog_1170_li
#The database file was growing after deleting many rows, and after large update operations.
@changelog_1169_h2
@changelog_1171_h2
#Version 1.0.75 (2008-07-14)
@changelog_1170_li
@changelog_1172_li
#Multi version concurrency (MVCC): when a row was updated or deleted, but this change was rolled back, the row was not visible by other sessions if no index was used to access it. Fixed.
@changelog_1171_li
@changelog_1173_li
#Views with multiple joined tables (where one was an outer join) couldn't be used in some cases. Fixed.
@changelog_1172_li
@changelog_1174_li
#The CSVREAD method did not process NULL correctly when using a whitespace field separator.
@changelog_1173_li
@changelog_1175_li
#Fixed the Oracle mode: Oracle allows multiple rows with NULL in a unique index.
@changelog_1174_li
@changelog_1176_li
#Running out of memory could result in incomplete transactions or corrupted databases. Fixed.
@changelog_1175_li
@changelog_1177_li
#When using order by in a query that uses the same table multiple times, the order could be incorrect. Fixed.
@changelog_1176_li
@changelog_1178_li
#Referential constraint checking improvement: now the constraint is only checked if the key column values change.
@changelog_1177_li
@changelog_1179_li
#Some database metadata calls returned the wrong data type for DATA_TYPE columns.
@changelog_1178_li
@changelog_1180_li
#The Lucene fulltext index was empty when opening a database with fulltext index enabled, and re-indexing it didn't work. Fixed.
@changelog_1179_li
@changelog_1181_li
#The character '$' could not be used in identifier names (table name, column names and so on). Fixed.
@changelog_1180_li
@changelog_1182_li
#The new method org.h2.tools.Server.startWebServer(conn) starts the H2 Console to inspect a database while debugging.
@changelog_1181_li
@changelog_1183_li
#Stopping a WebServer didn't always work. Fixed.
@changelog_1182_h2
@changelog_1184_h2
#Version 1.0.74 (2008-06-21)
@changelog_1183_li
@changelog_1185_li
#Work on row level locking has been started (but there is nothing usable yet).
@changelog_1184_li
@changelog_1186_li
#JaQu (Java Query), a tool similar to LINQ (Language Integrated Query; from Microsoft) is now included under src/tools/org/h2/jaqu. A small sample application is included under src/test/org/h2/test/jaqu.
@changelog_1185_li
@changelog_1187_li
#The source code is now switched to Java 1.6 by default. To switch back to Java 1.4, run 'build compile'. The h2.jar file is still Java 1.4.
@changelog_1186_li
@changelog_1188_li
#The ChangePassword tool is now called ChangeFileEncryption.
@changelog_1187_li
@changelog_1189_li
#It is no longer allowed to create columns with the data type NULL. Also, it is no longer allowed to convert a column to the data type NULL. This was possible before but caused data loss.
@changelog_1188_li
@changelog_1190_li
#When using computed columns or default values with a different data type than the column data type, a class cast exception could occur. Fixed.
@changelog_1189_li
@changelog_1191_li
#Opening databases larger than 1 GB was sometimes very slow if a lot of data was deleted previously. Fixed.
@changelog_1190_li
@changelog_1192_li
#RUNSCRIPT could throw a NullPointerException if the script name was an expression.
@changelog_1191_li
@changelog_1193_li
#Improved compatibility. New compatibility modes for Oracle and Derby. New compatibility flag uniqueIndexNullDistinct to only allow one row with 'NULL' in a unique index. This flag is enabled for Derby, Oracle, MSSQLServer, and HSQLDB.
@changelog_1192_li
@changelog_1194_li
#Linked tables: To view the statements that are executed against the target table, set the trace level to 3.
@changelog_1193_li
@changelog_1195_li
#RunScript tool: new options to show and check the results of queries.
@changelog_1194_li
@changelog_1196_li
#Deadlocks are now detected. One transaction is rolled back automatically.
@changelog_1195_li
@changelog_1197_li
#The Lucene fulltext index was always re-created when opening a database with fulltext index enabled.
@changelog_1196_li
@changelog_1198_li
#Support for overloaded Java methods. A user defined function can now be bound to multiple Java methods, if the Java methods have the same name but a different number of parameters. Thanks to Gary Tong for providing a patch!
@changelog_1197_h2
@changelog_1199_h2
#Version 1.0.73 (2008-05-31)
@changelog_1198_li
@changelog_1200_li
#ParameterMetaData now returns the right data type for most conditions, as in WHERE ID=?.
@changelog_1199_li
@changelog_1201_li
#The table SYSTEM_RANGE now supports expressions and parameters.
@changelog_1200_li
@changelog_1202_li
#New column INFORMATION_SCHEMA.CONSTRAINTS.UNIQUE_INDEX_NAME that contains the name of the unique index used to enforce this constraint, if there is such an index.
@changelog_1201_li
@changelog_1203_li
#SET QUERY_TIMEOUT and Statement.setQueryTimeout no longer commits a transaction. The same applies to SET @VARIABLE, SET LOCK_TIMEOUT, SET TRACE_LEVEL_*, SET THROTTLE, and SET PATH.
@changelog_1202_li
@changelog_1204_li
#The SCRIPT command does now emit IF NOT EXISTS for CREATE ROLE.
@changelog_1203_li
@changelog_1205_li
#MySQL compatibility: auto_increment column are no longer automatically converted to primary key columns.
@changelog_1204_li
@changelog_1206_li
#PostgreSQL compatibility: support for BOOL_OR and BOOL_AND aggregate functions.
@changelog_1205_li
@changelog_1207_li
#Negative scale values for DECIMAL or NUMBER columns are now supported in regular tables and in linked tables.
@changelog_1206_li
@changelog_1208_li
#A role or right can now be granted or revoked multiple times without getting an exception.
@changelog_1207_li
@changelog_1209_li
#Infinite numbers in SQL scripts are listed as POWER(0, -1)), negative infinite as (-POWER(0, -1)), and NaN (not a number) as SQRT(-1).
@changelog_1208_li
@changelog_1210_li
#The special double and float values 'NaN' (not a number) did not work correctly when sorting or comparing.
@changelog_1209_li
@changelog_1211_li
#The fulltext search did not support CLOB data types.
@changelog_1210_li
@changelog_1212_li
#If the drive with the database files was disconnected or unmounted while writing, sometimes a stack overflow exception was thrown instead of a IO exception.
@changelog_1211_li
@changelog_1213_li
#The H2 Console could not be shut down from within the tool if the browser supports keepAlive (most browsers do).
@changelog_1212_li
@changelog_1214_li
#If the password was passed as a char array, it was kept in an internal buffer longer than required. Theoretically the password could have been stolen if the main memory was swapped to disk before the garbage collection was run.
@changelog_1213_h2
@changelog_1215_h2
#Version 1.0.72 (2008-05-10)
@changelog_1214_li
@changelog_1216_li
#Some databases could not be opened when appending ;RECOVER=1 to the database URL.
@changelog_1215_li
@changelog_1217_li
#The Japanese translation of the error messages and the H2 Console has been completed by Masahiro Ikemoto (Arizona Design Inc.)
@changelog_1216_li
@changelog_1218_li
#Updates made to updatable rows are now visible within the same result set. DatabaseMetaData.ownUpdatesAreVisible now returns true.
@changelog_1217_li
@changelog_1219_li
#ParameterMetaData now returns the correct data for INSERT and UPDATE statements.
@changelog_1218_li
@changelog_1220_li
#H2 Shell: DESCRIBE now supports an schema name.
@changelog_1219_li
@changelog_1221_li
#A subset of the PostgreSQL 'dollar quoting' feature is now supported.
@changelog_1220_li
@changelog_1222_li
#SLF4J is now supported by using adding TRACE_LEVEL_FILE=4 to the database URL.
@changelog_1221_li
@changelog_1223_li
#The recovery tool did not work if the table name contained spaces or if there was a comment on the table.
@changelog_1222_li
@changelog_1224_li
#Triggers are no longer executed when changing the table structure (ALTER TABLE).
@changelog_1223_li
@changelog_1225_li
#When setting BLOB or CLOB values larger than 65 KB using a remote connection, temporary files were kept on the client longer than required (until the connection was closed or the object is garbage collected). Now they are removed as soon as the PreparedStatement is closed, or when the value is overwritten.
@changelog_1224_li
@changelog_1226_li
#Statements can now be canceled remotely (when using remote connections).
@changelog_1225_li
@changelog_1227_li
#The Shell tool now uses java.io.Console to read the password when using JDK 1.6
@changelog_1226_li
@changelog_1228_li
#When using read-only databases and setting LOG=2, an exception was written to the trace file when closing the database. Fixed.
@changelog_1227_h2
@changelog_1229_h2
#Version 1.0.71 (2008-04-25)
@changelog_1228_li
@changelog_1230_li
#H2 is now dual-licensed under the Eclipse Public License (EPL) and the old 'H2 License' (which is basically MPL).
@changelog_1229_li
@changelog_1231_li
#Sometimes an exception 'File ID mismatch' or 'try to add a record twice' occurred after large records (8 KB or larger) are updated or deleted. See also http://code.google.com/p/h2database/issues/detail?id=22
@changelog_1230_li
@changelog_1232_li
#H2 Console: The tools can now be translated (it didn't work in the last release).
@changelog_1231_li
@changelog_1233_li
#New traditional Chinese translation. Thanks a lot to Derek Chao!
@changelog_1232_li
@changelog_1234_li
#Indexes were not used when enabling the optimization for IN(SELECT...) (system property h2.optimizeInJoin).
@changelog_1233_h2
@changelog_1235_h2
#Version 1.0.70 (2008-04-20)
@changelog_1234_li
@changelog_1236_li
#The plan is to dual-license H2. The additional license is EPL (Eclipse Public License). The current license (MPL, Mozilla Public License) will stay. Current users are not affected because they can keep MPL. EPL is very similar to MPL, the only bigger difference is related to patents (EPL is a bit more business friendly in this regard). See also http://opensource.org/licenses/eclipse-1.0.php, http://www.eclipse.org/legal/eplfaq.php (FAQ), http://blogs.zdnet.com/Burnette/?p=131
@changelog_1235_li
@changelog_1237_li
#Multi version concurrency (MVCC): when a row was updated, and the updated column was not indexed, this update was visible sometimes for other sessions even if it was not committed.
@changelog_1236_li
@changelog_1238_li
#Calling SHUTDOWN on one connection and starting a query on another connection concurrently could result in a Java level deadlock.
@changelog_1237_li
@changelog_1239_li
#New system property h2.enableAnonymousSSL (default: true) to enable anonymous SSL connections.
@changelog_1238_li
@changelog_1240_li
#The precision if SUBSTR is now calculated if possible.
@changelog_1239_li
@changelog_1241_li
#The autocomplete in the H2 Console has been improved a bit.
@changelog_1240_li
@changelog_1242_li
#The tools in the H2 Console are now translatable.
@changelog_1241_li
@changelog_1243_li
#The servlet and lucene jar files are now automatically downloaded when building.
@changelog_1242_li
@changelog_1244_li
#The code switch tool has been replaced by a simpler tool called SwitchSource that just uses find and replace.
@changelog_1243_li
@changelog_1245_li
#Started to write a Ant replacement ('JAnt') that uses pure Java build definitions. Advantages: ability to debug the build, extensible, flexible, no XML, a bit faster. Future plan: support creating custom h2 distributions (for embedded use). Maybe create a new project 'Jant' or 'Javen' if other people are interested.
@changelog_1244_li
@changelog_1246_li
#The jar file is now about 10% smaller because the variable debugging info is no longer included. The source file and line number debugging info is still included. If required, the jar file size of the full version can be further reduced to about 720 KB using 'build jarSmall' or even more by removing unneeded components.
@changelog_1245_li
@changelog_1247_li
#Added shell scripts run.sh and build.sh. chmod +x is required, but otherwise it should work. Feedback or improvements are welcome!
@changelog_1246_li
@changelog_1248_li
#Databases in zip files: large queries are now supported. Temp files are created in the temp directory if required. The documentation how to create the zip file has been corrected.
@changelog_1247_li
@changelog_1249_li
#Invalid inline views threw confusing SQL exceptions.
@changelog_1248_li
@changelog_1250_li
#The Japanese translation of the error messages and the H2 Console has been improved. Thanks a lot to Masahiro IKEMOTO.
@changelog_1249_li
@changelog_1251_li
#Optimization for MIN() and MAX() when using MVCC.
@changelog_1250_li
@changelog_1252_li
#To protect against remote brute force password attacks, the delay after each unsuccessful login now gets double as long. New system properties h2.delayWrongPasswordMin and h2.delayWrongPasswordMax.
@changelog_1251_li
@changelog_1253_li
#After setting the query timeout and then resetting it, the next query would still timeout. Fixed.
@changelog_1252_li
@changelog_1254_li
#Adding a IDENTITY column to a table with data threw a lock timeout.
@changelog_1253_li
@changelog_1255_li
#OutOfMemoryError could occur when using EXISTS or IN(SELECT ..).
@changelog_1254_li
@changelog_1256_li
#The built-in connection pool is not called JdbcConnectionPool. The API and documentation has been changed.
@changelog_1255_li
@changelog_1257_li
#The ConvertTraceFile tool now generates SQL statement statistics at the end of the SQL script file (similar to the profiling data generated when using java -Xrunhprof).
@changelog_1256_li
@changelog_1258_li
#Nested joins are now supported (A JOIN B JOIN C ON .. ON ..)
@changelog_1257_h2
@changelog_1259_h2
#Version 1.0.69 (2008-03-29)
@changelog_1258_li
@changelog_1260_li
#Most command line tools can now be called from within the H2 Console.
@changelog_1259_li
@changelog_1261_li
#A new Shell tools is now included (org.h2.tools.Shell) to query a database from the command line.
@changelog_1260_li
@changelog_1262_li
#The command line options in the tools have changed: instead of '-log true' now '-trace' is used. Also, '-ifExists', '-tcpSSL' and '-tcpAllowOthers' and so on have changed: now the 'true' is no longer needed. The old behavior is still supported.
@changelog_1261_li
@changelog_1263_li
#New system property h2.sortNullsHigh to invert the default sorting behavior for NULL. The default didn't change.
@changelog_1262_li
@changelog_1264_li
#Performance was very slow when using LOG=2 and deleting or updating all rows of a table in a loop. Fixed.
@changelog_1263_li
@changelog_1265_li
#ALTER TABLE or CREATE TABLE now support parameters for the password field.
@changelog_1264_li
@changelog_1266_li
#The linear hash has been removed. It was always slower than the b-tree index, and there were some bugs that would be hard to fix.
@changelog_1265_li
@changelog_1267_li
#TRACE_LEVEL_ settings are no longer persistent. This was a problem when database initialization code caused a lot of trace output.
@changelog_1266_li
@changelog_1268_li
#Fulltext search (native implementation): The words table is no longer an in-memory table because this caused memory problems in some cases.
@changelog_1267_li
@changelog_1269_li
#It was possible to create a role with the name as an existing user (but not vice versa). This is not allowed any more.
@changelog_1268_li
@changelog_1270_li
#The recovery tool didn't work correctly for tables without rows.
@changelog_1269_li
@changelog_1271_li
#For years below 1, the YEAR method didn't return the correct value, and the conversion from date and timestamp to varchar was incorrect.
@changelog_1270_li
@changelog_1272_li
#CSVWRITE caused a NullPointerException when not specifying a nullString.
@changelog_1271_li
@changelog_1273_li
#When a log file switch occurred just after a truncate table or drop table statement, the database could not be started normally (RECOVER=1 was required). Fixed.
@changelog_1272_li
@changelog_1274_li
#When a log file switch occurred in the middle of a sequence flush (sequences are only flushed every 32 values by default), the sequence value was lost. Fixed.
@changelog_1273_li
@changelog_1275_li
#Altering a sequence didn't unlock the system table when autocommit switched off.
@changelog_1274_h2
@changelog_1276_h2
#Version 1.0.68 (2008-03-18)
@changelog_1275_li
@changelog_1277_li
#Very large SELECT DISTINCT and UNION EXCEPT queries are now supported, however this feature is disabled by default. To enable it, set the system property h2.maxMemoryRowsDistinct to a lower value, for example 10000.
@changelog_1276_li
@changelog_1278_li
#A error is now thrown when trying to call a method inside a trigger that implicitly commits the current transaction, if an object is locked.
@changelog_1277_li
@changelog_1279_li
#Unused LOB files were deleted much too late. Now they are deleted if no longer referenced in memory.
@changelog_1278_li
@changelog_1280_li
#ALTER SEQUENCE and ALTER TABLE ALTER COLUMN RESTART can now be used inside a transaction.
@changelog_1279_li
@changelog_1281_li
#New system property h2.aliasColumnName. When enabled, aliased columns (as in SELECT ID AS I FROM TEST) return the real table and column name in ResultSetMetaData.getTableName() and getColumnName(). This is disabled by default for compatibility with other databases (HSQLDB, Apache Derby, PostgreSQL, some version of MySQL). In version 1.1 this setting will be enabled.
@changelog_1280_li
@changelog_1282_li
#When using encrypted databases, and using the wrong file password, the log file was renamed if the database was not already open. Fixed.
@changelog_1281_li
@changelog_1283_li
#Improved performance when using lob files in directories (however this is still disabled by default)
@changelog_1282_li
@changelog_1284_li
#H2 Console: autocomplete didn't work with very large scripts. Fixed.
@changelog_1283_li
@changelog_1285_li
#Fulltext search: new method SEARCH_DATA that returns the column names and primary keys as arrays.
@changelog_1284_li
@changelog_1286_li
#New experimental optimization for GROUP BY queries if an index can be used that matches the group by columns. To enable this optimization, set the system property h2.optimizeGroupSorted to true.
@changelog_1285_li
@changelog_1287_li
#When using multi-version concurrency (MVCC=TRUE), duplicate rows could appear in the result set when running queries with uncommitted changes in the same session.
@changelog_1286_li
@changelog_1288_li
#H2 Console: remote connections were very slow because getHostName/getRemoteHost was used. Fixed (now using getHostAddress/getRemoteAddr.
@changelog_1287_li
@changelog_1289_li
#H2 Console: on Linux, Firefox, Konqueror, or Opera (in this order) are now started if available. This has been tested on Ubuntu.
@changelog_1288_li
@changelog_1290_li
#H2 Console: the start window works better with IKVM
@changelog_1289_li
@changelog_1291_li
#H2 Console: improved compatibility with Safari (Safari requires keep-alive)
@changelog_1290_li
@changelog_1292_li
#Random: the process didn't stop if generating the random seed using the standard way (SecureRandom.generateSeed) was very slow. Now using a daemon thread to avoid this problem.
@changelog_1291_li
@changelog_1293_li
#SELECT UNION with a different number of ORDER BY columns did throw an ArrayIndexOutOfBoundsException.
@changelog_1292_li
@changelog_1294_li
#When using a view, the column precision was changed to the default scale for some data types.
@changelog_1293_li
@changelog_1295_li
#CSVWRITE now supports a 'null string' that is used for parsing and writing NULL.
@changelog_1294_li
@changelog_1296_li
#Some long running queries could not be canceled.
@changelog_1295_li
@changelog_1297_li
#Queries with many outer join tables were very slow. Fixed.
@changelog_1296_li
@changelog_1298_li
#The performance of text comparison has been improved when using locale sensitive string comparison (SET COLLATOR). Now CollationKey is used with a LRU cache. The default cache size is 10000, and can be changed using the system property h2.collatorCacheSize. Use 0 to disable the cache.
@changelog_1297_li
@changelog_1299_li
#UPDATE SET column=DEFAULT is now supported.
@changelog_1298_h2
@changelog_1300_h2
#Version 1.0.67 (2008-02-22)
@changelog_1299_li
@changelog_1301_li
#New function FILE_READ to read a file or from an URL. Both binary and text data is supported.
@changelog_1300_li
@changelog_1302_li
#CREATE TABLE AS SELECT now supports specifying the column list and data types.
@changelog_1301_li
@changelog_1303_li
#Connecting to a TCP server and at shutting it down at the same time could cause a Java level deadlock.
@changelog_1302_li
@changelog_1304_li
#A user now has all rights on his own local temporary tables.
@changelog_1303_li
@changelog_1305_li
#The CSV tool now supports a custom lineSeparator.
@changelog_1304_li
@changelog_1306_li
#When using multiple connections, empty space was reused too early sometimes. This could corrupt the database when recovering.
@changelog_1305_li
@changelog_1307_li
#The H2 Console has been translated to Dutch. Thanks a lot to Remco Schoen!
@changelog_1306_li
@changelog_1308_li
#Databases can now be opened even if trigger classes are not in the classpath. The exception is thrown when trying to fire the trigger.
@changelog_1307_li
@changelog_1309_li
#Opening databases with ACCESS_MODE_DATA=r is now supported. In this case the database is read-only, but the files don't not need to be read-only.
@changelog_1308_li
@changelog_1310_li
#Security: The database now waits 200 ms before throwing an exception if the user name or password don't match, to slow down dictionary attacks.
@changelog_1309_li
@changelog_1311_li
#The value cache is now a soft reference cache. This should help save memory.
@changelog_1310_li
@changelog_1312_li
#CREATE INDEX on a table with many rows could run out of memory. Fixed.
@changelog_1311_li
@changelog_1313_li
#Large result sets are now a bit faster.
@changelog_1312_li
@changelog_1314_li
#ALTER TABLE ALTER COLUMN RESTART and ALTER SEQUENCE now support parameters (any expressions).
@changelog_1313_li
@changelog_1315_li
#When setting the base directory on the command line, the user directory prefix ('~') was ignored.
@changelog_1314_li
@changelog_1316_li
#The DbStarter servlet didn't start the TCP listener even if configured.
@changelog_1315_li
@changelog_1317_li
#Statement.setQueryTimeout() is now supported.
@changelog_1316_li
@changelog_1318_li
#New session setting QUERY_TIMEOUT, and new system property h2.maxQueryTimeout.
@changelog_1317_li
@changelog_1319_li
#Changing the transaction log level (SET LOG) is now written to the trace file by default.
@changelog_1318_li
@changelog_1320_li
#In a SQL script, primary key constraints are now ordered before foreign key constraints.
@changelog_1319_li
@changelog_1321_li
#It was not possible to create a referential constraint to a table in a different schema in some situations.
@changelog_1320_li
@changelog_1322_li
#The H2 Console was slow when the database contains many tables. Now the column names are not shown in this case.
@changelog_1321_h2
@changelog_1323_h2
#Version 1.0.66 (2008-02-02)
@changelog_1322_li
@changelog_1324_li
#There is a new online error analyzer tool.
@changelog_1323_li
@changelog_1325_li
#H2 Console: stack traces are now links to the source code in the source repository (H2 database only).
@changelog_1324_li
@changelog_1326_li
#CHAR data type equals comparison was case insensitive instead of case sensitive.
@changelog_1325_li
@changelog_1327_li
#The exception 'Value too long for column' now includes the data.
@changelog_1326_li
@changelog_1328_li
#The table name was missing in the documentation of CREATE INDEX.
@changelog_1327_li
@changelog_1329_li
#Better support for IKVM (www.ikvm.net): the H2 Console now opens a browser window.
@changelog_1328_li
@changelog_1330_li
#The cache size was not correctly calculated for tables with large objects (specially if compression is used). This could lead to out-of-memory exceptions.
@changelog_1329_li
@changelog_1331_li
#The exception "Hexadecimal string contains non-hex character" was not always thrown when it should have been. Fixed.
@changelog_1330_li
@changelog_1332_li
#The H2 Console now provides a link to the documentation when an error occurs (H2 databases only so far).
@changelog_1331_li
@changelog_1333_li
#The acting as PostgreSQL server, when a base directory was set, and the H2 Console was started as well, the base directory was applied twice.
@changelog_1332_li
@changelog_1334_li
#Calling EXTRACT(HOUR FROM ...) or EXTRACT(HH FROM ...) returned the wrong values (0 to 11 instead of 0 to 23). All other tested databases return values from 0 to 23. Please check if your application relies on the old behavior before upgrading.
@changelog_1333_li
@changelog_1335_li
#For compatibility with other databases the column default (COLUMN_DEF) for columns without default is now null (it was an empty string).
@changelog_1334_li
@changelog_1336_li
#Statements that contain very large subqueries (where the subquery result does not fit in memory) are now faster.
@changelog_1335_li
@changelog_1337_li
#Variables: large objects (CLOB and BLOB) that don't fit in memory did not work correctly when used as variables.
@changelog_1336_li
@changelog_1338_li
#Fulltext search is now supported in named in-memory databases.
@changelog_1337_li
@changelog_1339_li
#H2 Console: multiple consecutive spaces in the setting name did not work. Fixed.
@changelog_1338_h2
@changelog_1340_h2
#Version 1.0.65 (2008-01-18)
@changelog_1339_li
@changelog_1341_li
#The build (ant) now automatically switches the source code to the correct version (JDK 1.4/1.5 or 1.6).
@changelog_1340_li
@changelog_1342_li
#A recovery bug has been fixed. With older versions, it was necessary to add ;RECOVER=1 to the database URL in cases where it should not have been required.
@changelog_1341_li
@changelog_1343_li
#The performance for DROP and DROP ALL OBJECTS has been improved.
@changelog_1342_li
@changelog_1344_li
#The ChangePassword API has been improved.
@changelog_1343_li
@changelog_1345_li
#User defined variables are now supported. Examples: SET @VAR=10;CALL @VAR. This can be used for running totals as in: select x, set(@t, ifnull(@t, 0) + x) from system_range(1, 10)
@changelog_1344_li
@changelog_1346_li
#The Ukrainian translation has been improved.
@changelog_1345_li
@changelog_1347_li
#CALL statements can now be used in batch updates and called using Statement.executeUpdate.
@changelog_1346_li
@changelog_1348_li
#New read-only setting CREATE_BUILD (the build number of the database engine that created the database).
@changelog_1347_li
@changelog_1349_li
#The optimizer did not use multi column indexes for range queries in some cases. Fixed.
@changelog_1348_li
@changelog_1350_li
#The H2 Console now calls DataSource.getConnection() instead of DataSource.getConnection(user, password) when user name and password are not specified.
@changelog_1349_li
@changelog_1351_li
#The bind IP address can now be set when using multi-homed host (if multiple network adapters are available) using the system property h2.bindAddress.
@changelog_1350_li
@changelog_1352_li
#Batch update: Calling BatchUpdateException.printStackTrace() could result in out of memory. Fixed.
@changelog_1351_li
@changelog_1353_li
#Indexes of unique or foreign constraints where not dropped when the constraint was dropped after altering the table (for example dropping a column). Fixed.
@changelog_1352_li
@changelog_1354_li
#The performance for large result sets in the server mode has been improved.
@changelog_1353_li
@changelog_1355_li
#The setting h2.serverSmallResultSetSize has been renamed to h2.serverResultSetFetchSize.
@changelog_1354_li
@changelog_1356_li
#The SCRIPT command now uses multi-row insert statements to save space except if the option SIMPLE is used.
@changelog_1355_li
@changelog_1357_li
#The SCRIPT command did not split up CLOB data correctly. Fixed.
@changelog_1356_li
@changelog_1358_li
#Optimization for single column distinct queries with an index: select distinct name from test. Can be disabled by setting the system property h2.optimizeDistinct to false.
@changelog_1357_li
@changelog_1359_li
#DROP ALL OBJECTS did not drop user defined aggregate functions and domains.
@changelog_1358_li
@changelog_1360_li
#PostgreSQL compatibility: COUNT(T.*) is now supported.
@changelog_1359_li
@changelog_1361_li
#LIKE comparisons are now faster.
@changelog_1360_li
@changelog_1362_li
#Encrypted databases are now faster.
@download_1000_h1
ダウンロード
@download_1001_h3
#Version 1.1.104 (2008-11-28, Beta)
#Version 1.1.105 (2008-12-19, Beta)
@download_1002_a
Windows Installer
......@@ -2614,7 +2620,7 @@ ORDER BY, GROUP BY, HAVING, UNION, LIMIT, TOP
Collationをサポート、users、roles
@features_1062_li
HSQLDB、MySQLとPostgreSQLのための互換モード
#Compatibility modes for IBM DB2, Apache Derby, HSQLDB, MS SQL Server, MySQL, Oracle, and PostgreSQL.
@features_1063_h3
セキュリティの特徴
......@@ -3832,366 +3838,375 @@ checksumのレコードが合わないために (例えば、別のアプリケ
#For certain features, this database can emulate the behavior of specific databases. Not all features or differences of those databases are implemented. Here is the list of currently supported modes and the difference to the regular mode:
@features_1468_h3
#PostgreSQL Compatibility Mode
#DB2 Compatibility Mode
@features_1469_p
#To use the PostgreSQL mode, use the database URL <code>jdbc:h2:~/test;MODE=PostgreSQL</code> or the SQL statement <code>SET MODE PostgreSQL</code> .
#To use the IBM DB2 mode, use the database URL <code>jdbc:h2:~/test;MODE=DB2</code> or the SQL statement <code>SET MODE DB2</code> .
@features_1470_li
#Concatenation of a NULL with another value results in NULL. Usually, the NULL is treated as an empty string if only one of the operators is NULL, and NULL is only returned if both values are NULL.
#For aliased columns, ResultSetMetaData.getColumnName() returns the alias name and getTableName() returns null.
@features_1471_li
#When converting a floating point number to a integer, the fractional digits should not be truncated, but the value should be rounded.
#Support for the syntax [OFFSET .. ROW] [FETCH ... ONLY] as an alternative syntax for LIMIT .. OFFSET.
@features_1472_li
#The system columns 'CTID' and 'OID' should be supported.
@features_1472_h3
#Derby Compatibility Mode
@features_1473_li
#For aliased columns, ResultSetMetaData.getColumnName() returns the alias name and getTableName() returns null.
@features_1473_p
#To use the Apache Derby mode, use the database URL <code>jdbc:h2:~/test;MODE=Derby</code> or the SQL statement <code>SET MODE Derby</code> .
@features_1474_h3
#MySQL Compatibility Mode
@features_1474_li
#For aliased columns, ResultSetMetaData.getColumnName() returns the alias name and getTableName() returns null.
@features_1475_p
#To use the MySQL mode, use the database URL <code>jdbc:h2:~/test;MODE=MySQL</code> or the SQL statement <code>SET MODE MySQL</code> .
@features_1475_li
#For unique indexes, NULL is distinct. That means only one row with NULL in one of the columns is allowed.
@features_1476_li
#When inserting data, if a column is defined to be NOT NULL and NULL is inserted, then a 0 (or empty string, or the current timestamp for timestamp columns) value is used. Usually, this operation is not allowed and an exception is thrown.
@features_1476_h3
#HSQLDB Compatibility Mode
@features_1477_li
#When converting a floating point number to a integer, the fractional digits should not be truncated, but the value should be rounded.
@features_1477_p
#To use the HSQLDB mode, use the database URL <code>jdbc:h2:~/test;MODE=HSQLDB</code> or the SQL statement <code>SET MODE HSQLDB</code> .
@features_1478_li
#The identifiers should be returned in lower case.
#For aliased columns, ResultSetMetaData.getColumnName() returns the alias name and getTableName() returns null.
@features_1479_li
#Creating indexes in the CREATE TABLE statement should be supported.
#When converting the scale of decimal data, the number is only converted if the new scale is smaller then current scale. Usually, the scale is converted and 0s are added if required.
@features_1480_li
#For aliased columns, ResultSetMetaData.getColumnName() and getTableName() return the real column and table name.
#Concatenation of a NULL with another value results in NULL. Usually, the NULL is treated as an empty string if only one of the operators is NULL, and NULL is only returned if both values are NULL.
@features_1481_h3
#HSQLDB Compatibility Mode
@features_1481_li
#For unique indexes, NULL is distinct. That means only one row with NULL in one of the columns is allowed.
@features_1482_p
#To use the HSQLDB mode, use the database URL <code>jdbc:h2:~/test;MODE=HSQLDB</code> or the SQL statement <code>SET MODE HSQLDB</code> .
@features_1482_h3
#MS SQL Server Compatibility Mode
@features_1483_li
#Concatenation of a NULL with another value results in NULL. Usually, the NULL is treated as an empty string if only one of the operators is NULL, and NULL is only returned if both values are NULL.
@features_1483_p
#To use the MS SQL Server mode, use the database URL <code>jdbc:h2:~/test;MODE=MSSQLServer</code> or the SQL statement <code>SET MODE MSSQLServer</code> .
@features_1484_li
#When converting the scale of decimal data, the number is only converted if the new scale is smaller then current scale. Usually, the scale is converted and 0s are added if required.
#For aliased columns, ResultSetMetaData.getColumnName() returns the alias name and getTableName() returns null.
@features_1485_li
#When using unique indexes, multiple rows with NULL in one of the columns are allowed by default. However many databases view NULL as distinct in this regard and only allow one row with NULL.
#Identifiers may be quoted using square brackets as in [Test].
@features_1486_li
#For aliased columns, ResultSetMetaData.getColumnName() returns the alias name and getTableName() returns null.
#For unique indexes, NULL is distinct. That means only one row with NULL in one of the columns is allowed.
@features_1487_h3
#MS SQL Server Compatibility Mode
#MySQL Compatibility Mode
@features_1488_p
#To use the MS SQL Server mode, use the database URL <code>jdbc:h2:~/test;MODE=MSSQLServer</code> or the SQL statement <code>SET MODE MSSQLServer</code> .
#To use the MySQL mode, use the database URL <code>jdbc:h2:~/test;MODE=MySQL</code> or the SQL statement <code>SET MODE MySQL</code> .
@features_1489_li
#Identifiers may be quoted using square brackets as in [Test].
#When inserting data, if a column is defined to be NOT NULL and NULL is inserted, then a 0 (or empty string, or the current timestamp for timestamp columns) value is used. Usually, this operation is not allowed and an exception is thrown.
@features_1490_li
#When using unique indexes, multiple rows with NULL in one of the columns are allowed by default. However many databases view NULL as distinct in this regard and only allow one row with NULL.
#Creating indexes in the CREATE TABLE statement should be supported.
@features_1491_li
#For aliased columns, ResultSetMetaData.getColumnName() returns the alias name and getTableName() returns null.
#The identifiers should be returned in lower case.
@features_1492_h3
#Derby Compatibility Mode
@features_1492_li
#When converting a floating point number to a integer, the fractional digits should not be truncated, but the value should be rounded.
@features_1493_p
#To use the Derby mode, use the database URL <code>jdbc:h2:~/test;MODE=Derby</code> or the SQL statement <code>SET MODE Derby</code> .
@features_1493_h3
#Oracle Compatibility Mode
@features_1494_li
#When using unique indexes, multiple rows with NULL in one of the columns are allowed by default. However many databases view NULL as distinct in this regard and only allow one row with NULL.
@features_1494_p
#To use the Oracle mode, use the database URL <code>jdbc:h2:~/test;MODE=Oracle</code> or the SQL statement <code>SET MODE Oracle</code> .
@features_1495_li
#For aliased columns, ResultSetMetaData.getColumnName() returns the alias name and getTableName() returns null.
@features_1496_h3
#Oracle Compatibility Mode
@features_1496_li
#When using unique indexes, multiple rows with NULL in all columns are allowed, however it is not allowed to have multiple rows with the same values otherwise.
@features_1497_p
#To use the Oracle mode, use the database URL <code>jdbc:h2:~/test;MODE=Oracle</code> or the SQL statement <code>SET MODE Oracle</code> .
@features_1497_h3
#PostgreSQL Compatibility Mode
@features_1498_li
#When using unique indexes, multiple rows with NULL in one of the columns are allowed by default. However many databases view NULL as distinct in this regard and only allow one row with NULL.
@features_1498_p
#To use the PostgreSQL mode, use the database URL <code>jdbc:h2:~/test;MODE=PostgreSQL</code> or the SQL statement <code>SET MODE PostgreSQL</code> .
@features_1499_li
#For aliased columns, ResultSetMetaData.getColumnName() returns the alias name and getTableName() returns null.
@features_1500_h2
@features_1500_li
#Concatenation of a NULL with another value results in NULL. Usually, the NULL is treated as an empty string if only one of the operators is NULL, and NULL is only returned if both values are NULL.
@features_1501_li
#When converting a floating point number to a integer, the fractional digits should not be truncated, but the value should be rounded.
@features_1502_li
#The system columns 'CTID' and 'OID' should be supported.
@features_1503_h2
#Auto-Reconnect
@features_1501_p
@features_1504_p
#The auto-reconnect feature causes the JDBC driver to reconnect to the database if the connection is lost. The automatic re-connect only occurs when auto-commit is enabled; if auto-commit is disabled, an exception is thrown.
@features_1502_p
@features_1505_p
#Re-connecting will open a new session. After an automatic re-connect, variables and local temporary tables definitions (excluding data) are re-created. The contents of the system table INFORMATION_SCHEMA.SESSION_STATE contains all client side state that is re-created.
@features_1503_h2
@features_1506_h2
#Automatic Mixed Mode
@features_1504_p
@features_1507_p
#Multiple processes can access the same database without having to explicitly start the server. To do that, append <code>;AUTO_SERVER=TRUE</code> to the database URL. In this case, the first connection to the database is made in embedded mode, and additionally a server is started. If the database is already open in another process, the server mode is used.
@features_1505_p
@features_1508_p
#When using this feature, auto-reconnect is enabled as well.
@features_1506_p
@features_1509_p
#The application that opens the first connection to the database uses the embedded mode, which is faster than the server mode. Therefore the main application should open the database first if possible. A server is started on a random port. This server allows remote connections, however only to this database. In addition to the user name and password, the client sends the random key that is stored in .lock.db file to the server.
@features_1507_h2
@features_1510_h2
トレースオプションを使用する
@features_1508_p
@features_1511_p
アプリケーション内の問題を見つけるために、時々、何のデータベースオペレーションがどこで実行されているかを知るのは良い方法です。このデータベースは次のトレースの特徴を提供します:
@features_1509_li
@features_1512_li
System.out と (または) ファイルをトレースする
@features_1510_li
@features_1513_li
トレースレベル OFF、ERROR、INFO と DEBUG をサポート
@features_1511_li
@features_1514_li
トレースファイルの最大サイズの設定が可能
@features_1512_li
@features_1515_li
Javaコード生成が可能
@features_1513_li
@features_1516_li
手動でファイルを作成することによって、ランタイムでトレースが可能
@features_1514_h3
@features_1517_h3
トレースオプション
@features_1515_p
@features_1518_p
トレースオプションを可能にする簡単な方法は、データベースURLにトレースオプションを設定することです。二つの設定があり、ひとつは、System.out (TRACE_LEVEL_SYSTEM_OUT) トレーシングで、もうひとつはファイルトレーシング(TRACE_LEVEL_FILE)です。トレースレベルは、0 が OFF、1 が ERROR (デフォルト)、2 が INFO で 3 が DEBUGです。両方のレベルがDEBUGに設定されたデータベースURLです:
@features_1516_p
@features_1519_p
トレースレベルは、SQLコマンド <CODE>SET TRACE_LEVEL_SYSTEM_OUT level</CODE> (System.out トレーシング) または <CODE>SET TRACE_LEVEL_FILE level</CODE> (ファイルトレーシング) を実行することによってランタイムで変更できます。例:
@features_1517_h3
@features_1520_h3
トレースファイルの最大サイズを設定
@features_1518_p
@features_1521_p
高いトレースレベルを使用する時、トレースファイルは早くサイズが非常に大きくなります。SQLステートメント <CODE>SET TRACE_MAX_FILE_SIZE maximumFileSizeInMB</CODE> を実行することによりファイルのサイズを制限することができます。ログファイルが制限を超えたら、ファイルは ".old" にファイル名を変えて、新しいファイルが作成されます。もしもうひとつの .oldファイルが存在する場合は、それは削除されます。デフォルトの設定は16 MBです。例:
@features_1519_h3
@features_1522_h3
Javaコード生成
@features_1520_p
@features_1523_p
トレースレベルをINFOかDEBUGに設定した時、同様にJavaのソースコードが生成されるので、問題はより簡単に再生されます。トレースファイルはこのようなものです:
@features_1521_p
@features_1524_p
Javaのソースコードを得るために、 /**/ のない行を取り除く必要があります。 Windowsでの簡単な方法は:
@features_1522_p
@features_1525_p
その後、コンパイルされる前にTrace.javaファイルを完全にする必要があります。例:
@features_1523_p
@features_1526_p
また、トレースファイルに載せられていないため、ユーザー名とパスワードが設定されている必要があります。
@features_1524_h3
@features_1527_h3
手動でファイルを作成し、ランタイムでトレースオプションを可能にする
@features_1525_p
@features_1528_p
時々、アプリケーション、またはデータベースのURLを変えられない、変えたくない場合があります。このような場合に、ランタイムであっても (データベースの接続が開かれている間) トレースモードを可能にできる方法がまだあります。必要なことは、データベースファイルが保存されているディレクトリに特別なファイルを作るだけです。データベースエンジンは、このファイルが存在する場合に (ステートメントが実行されている間のみ) 4秒ごとにチェックしています。このファイル名は、データベース名 プラス ".trace.db.start" です。この特徴はデータベースが暗号化されている場合は無効になります。
@features_1526_p
@features_1529_p
例: データベース名が "test"の場合、 トレーシングを開始するファイルは "test.trace.db.start"です。データベースエンジンは、このファイルを見つけた時、ファイルを削除しようとします。スタートファイルを使用することでトレースが可能になるなら、トレースレベルはデータベースに対して永続的ではなく、トレースはデータベースに接続する以前のレベルに戻されます。しかし、スタートファイルが読み取り専用なら、データベースエンジンはファイルを削除することができず、接続するときはいつもトレースモードになります。
@features_1527_h2
@features_1530_h2
#Using Other Logging APIs
@features_1528_p
@features_1531_p
#By default, this database uses its own native 'trace' facility. This facility is called 'trace' and not 'log' within this database to avoid confusion with the transaction log. Trace messages can be written to both file and System.out. In most cases, this is sufficient, however sometimes it is better to use the same facility as the application, for example Log4j. To do that, this database support SLF4J.
@features_1529_a
@features_1532_a
#SLF4J
@features_1530_p
@features_1533_p
#is a simple facade for various logging APIs and allows to plug in the desired implementation at deployment time. SLF4J supports implementations such as Logback, Log4j, Jakarta Commons Logging (JCL), JDK 1.4 logging, x4juli, and Simple Log.
@features_1531_p
@features_1534_p
#To enable SLF4J, set the file trace level to 4 in the database URL:
@features_1532_p
@features_1535_p
#Changing the log mechanism is not possible after the database is open, that means executing the SQL statement SET TRACE_LEVEL_FILE 4 when the database is already open will not have the desired effect. To use SLF4J, all required jar files need to be in the classpath. If it does not work, check in the file &lt;database&gt;.trace.db for error messages.
@features_1533_h2
@features_1536_h2
読み取り専用データベース
@features_1534_p
@features_1537_p
データベースファイルが読み取り専用なら、同様にデータベースも読み取り専用です。このデータベースで新しいテーブルを作成したり、データを追加したり変更したりすることはできません。SELECTステートメントのみ許可されています。読み取り専用データベースを作成するには、データベースを終了してログファイルを小さくします。ログファイルを削除してはいけません。そして、オペレーティングシステムを使用してデータベースファイルを読み取り専用にします。これでデータベースを開くと、読み取り専用になっています。アプリケーションが、データベースが読み取り専用であることを判断する方法は二つあります: Connection.isReadOnly() を呼ぶか、SQLステートメント CALL READONLY() を実行します。
@features_1535_h2
@features_1538_h2
#Read Only Databases in Zip or Jar File
@features_1536_p
@features_1539_p
#To create a read-only database in a zip, first create a regular persistent database, and then create a backup. If you are using a database named 'test', an easy way to do that is using the Backup tool or the BACKUP SQL statement:
@features_1537_p
@features_1540_p
#The database must not have pending changes, that means you need to close all connections to the database, open one single connection, and then execute the statement. Afterwards, you can log out, and directly open the database in the zip file using the following database URL:
@features_1538_p
@features_1541_p
#Databases in a zip file are read-only. The performance for some queries will be slower than when using a regular database, because random access in zip files is not supported (only streaming). How much this affects the performance depends on the queries and the data. The database is not read in memory; so large databases are supported as well. The same indexes are used than when using a regular database.
@features_1539_h2
@features_1542_h2
ディスクスペースが少ない状況での正しい取り扱い
@features_1540_p
@features_1543_p
データベースは、利用可能なディスクスペースが少なくなっている状況に対処することができます。データベースを開始する時はいつも、"emergency space" ファイルが作られ (サイズは 1 MB)、利用可能なスペースがもうない場合には、ファイルは小さくなります。利用可能なスペースが 128 KB以下になった場合、データベースは特別な読み取り専用モードになり、全ての書き込み操作はもはや許可されません: この時点から全ての書き込み操作は、"No disk space available" を例外に投げます。通常のオペレーションモードに戻るためには、最初にデータベースへの全ての接続を終了し、スペースを空ける必要があります。
@features_1541_p
@features_1544_p
早くからディスクスペースの少ない状況を把握するために、データベースイベントリスナーをインストールすることは可能です (ディスクスペースが 1MB のみ利用可能な時)。SQLステートメント SET DATABASE_EVENT_LISTENER を使用します。フォームのURLを使用して、接続時にリスナーを設定することが可能です jdbc:h2:~/test;DATABASE_EVENT_LISTENER='com.acme.DbListener' (クラス名の周りの引用文は必要です)。APIのDatabaseEventListenerもご覧下さい。
@features_1542_h3
@features_1545_h3
破損したデータベースを開く
@features_1543_p
@features_1546_p
boot info (始動時に実行されるSQLスクリプト) が破損しているため、データベースを開くことができない場合、データベースイベントリスナーを指定することでデータベースを開くことができます。例外は記録されますが、データベースの開始は続行します。
@features_1544_h2
@features_1547_h2
computed column / ベースインデックスの機能
@features_1545_p
@features_1548_p
インデックスの機能は、このデータベースによって直接サポートはされていませんが、computed columnsを使用することによって、簡単にエミュレートすることができます。例えば、カラムのupper-caseバージョンのインデックスが必要なら、原形のカラムのupper-caseバージョンのcomputed columnを作成し、このカラムにインデックスをつけます:
@features_1546_p
@features_1549_p
値は生成されているので、データを挿入する時、カラムのupper-caseバージョンのための値を指定する必要はありません (許可されていません)。 しかし、テーブルを呼ぶ時、このカラムを使用することはできます。:
@features_1547_h2
@features_1550_h2
多次元インデックス
@features_1548_p
@features_1551_p
効率的な多次元の (空間的) 領域のクエリーを実行するためにツールを提供します。このデータベースは専門的な空間的インデックス (R-Tree またはより小さいもの) をサポートしていません。代わりに、B-Treeインデックスが使われています。それぞれのレコードに対して、多次元のキーは、単数範囲 (スカラー) の値に変換 (位置づけ) されます。この値は、space-filling curve (空間充填曲線) で位置を指定します。
@features_1549_p
@features_1552_p
現在、Z-order (N-order または Morton-order とも呼ばれています) が使用されています; Hilbert curveも使用できますが、実装はより複雑です。多次元の値を変換するアルゴリズムは、bit-interleavingと呼ばれています。B-Treeインデックス (通常は computed columnを使用します)を使用することで、スカラーの値はインデックスをつけられます。
@features_1550_p
@features_1553_p
最初のカラムにインデックスを使用する上で、メソッドは徹底的なパフォーマンスの改良をもたらすことができます。データと次元の数によりますが、改良は通常、factor 5よりも高いものです。指定された多次元の範囲から、ツールはSQLクエリーを生成します。使用されたメソッドは、データベースに依存しておらず、ツールは簡単に他のデータベースに移植することができます。ツールの使用方法の例は、TestMultiDimension.java で提供されているサンプルコードをご覧下さい。
@features_1551_h2
@features_1554_h2
パスワードを使用する
@features_1552_h3
@features_1555_h3
安全なパスワードを使用する
@features_1553_p
@features_1556_p
弱いパスワードは、暗号化やセキュリティプロトコルに取るに足らず、解読されてしまうことを覚えておいて下さい。辞書で見つけられるようなパスワードは使用しないでください。また、数字を付け足してもそのようなパスワードは安全にはなりません。良いパスワードを作る方法は、覚えやすい、文章の最初の文字を使う、大文字と小文字を使う、特別な文字が含まれているものを作る、です。例:
@features_1554_p
@features_1557_p
i'sE2rtPiUKtT (もしトリックを知っていれば、このパスワードは覚えやすいものです)
@features_1555_h3
@features_1558_h3
パスワード: Stringの代わりにChar Arraysを使用する
@features_1556_p
@features_1559_p
Java Stringは不変のオブジェクトであり、アプリケーションによって安全に壊されることはできません。Stringの作成後、Stringは少なくともガベージコレクションになるまで、コンピューターのメインメモリ内にとどまるでしょう。ガベージコレクションはアプリケーションによって制御されず、ガベージコレクションであっても、データはまだメモリにとどまっているでしょう。パスワードが含まれるメモリの一部をディスクと取り換えることも可能でしょう (十分でないメインメモリも使用可能のため)。
@features_1557_p
@features_1560_p
アタッカーはオペレーティングシステムのスワップファイルにアクセスするでしょう。したがって、パスワードを保存するために、Stringの代わりにchar arrayを使用するのは良い方法です。char arrayは使用後クリアにされるので (0で埋められます)、パスワードはスワップファイルに保存されません。
@features_1558_p
@features_1561_p
このデータベースは、ユーザーパスワードとファイルパスワードを認証するために、Stringの代わりにchar arrayを使用することをサポートしています。次のコードはこのように使用されます:
@features_1559_p
@features_1562_p
このサンプルでは、パスワードはアプリケーションでのハードコードで、もちろん安全ではありません。しかし、Java Swingはchar arrayを使用してパスワードを得る方法をサポートしています (JPasswordField)。
@features_1560_h3
@features_1563_h3
ユーザー名 と (または) パスワードをURLで認証する
@features_1561_p
@features_1564_p
ユーザー名を <code>Connection conn = DriverManager. getConnection("jdbc:h2:~/test", "sa", "123");</code> のように切り離されたパラメータとして認証する代わりに、URLそのもので <code>Connection conn = DriverManager. getConnection("jdbc:h2:~/test;USER=sa;PASSWORD=123");</code> ユーザー名 (と (または) パスワード)を提供することができます。URL内の設定は、切り離されたパラメータとして認証させる設定より優先されます。
@features_1562_h2
@features_1565_h2
ユーザー定義の関数とストアドプロシージャ
@features_1563_p
@features_1566_p
組み込み関数に加えて、このデータベースはユーザー定義のJava関数をサポートしています。同様に、このデータベースではJava関数はストアドプロシージャとして使用されています。関数は、使用される前に宣言 (登録) されていなければなりません。static Javaメソッドのみサポートされています; クラスとメソッドの両方が public である必要があります。Javaメソッドの例:
@features_1564_p
@features_1567_p
Java関数は、CREATE ALIAS と呼ばれるデータベースに登録されていなければなりません:
@features_1565_p
@features_1568_p
完全なサンプルアプリケーションは src/test/org/h2/samples/Function.java をご覧下さい。
@features_1566_h3
@features_1569_h3
データタイプマッピング関数
@features_1567_p
@features_1570_p
"int" のような non-nullable (NULL可能ではない) パラメータを受け入れる関数は、パラメータのうちひとつがNULLであるなら呼ばれないでしょう。このケースでは、NULLの値は結果として使用されます。このケースで関数を呼び出したいのなら、"int" の代わりに "java.lang.Integer" を使用する必要があります。
@features_1568_h3
@features_1571_h3
接続を必要とする関数
@features_1569_p
@features_1572_p
もしJava関数の最初のパラメータが java.sql.Connection なら、データベースへの接続は与えられています。返す前にこの接続を閉じる必要はありません。
@features_1570_h3
@features_1573_h3
例外を投げる関数
@features_1571_p
@features_1574_p
関数が例外を投げたら、現在のステートメントはロールバックされ、例外はアプリケーションに投げられます。
@features_1572_h3
@features_1575_h3
Result Setを返す関数
@features_1573_p
@features_1576_p
関数はresult setを返します。このような関数はCALLステートメントと一緒に呼ばれます:
@features_1574_h3
@features_1577_h3
SimpleResultSetを使用する
@features_1575_p
@features_1578_p
result setを返す関数は、SimpleResultSetツールを使用して最初からこのresult setを作成することができます:
@features_1576_h3
@features_1579_h3
関数をテーブルとして使用する
@features_1577_p
@features_1580_p
result setを返す関数はテーブルのようになれます。しかし、このケースでは関数は少なくとも二回は呼ばれます: 最初はカラム名を集めるために構文解析している間です (コンパイル時に未知のところでパラメータはNULLに設定)。そして、データを取得するためにステートメントを実行している間です (これが結合なら繰り返されます)。関数がカラム一覧を取得するためだけに呼ばれたのなら、関数を認証する接続URLは jdbc:columnlist:connection です。そうでなければ、接続URLは jdbc:default:connection です。
@features_1578_h2
@features_1581_h2
トリガー
@features_1579_p
@features_1582_p
このデータベースは、行が更新、挿入、または削除された前後に呼ばれるJavaトリガーをサポートしています。トリガーは複雑な一貫性チェックか、データベース内の関連したデータをアップデートするのに使用されます。マテリアライズドビューをシミュレートするためにトリガーを使用することも可能です。完全なサンプルアプリケーションは src/test/org/h2/samples/TriggerSample.java をご覧下さい。Javaトリガーは、インターフェイス org.h2.api.Trigger を実装しなければなりません:
@features_1580_p
@features_1583_p
他のテーブルのクエリーかデータのアップデートに接続を使用することができます。トリガーはその時データベースで定義されている必要があります:
@features_1581_p
@features_1584_p
トリガーはSQL Exceptionを投げることによって、変更を禁止させることができます。
@features_1582_h2
@features_1585_h2
データベースをコンパクトにする
@features_1583_p
@features_1586_p
データベースファイルの空のスペースは自動的に再利用されます。インデックスを再構築するもっとも簡単な方法は、データベースが閉じられている間に .index.db ファイルを削除します。しかし、一部状況では (例えば、データベースの多数のデータを削除した後)、データベースのサイズを縮小したい場合があります (データベースをコンパクトにする)。そのためのサンプルです:
@features_1584_p
@features_1587_p
サンプルアプリケーション org.h2.samples.Compact もご覧下さい。データベースのバックアップを作るのと、スクリプトからデータベースを再構築するのにSCRIPT / RUNSCRIPT コマンドを使用することができます。
@features_1585_h2
@features_1588_h2
キャッシュの設定
@features_1586_p
@features_1589_p
データベースは最も頻繁に使われるデータやインデックスページをメインメモリに保存します。キャッシュに使用されるメモリ量を CACHE_SIZE 設定を使用して変更することができます。この設定は、データベース接続URL (jdbc:h2:~/test;CACHE_SIZE=131072) か、ランタイムにSET CACHE_SIZE を使用してサイズを変更できます。
@features_1587_p
@features_1590_p
このデータベースは二つのcache page replacement algorithms (キャッシュページ置換アルゴリズム) をサポートしています: LRU (デフォルト) と2Qです。LRUは、キャッシュがいっぱいになったら、頻繁に使用されていないページをキャッシュから削除します。2Qアルゴリズムは少し複雑で、基本的に二つのクエリーが使用されます。2Qアルゴリズムはテーブルスキャンに、より抵抗がありますが、LRUと比較してオーバーヘッドは少し高めです。キャッシュアルゴリズム 2Qを使用するためには、フォームのデータベースURL jdbc:h2:~/test;CACHE_TYPE=TQ を使用します。キャッシュアルゴリズムは、一度データベースが開かれたら変更することはできません。
@features_1588_p
@features_1591_p
読んだり書いたりしたページや、現在使用されているキャッシュアルゴリズムの情報を得るためには、SELECT * FROM INFORMATION_SCHEMA.SETTINGS を呼びます。データとインデックスファイルに読み書きしたページ数が書かれています。
@fragments_1000_b
......@@ -5728,7 +5743,7 @@ H2 データベース エンジン
#Download Beta
@mainWeb_1007_td
#Version 1.1.104 (2008-11-28):
#Version 1.1.105 (2008-12-19):
@mainWeb_1008_a
#Windows Installer (3.1 MB)
......
......@@ -278,12 +278,13 @@ java org.h2.test.TestAll timer
System.setProperty("h2.check2", "true");
/*
create a short one page documentation
checksum: no need to checksum all data; every 128th byte is enough;
but need position+counter
JCR: for each node type, create a table; one 'dynamic' table with parameter;
option to cache the results
<link rel="icon" type="image/png" href="/path/image.png">
create a short one page documentation
update roadmap (specially priority 1)
checksum: no need to checksum all data; every 128th byte is enough;
but need position+counter
http://blog.flexive.org/2008/12/05/porting-flexive-to-the-h2-database/
postgresql generate_series?
......
......@@ -575,4 +575,4 @@ bleyl donald conservative offsets diabetes ansorg allocating osmond gluco
joachim mysqladmin sudo mysqld indicator wire ring relates expedites
approximated approximation dvan dsn dobysoft ebean syswow tmueller dbbench
connecturl problematic transformation lazy querydsl squill empire liq fle
xive evolving
xive evolving mssqlserver
Markdown 格式
0%
您添加了 0 到此讨论。请谨慎行事。
请先完成此评论的编辑!
注册 或者 后发表评论