- 22 3月, 2017 1 次提交
-
-
由 Sergey Kalashnikov 提交于
* Custom data types handler * Updated doc, changelog, dictionary. Fixed review comment. * Extended the custom types handler interface * Fixed test * Fixed review comments * Added note on ABI stability of the feature to docs
-
- 15 3月, 2017 1 次提交
-
-
由 Sergey Kalashnikov 提交于
-
- 14 3月, 2017 1 次提交
-
-
由 Sergi Vladykin 提交于
-
- 10 3月, 2017 1 次提交
-
-
由 thomasmueller 提交于
-
- 09 3月, 2017 3 次提交
-
-
-
由 thomasmueller 提交于
-
由 Sergi Vladykin 提交于
-
- 02 3月, 2017 3 次提交
-
-
由 thomasmueller 提交于
-
由 thomasmueller 提交于
-
由 Noel Grandin 提交于
-
- 24 2月, 2017 4 次提交
-
-
由 Thomas Mueller Graf 提交于
-
由 Thomas Mueller Graf 提交于
-
由 Thomas Mueller Graf 提交于
-
由 Thomas Mueller Graf 提交于
-
- 23 2月, 2017 4 次提交
-
-
由 Thomas Mueller Graf 提交于
-
由 Thomas Mueller Graf 提交于
-
由 Thomas Mueller Graf 提交于
-
由 Thomas Mueller Graf 提交于
-
- 22 2月, 2017 1 次提交
-
-
由 Thomas Mueller Graf 提交于
-
- 16 2月, 2017 1 次提交
-
-
由 Noel Grandin 提交于
-
- 09 2月, 2017 2 次提交
-
-
由 Noel Grandin 提交于
-
由 Noel Grandin 提交于
to make it more obvious
-
- 06 2月, 2017 2 次提交
-
-
由 Noel Grandin 提交于
Updated commercial support information
-
由 Steve McLeod 提交于
-
- 02 2月, 2017 1 次提交
-
-
由 Noel Grandin 提交于
Use System.nanoTime() to check timeouts
-
- 30 1月, 2017 1 次提交
-
-
由 Ulrich Wielant 提交于
-
- 26 1月, 2017 1 次提交
-
-
由 Ulrich Wielant 提交于
System.currentTimeMillis() is influenced by system time corrections whereas System.nanoTime() is strongly sequential. So it is better to use System.nanoTime() when checking for timeouts and elapsed time.
-
- 23 1月, 2017 1 次提交
-
-
由 Noel Grandin 提交于
-
- 22 1月, 2017 1 次提交
-
-
由 Noel Grandin 提交于
Fix JDBC type of TIMESTAMP WITH TIME ZONE
-
- 21 1月, 2017 1 次提交
-
-
由 Noel Grandin 提交于
-
- 20 1月, 2017 7 次提交
-
-
由 alexpaschenko 提交于
* Added WITH to CREATE SCHEMA to supply default TableEngine params * Updated docs to reflect changes in CREATE SCHEMA * Review fixes - docs; code de-duplication; test for table engine params in schema * Setter for table engine params in Schema
-
由 Noel Grandin 提交于
-
由 Sergi 提交于
-
-
由 Sergi 提交于
-
由 Noel Grandin 提交于
Optimized column vs constant comparisons
-
由 Alexander Paschenko 提交于
-
- 19 1月, 2017 3 次提交
-
-
由 Philippe Marschall 提交于
Currently the JDBC type of TIMESTAMP WITH TIME ZONE is Types.OTHER. JDBC 4.2 has a dedicated type for this Types.TIMESTAMP_WITH_TIMEZONE. Unfortunately this type is only available in JDBC 4.2/Java 1.8 so I hard code the constant value instead of the constant reference.
-
由 Noel Grandin 提交于
unfortunately I had to hit it with the big synchronization stick. I could no simple way to rescue the current rather clever code. This bug was reported by Anatolii K in this message: https://groups.google.com/d/msg/h2-database/rhSoRhzeZzk/gc-pNlSpEwAJ
-
由 Noel Grandin 提交于
Issue #434 - parse engine params in CREATE TABLE w/o engine specified
-