SQL_BUFFER_RESULT and SQL_CALC_FOUND_ROWS in same SELECT broken

>Description: *** against BK as of set 1.1144 *** It appears that putting SQL_BUFFER_RESULT and SQL_CALC_FOUND_ROWS in the same SELECT statement is a really bad idea! SELECT FOUND_ROWS() after SELECT SQL_BUFFER_RESULT SQL_CALC_FOUND_ROWS either returns a h

create index on table breaks tables! ("n parts found, should be 0 parts")

>Description: Under either mysql 4.0.1 binary RPM from mysql, locally built 4.0.1, or bk set 1.1079, adding an index to a table causes the number of expected parts in that table to be set to 0. >How-To-Repeat: State of table (dirty, clean, just rebuilt, doesn't ma

Failure to enforce length of fields to index corrupts tables

>Description: Documentation section 6.5.7 regarding create index states: "For CHAR and VARCHAR columns, indexes can be created that use only part of a column, using col_name(length) syntax. (On BLOB and TEXT columns the length is required.)" It's still possible in the mysql clien