- 10 11月, 2017 5 次提交
-
-
由 LaughingMan 提交于
-
由 LaughingMan 提交于
-
由 LaughingMan 提交于
-
由 LaughingMan 提交于
The corresponding documentation was already removed in https://github.com/h2database/h2database/commit/197daa58104de6185e08b66e836876eb46b39844
-
由 LaughingMan 提交于
-
- 08 11月, 2017 1 次提交
-
-
由 Noel Grandin 提交于
-
- 07 11月, 2017 2 次提交
-
-
-
由 Noel Grandin 提交于
-
- 04 11月, 2017 5 次提交
-
-
由 Noel Grandin 提交于
Support drop-columns using brackets (Oracle syntax style)
-
由 plus33 提交于
too. The type treaded same as CHAR.
-
由 plus33 提交于
-
由 Noel Grandin 提交于
This reverts commit e26337e9. seems to cause various unit test failures.
-
由 Noel Grandin 提交于
-
- 03 11月, 2017 3 次提交
-
-
由 Noel Grandin 提交于
This reverts commit e26337e9. seems to cause various unit test failures.
-
-
由 Noel Grandin 提交于
-
- 02 11月, 2017 5 次提交
-
-
由 plus33 提交于
-
由 plus33 提交于
-
由 plus33 提交于
-
由 plus33 提交于
E.g. alter table test drop (a, b) works same as alter table test drop column a, b
-
由 Noel Grandin 提交于
fixing incorrect index reuse in AlterTableAddConstraint.java
-
- 01 11月, 2017 8 次提交
-
-
-
由 andrei 提交于
-
由 Petr Kureš 提交于
fixing incorrect index reuse in AlterTableAddConstraint.java ALTER_TABLE_ADD_CONSTRAINT_REFERENTIAL and ALTER_TABLE_ADD_CONSTRAINT_UNIQUE problem in ALTER_TABLE_ADD_CONSTRAINT_REFERENTIAL was caused by commit 08b98324 by Thomas Mueller <mueller@adobe.com> he intended to reuse existing index... but it prevents that index from being dropped which can cause problems later Correct solution would be to rewrite how automatically created indexes (referential/constraint) are managed to create new automatic index when dropping the reused existing index. Until this is solved it's IMHO better to not reuse existing index as it causes database to be effectively corrupted. Also removing test code Thomas added to TestCases.java problem in ALTER_TABLE_ADD_CONSTRAINT_UNIQUE was caused by canUseUniqueIndex allowing to use index with more columns than requested as unique index which caused unique constraint to fail as ConstraintUnique checkRow comment says that 'unique index check is enough' and the index is not unique for given constraint if it has more columns
-
由 andrei 提交于
-
由 Noel Grandin 提交于
Fix problem with websphere liberty connection pool resetting client info
-
由 mehneni 提交于
-
由 mehneni 提交于
-
由 Noel Grandin 提交于
Cleanup CreateCluster tool
-
- 31 10月, 2017 1 次提交
-
-
由 Noel Grandin 提交于
-
- 29 10月, 2017 1 次提交
-
-
由 LaughingMan 提交于
-
- 28 10月, 2017 9 次提交
-
-
由 LaughingMan 提交于
-
由 LaughingMan 提交于
-
由 LaughingMan 提交于
-
由 LaughingMan 提交于
-
由 LaughingMan 提交于
-
由 LaughingMan 提交于
If the database exists, it gets deleted. If the database doesn't exist, an exception gets thrown, immediately caught, and ignored. In both cases exists will be false and we continue. Later the database gets deleted unconditionally, which means we can delete this entire block.
-
由 LaughingMan 提交于
-
由 LaughingMan 提交于
-
由 LaughingMan 提交于
-