into ibmlab.site:/home/my/bk/mysql-5.0

into hundin.mysql.fi:/home/jan/mysql-5.0

into hundin.mysql.fi:/home/jan/mysql-5.0

into ibmlab.site:/home/my/bk/mysql-4.1

upper/lower conversion for LATIN LETTER D WITH STROKE
was wrong in latin2.

into hundin.mysql.fi:/home/marko/mysql-5.0.4

into mysql.com:/root/mysql-5.0

into mysql.com:/root/mysql-5.0

into mysql.com:/home/dlenev/src/mysql-5.0-bg9841

into hundin.mysql.fi:/home/marko/mysql-4.1

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

into mysql.com:/root/mysql-5.0

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

into mysql.com:/space/my/mysql-4.1-build

into mysql.com:/space/my/mysql-5.0-build

into mysql.com:/home/hf/work/mysql-5.0.prec

into mysql.com:/home/shuichi/apps/mysql/bk/4.1/mysql

into quadita2.mysql.com:/nfstmp1/guilhem/mysql-5.0-4ita

We cannot propagate constants with tricky collations.

a stored procedure" (version 2).

To handle updates and inserts into view in SP properly we should set
lock types for tables of the view's main select when we are opening
view for prelocking purproses.

Mostly about precision/decimals of the results of the operations

into ram-book.(none):/home/ram/work/5.0

into sergbook.mylan:/usr/home/serg/Abk/mysql-5.0

into quadita2.mysql.com:/nfstmp1/guilhem/mysql-5.0-4ita

  Approximative fixes for BUG#2610,2611,9100 i.e. WL#2146 binlogging/replication of routines (stored procs and functions).
  Approximative, because it's using our binlogging way (what we call "query"-level) and this is not as good as record-level binlog (5.1) would be. It imposes several
  limitations to routines, and has caveats (which I'll document, and for which the server will try to issue errors but that is not always possible).
  Reason I don't propagate caller info to the binlog as planned is that on master and slave
  users may be different; even with that some caveats would remain.