Under strict mode MySQL will generate an error message if there was any conversion when assigning data to a field.
Added checking of date/datetime fields.
If strict mode, give error if we have not given value to field without a default value (for INSERT)

Removed wrong warnings in test suite (This was because select_insert / select_create results was not freed.
Added thd to openfrm() for initialization of TABLE->in_use. This fixed a bug in BDB handling where table->in_use was used early

This allows one to setup a master <-> master replication with non conflicting auto-increment series.
Cleaned up binary log code to make it easyer to add new state variables.
Added simpler 'upper level' logic for artificial events (events that should not cause cleanups on slave).
Simplified binary log handling.
Changed how auto_increment works together with to SET INSERT_ID=# to make it more predictable: Now the inserted rows in a multi-row statement are set independent of the existing rows in the table. (Before only InnoDB did this correctly)

into sanja.is.com.ua:/home/bell/mysql/bk/mysql-5.0

fixed privilege system upgrade script, to allow VIEW privileges for used who have CREATE privilege (BUG#5329)

into mysql.com:/home/cps/mysql/devel/im/default_patch/mysql-5.0

options.

test result.

  Make "FRAC_SECOND"/"SQL_TSI_FRAC_SECOND" non-reserved words,
  must like "SECOND"/"SQL_TSI_SECOND", "MINUTE"/"SQL_TSI_MINUTE",
  etc.
  Will wait for okay to push. (It doesn't break any tests.)

into mysql.com:/home/pem/work/mysql-5.0-merge

into sanja.is.com.ua:/home/bell/mysql/bk/work-show-5.0

  Dropping the table was not the real problem, the problem was with errors
  occuring within error handlers.

Added previously missing sql_trigger.cc file to embedded library.

into sanja.is.com.ua:/home/bell/mysql/bk/work-show-5.0

into mysql.com:/home/dlenev/src/mysql-5.0-1218-a

into mishka.local:/home/my/mysql-5.0

Fixed (together with Guilhem) bugs in mysqlbinlog regarding --offset
Prefix addresses with 0x for easier comparisons of debug logs
Fixed problem where MySQL choosed index-read even if there would be a much better range on the same index
This fix changed some 'index' queries to 'range' queries in the test suite
Don't create 'dummy' WHERE clause for trivial WHERE clauses where we can remove the WHERE clause.
This fix removed of a lot of 'Using where' notes in the test suite.
Give NOTE instead of WARNING if table/function doesn't exists when using DROP IF EXISTS
Give NOTE instead of WARNING for safe field-type conversions

After review and after merge fixes.

  Easy to prevent crash, but the question was how to treat this case?
  We ended up implementing the "global" SPs (i.e. with no associated
  db), which were planned but left unresolved when SPs moved into dbs.
  So now things like "call .p()" work too.

  Althought techically not a but (as it's functioning as designed),
  it was decided that the design should be changed. Some users have
  a problem with dates being '0000-00-00' and the SQL standard specifies
  that the modification date should be the same as the creation date
  at creation.