TiDB v6.5 Documentation### For detailed information why RocksDB needs to implement compaction, see �→ RocksDB-related materials. When write ### traffic (like the importing data size) is big, it is recommended to �→ enable ('dave'), ('sarah'), ('bill'); With optimistic locking and tidb_constraint_check_in_place=OFF: BEGIN OPTIMISTIC; INSERT INTO users (username) VALUES ('jane'), ('chris'), ('bill'); Query OK, 3 rows affected affected (0.00 sec) Records: 2 Duplicates: 0 Warnings: 0 COMMIT; ERROR 1062 (23000): Duplicate entry 'bill' for key 'users.username' In the preceding optimistic example, the unique check was deferred until0 码力 | 5282 页 | 99.69 MB | 1 年前3
TiDB v5.1 Documentation#### For detailed information why RocksDB needs to implement compaction, see �→ RocksDB-related materials. When write #### traffic (like the importing data size) is big, it is recommended to �→ enable ('dave'), ('sarah'), ('bill'); With the default of pessimistic locking: BEGIN; INSERT INTO users (username) VALUES ('jane'), ('chris'), ('bill'); ERROR 1062 (23000): Duplicate entry 'bill' for key 'username' tidb_constraint_check_in_place=0: BEGIN OPTIMISTIC; INSERT INTO users (username) VALUES ('jane'), ('chris'), ('bill'); Query OK, 0 rows affected (0.00 sec) Query OK, 3 rows affected (0.00 sec) Records: 3 Duplicates:0 码力 | 2745 页 | 47.65 MB | 1 年前3
TiDB v7.1 Documentation### For detailed information why RocksDB needs to implement compaction, see �→ RocksDB-related materials. When write ### traffic (like the importing data size) is big, it is recommended to �→ enable ('dave'), ('sarah'), ('bill'); With optimistic locking and tidb_constraint_check_in_place=OFF: BEGIN OPTIMISTIC; INSERT INTO users (username) VALUES ('jane'), ('chris'), ('bill'); Query OK, 3 rows affected affected (0.00 sec) Records: 2 Duplicates: 0 Warnings: 0 COMMIT; ERROR 1062 (23000): Duplicate entry 'bill' for key 'users.username' In the preceding optimistic example, the unique check was deferred until0 码力 | 5716 页 | 104.74 MB | 1 年前3
TiDB v7.6 Documentation### For detailed information why RocksDB needs to implement compaction, see �→ RocksDB-related materials. When write ### traffic (like the importing data size) is big, it is recommended to �→ enable ('dave'), ('sarah'), ('bill'); With optimistic locking and tidb_constraint_check_in_place=OFF: BEGIN OPTIMISTIC; INSERT INTO users (username) VALUES ('jane'), ('chris'), ('bill'); Query OK, 3 rows affected affected (0.00 sec) Records: 2 Duplicates: 0 Warnings: 0 COMMIT; ERROR 1062 (23000): Duplicate entry 'bill' for key 'users.username' In the preceding optimistic example, the unique check was deferred until0 码力 | 6123 页 | 107.24 MB | 1 年前3
TiDB v7.5 Documentation### For detailed information why RocksDB needs to implement compaction, see �→ RocksDB-related materials. When write ### traffic (like the importing data size) is big, it is recommended to �→ enable ('dave'), ('sarah'), ('bill'); With optimistic locking and tidb_constraint_check_in_place=OFF: BEGIN OPTIMISTIC; INSERT INTO users (username) VALUES ('jane'), ('chris'), ('bill'); Query OK, 3 rows affected affected (0.00 sec) Records: 2 Duplicates: 0 Warnings: 0 COMMIT; ERROR 1062 (23000): Duplicate entry 'bill' for key 'users.username' In the preceding optimistic example, the unique check was deferred until0 码力 | 6020 页 | 106.82 MB | 1 年前3
TiDB v5.3 Documentation#### For detailed information why RocksDB needs to implement compaction, see �→ RocksDB-related materials. When write #### traffic (like the importing data size) is big, it is recommended to �→ enable ('dave'), ('sarah'), ('bill'); With the default of pessimistic locking: BEGIN; INSERT INTO users (username) VALUES ('jane'), ('chris'), ('bill'); ERROR 1062 (23000): Duplicate entry 'bill' for key 'username' tidb_constraint_check_in_place=0: BEGIN OPTIMISTIC; INSERT INTO users (username) VALUES ('jane'), ('chris'), ('bill'); Query OK, 0 rows affected (0.00 sec) Query OK, 3 rows affected (0.00 sec) Records: 3 Duplicates:0 码力 | 2996 页 | 49.30 MB | 1 年前3
TiDB v5.2 Documentation#### For detailed information why RocksDB needs to implement compaction, see �→ RocksDB-related materials. When write #### traffic (like the importing data size) is big, it is recommended to �→ enable ('dave'), ('sarah'), ('bill'); With the default of pessimistic locking: BEGIN; INSERT INTO users (username) VALUES ('jane'), ('chris'), ('bill'); ERROR 1062 (23000): Duplicate entry 'bill' for key 'username' tidb_constraint_check_in_place=0: BEGIN OPTIMISTIC; INSERT INTO users (username) VALUES ('jane'), ('chris'), ('bill'); Query OK, 0 rows affected (0.00 sec) Query OK, 3 rows affected (0.00 sec) Records: 3 Duplicates:0 码力 | 2848 页 | 47.90 MB | 1 年前3
TiDB v8.1 Documentation### For detailed information why RocksDB needs to implement compaction, see �→ RocksDB-related materials. When write ### traffic (like the importing data size) is big, it is recommended to �→ enable ('dave'), ('sarah'), ('bill'); With optimistic locking and tidb_constraint_check_in_place=OFF: BEGIN OPTIMISTIC; INSERT INTO users (username) VALUES ('jane'), ('chris'), ('bill'); Query OK, 3 rows affected affected (0.00 sec) Records: 2 Duplicates: 0 Warnings: 0 COMMIT; ERROR 1062 (23000): Duplicate entry 'bill' for key 'users.username' In the preceding optimistic example, the unique check was deferred until0 码力 | 6321 页 | 107.46 MB | 1 年前3
TiDB v8.0 Documentation### For detailed information why RocksDB needs to implement compaction, see �→ RocksDB-related materials. When write ### traffic (like the importing data size) is big, it is recommended to �→ enable ('dave'), ('sarah'), ('bill'); With optimistic locking and tidb_constraint_check_in_place=OFF: BEGIN OPTIMISTIC; INSERT INTO users (username) VALUES ('jane'), ('chris'), ('bill'); Query OK, 3 rows affected affected (0.00 sec) Records: 2 Duplicates: 0 Warnings: 0 COMMIT; ERROR 1062 (23000): Duplicate entry 'bill' for key 'users.username' In the preceding optimistic example, the unique check was deferred until0 码力 | 6327 页 | 107.55 MB | 1 年前3
TiDB v8.5 Documentation### For detailed information why RocksDB needs to implement compaction, see �→ RocksDB-related materials. When write ### traffic (like the importing data size) is big, it is recommended to �→ enable ('dave'), ('sarah'), ('bill'); With optimistic locking and tidb_constraint_check_in_place=OFF: BEGIN OPTIMISTIC; INSERT INTO users (username) VALUES ('jane'), ('chris'), ('bill'); Query OK, 3 rows affected affected (0.00 sec) Records: 2 Duplicates: 0 Warnings: 0 COMMIT; ERROR 1062 (23000): Duplicate entry 'bill' for key 'users.username' In the preceding optimistic example, the unique check was deferred until0 码力 | 6730 页 | 111.36 MB | 10 月前3
共 30 条
- 1
- 2
- 3













