and auto_increment keys

Problems: 
  1. ALTER TABLE ... ORDER BY... doesn't make sence if there's a 
     user-defined clustered index in the table.
  2. using a secondary index is slower than using a clustered one 
     for a table scan.

Fixes:
  1. raise a warning.
  2. use the clustered index.

into  loke.(none):/home/knielsen/devel/mysql-5.1-new-maint

into  loke.(none):/home/knielsen/devel/mysql-5.1-new-maint

An integer overflow in number->string conversion caused completely
wrong output of the number LONGLONG_MIN with gcc 4.2.1.

Fixed by eliminating the overflow, using only operations that are
well-defined in ANSI C.

into  mysql.com:/home/ram/work/b30679/b30679.5.1

into  mysql.com:/home/ram/work/b30654/b30654.5.1

into  mysql.com:/home/ram/work/b30654/b30654.5.1

names include backticks or blank

Problem: mysqlcheck doesn't escape backtick characters in the table names.

Fix: escape them.

into  mysql.com:/home/ram/work/b31137/b31137.5.1

into  mysql.com:/home/ram/work/b30782/b30782.5.1

JOIN, and ORDER BY

Problem: improper maximum length calculation of the CASE function leads to 
decimal value truncation (storing/retrieving decimal field values).

Fix: accurately calculate maximum length/unsigned flag/decimals parameters 
of the CASE function.

file .\ha_innodb.

Problem: if a partial unique key followed by a non-partial one we declare
the second one as a primary key.

Fix: sort non-partial unique keys before partial ones.

into  polly.(none):/home/kaa/src/maint/mysql-5.1-maint

into  ramayana.hindu.god:/home/tsmith/m/bk/maint/51

into  ramayana.hindu.god:/home/tsmith/m/bk/maint/50

into  ramayana.hindu.god:/home/tsmith/m/bk/maint/51

into  ramayana.hindu.god:/home/tsmith/m/bk/maint/50

into  polly.(none):/home/kaa/src/maint/mysql-5.1-maint

into  polly.(none):/home/kaa/src/maint/mysql-5.1-maint

into  polly.(none):/home/kaa/src/maint/mysql-5.0-maint

into  polly.(none):/home/kaa/src/maint/mysql-5.1-maint

Problem: we skip views perfoming --fix-table-names.

Fix: rename views as well.

into  polly.(none):/home/kaa/src/maint/mysql-5.0-maint

some platforms

Since the behavior of write(fd, buf, 0) is undefined, it may fail with
EFAULT on some architectures when buf == NULL. The error was propagated
up to a caller, since my_write() code did not handle it properly.

Fixed by checking the 'number of bytes' argument in my_write() and
returning before calling the write() system call when there is nothing
to write.

into  mysql.com:/home/ram/work/b31615/b31615.4.1

into  mysql.com:/home/ram/work/b31615/b31615.5.0

into  mysql.com:/home/ram/work/b31615/b31615.5.1

separate checking.

into  pilot.mysql.com:/data/msvensson/mysql/mysql-5.1-new-maint

into  pilot.mysql.com:/data/msvensson/mysql/mysql-5.1-new-maint

into  pilot.mysql.com:/data/msvensson/mysql/mysql-5.0-maint

into  pilot.mysql.com:/data/msvensson/mysql/mysql-5.0-maint

into  mysql.com:/home/ram/work/b31615/b31615.5.1

into  mysql.com:/home/ram/work/b31615/b31615.5.0

into  pilot.mysql.com:/data/msvensson/mysql/bug30560/my51-bug30560

into  mysql.com:/scratch/tnurnberg/20901/51-20901

into  mysql.com:/home/ram/work/b31604/b31604.5.1

into  mysql.com:/home/ram/work/b31349/b31349.5.0