----------------------------------------------------------------------- WORKLOG TASK -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- TASK...........: support many clustered keys per table CREATION DATE..: Sun, 25 Apr 2010, 16:23 SUPERVISOR.....: Sergei IMPLEMENTOR....: COPIES TO......: CATEGORY.......: Server-BackLog TASK ID........: 113 (http://askmonty.org/worklog/?tid=113) VERSION........: Server-5.3 STATUS.........: Un-Assigned PRIORITY.......: 60 WORKED HOURS...: 0 ESTIMATE.......: 0 (hours remain) ORIG. ESTIMATE.: 0 PROGRESS NOTES: -=-=(Serg - Mon, 10 May 2010, 14:35)=-=- Category updated. --- /tmp/wklog.113.old.7118 2010-05-10 14:35:50.000000000 +0000 +++ /tmp/wklog.113.new.7118 2010-05-10 14:35:50.000000000 +0000 @@ -1 +1 @@ -Server-Sprint +Server-BackLog -=-=(Serg - Mon, 10 May 2010, 14:35)=-=- Version updated. --- /tmp/wklog.113.old.7105 2010-05-10 14:35:25.000000000 +0000 +++ /tmp/wklog.113.new.7105 2010-05-10 14:35:25.000000000 +0000 @@ -1 +1 @@ -Server-9.x +Server-5.3 DESCRIPTION: The server now assumes that there can be only one clustered key per table, and only primary key can be clustered. It's not true for certain storage engines, we need to remove this limitation ESTIMATED WORK TIME ESTIMATED COMPLETION DATE ----------------------------------------------------------------------- WorkLog (v3.5.9)