into  mysql.com:/home/dlenev/mysql-5.0-bg15153-2

Error was emitted when one tried to select information from view which used
merge algorithm and which also had CONVERT_TZ() function in its select list.

This bug was caused by wrong assumption that global table list for view
which is handled using merge algorithm begins from tables belonging to
the main select of this view. Nowadays the above assumption is not true only
when one uses convert_tz() function in view's select list, but in future
other cases may be added (for example we may support merging of views
with subqueries in select list one day). Relying on this false assumption
led to the usage of wrong table list for field lookups and therefor errors. 

With this fix we explicitly use pointer to the beginning of main select's
table list.

Do not reset value of LAST_INSERT_ID() in sub-statement.

Fixed windows compile error in sql/sp.cc (missing cast to byte*)

into  mysql.com:/extern/mysql/5.0/bug18344/mysql-5.0-runtime

into  mysql.com:/extern/mysql/5.0/bug18949/mysql-5.0-runtime

into  mysql.com:/home/dlenev/mysql-5.0-bg16021

which was caused by the same bulk insert optimization as bug #17764 but
had slightly different symptoms.

into  mysql.com:/home/stewart/Documents/MySQL/5.0/merge

  We must use the db key length in sp_drop_db_routines (and not the
  number of characters), or long db names will be truncated in the key.

into  mysql.com:/extern/mysql/5.0/bug18787/mysql-5.0-runtime

Item_func_sp::tmp_table_field() to something more descriptive.

  Removed sp-goto.test, sp-goto.result and all (disabled) GOTO code.
  Also removed some related code that's not needed any more (no possible
  unresolved label references any more, so no need to check for them).
  NB: Keeping the ER_SP_GOTO_IN_HNDLR in errmsg.txt; it might become useful
      in the future, and removing it (and thus re-enumerating error codes)
      might upset things. (Anything referring to explicit error codes.)

into  mysql.com:/home/stewart/Documents/MySQL/5.0/merge

into  zippy.(none):/home/cmiller/work/mysql/mysql-5.0__ready

into  zippy.(none):/home/cmiller/work/mysql/mysql-5.0__ready

  Testsuite added

  5.0 additional fix for b#18691
  Handle DECIMAL the same with INT and REAL.

into  mysql.com:/usr/home/bar/mysql-5.0

does not have "NOT NULL" attribute set.  Also, calculate the padding
characters more safely, so that a negative number doesn't cause it to 
print MAXINT-n spaces.

into  april.(none):/home/svoj/devel/mysql/BUG17917/mysql-5.0

removing comments from the opt file.

into  mysql.com:/usr/home/bar/mysql-4.1.b18691

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

into  mysql.com:/opt/local/work/mysql-5.0-runtime-merge

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

into  mysql.com:/opt/local/work/mysql-5.0-runtime-merge

into  dl145j.mysql.com:/tmp/andrei/5.0-bug18715_drop_view_slave

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

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

into  mysql.com:/home/MySQL/5.0-Bug-17248a

into  mysql.com:/home/psergey/mysql-5.0-csc9139

get_best_covering_ror_intersect() was copying ror_scans starting from the 
end of the array and not from its beginning.

into  april.(none):/home/svoj/devel/mysql/BUG17917/mysql-4.1

into  april.(none):/home/svoj/devel/mysql/BUG17917/mysql-4.1

Retrieving data from compressed MyISAM table which is bigger than 4G on 32-bit box
with mmap() support results in server crash.

mmap() accepts length of bytes to be mapped in second param, which is 32-bit
size_t. But we pass data_file_length, which is 64-bit my_off_t. As a result only
first data_file_length % 4G were mapped.

This fix adds additional condition for mmap() usage, that is use mmap() for
compressed table which size is no more than 4G on 32-bit platform.