and CHARSET is now the same with CHARACTER SET:

CREATE DATABASE name 
  [DEFAULT] {CHAR SET | CHARACTER SET | CHARSET} csname


CREATE TABLE (...)  [DEFAULT] {CHARSET | CHARACTER SET | CHAR SET} [=] csname

To Paul and Arjen:
However this should be recommended in db option to conform SQL99:
CREATE DATABASE dbname DEFAULT CHARACTER SET csname
In table option there is no SQL99 recommended syntax as far as
table charset is MySQL extension.

into sanja.is.com.ua:/home/bell/mysql/work-distinct-4.1

small Item_ref fix

CREATE TABLE a (...) TYPE isam  CHARSET latin1  MAX_ROWS 1000;
CREATE TABLE a (...) TYPE=isam  CHARSET=latin1  MAX_ROWS=1000;
CREATE TABLE a (...) TYPE isam, CHARSET latin1, MAX_ROWS 1000;
CREATE TABLE a (...) TYPE=isam, CHARSET=latin1, MAX_ROWS=1000;

CREATE TABLE a (...) TYPE isam  CHARSET latin1  MAX_ROWS 1000;
CREATE TABLE a (...) TYPE=isam  CHARSET=latin1  MAX_ROWS=1000;

  max_sort_char is 255 for binary

  character set binary didn't work

into bar.mysql.r18.ru:/usr/home/bar/mysql-4.1.wrk

  binary charset
ctype-bin.c:
  new file

into serg.mysql.com:/usr/home/serg/Abk/mysql-4.1

into sinisa.nasamreza.org:/mnt/work/mysql-4.1

into sinisa.nasamreza.org:/mnt/work/mysql-4.1

And I am not able to find a Changelog for 4.1

I intend to do some more accelerations in mysql_execute_command and
in SQLCOM_SELECT part for which I need to fix EXPLAIN with derived
tables plus few additional items. If this proves to be much I wil
just make it a new SCRUM task

Ignore changed keyblocks when on does DELETE FROM table_name;

into sinisa.nasamreza.org:/mnt/work/mysql-4.1

into fred.bitbike.com:/home/arjen/mysql-4.1

into sanja.is.com.ua:/home/bell/mysql/work-distinct-4.1