summaryrefslogtreecommitdiff
path: root/mysql-test/t
diff options
context:
space:
mode:
authorunknown <monty@mysql.com>2006-06-30 18:29:27 +0300
committerunknown <monty@mysql.com>2006-06-30 18:29:27 +0300
commita616b65e73f5ceedcc12df662c2fee0b5e8754d5 (patch)
treeb32804ac8755f9a1db6113b996ee5dfda0e7a65f /mysql-test/t
parentaa5ecc4cb22e81ae66e1515a4471fd212fe18c6d (diff)
downloadmariadb-git-a616b65e73f5ceedcc12df662c2fee0b5e8754d5.tar.gz
Reverted wrong bug fix (Bug#11228)
mysql-test/r/key.result: Fixed result after removing wrong bug fix mysql-test/t/key.test: Added SHOW CREATE TABLE, which is the proper way to check for table definitions sql/table.cc: Reverted wrong bug fix. The intention with the original code was to show that MySQL treats the first given unique key as a primary key. Clients can use the marked primary key as a real primary key to validate row changes in case of conflicting updates. The ODBC driver (and other drivers) may also use this fact to optimize/check updates and handle conflicts. The marked key also shows what some engines, like InnoDB or NDB, will use as it's internal primary key. For checking if someone has declared a true PRIMARY KEY, one should use 'SHOW CREATE TABLE'
Diffstat (limited to 'mysql-test/t')
-rw-r--r--mysql-test/t/key.test1
1 files changed, 1 insertions, 0 deletions
diff --git a/mysql-test/t/key.test b/mysql-test/t/key.test
index 796e36cb608..9aab8a13b06 100644
--- a/mysql-test/t/key.test
+++ b/mysql-test/t/key.test
@@ -330,6 +330,7 @@ create table t1 (
UNIQUE i1idx (i1),
UNIQUE i2idx (i2));
desc t1;
+show create table t1;
drop table t1;
#