Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Commits on Jun 13, 2008
  1. Merging bug fixes for 34995 and 35543 into the main tree,

    Joerg Bruehe committed
    and the build tag for 5.0.62.
  2. No change - hack to force BZR conversion

    Unknown committed
Commits on Jun 10, 2008
  1. Raise version number after cloning 5.0.64

    mysqldev committed
Commits on Jun 3, 2008
  1. @gkodinov
Commits on May 25, 2008
  1. Merge trift-lap.fambruehe:/MySQL/M50/mysql-5.0

    Unknown committed
    into  trift-lap.fambruehe:/MySQL/M50/work-5.0
Commits on May 22, 2008
  1. Merge metainfo for mailer plugin.

    Chad Miller committed
Commits on May 21, 2008
  1. Add branch metainfo for mailer plugin.

    Chad MILLER committed
Commits on May 18, 2008
  1. Merge host.loc:/work/bugs/5.0-bugteam-36676

    Unknown committed
    into  host.loc:/work/bk/5.0-bugteam
  2. Fixed bug#36676: multiupdate using LEFT JOIN updates only

    Unknown committed
                     first row or fails with an error:
      ERROR 1022 (23000): Can't write; duplicate key in table ''
    The server uses intermediate temporary table to store updated
    row data.  The first column of this table contains rowid.
    Current server implementation doesn't reset NULL flag of that
    column even if the server fills a column with rowid.
    To keep each rowid unique, there is an unique index.
    An insertion into an unique index takes into account NULL
    flag of key value and ignores real data if NULL flag is set.
    So, insertion of actually different rowids may lead to two
    kind of problems.  Visible effect of each of these problems
    depends on an initial engine type of temporary table:
    1. If multiupdate initially creates temporary table as
    a MyISAM table (a table contains blob columns, and the
    create_tmp_table function assumes, that this table is
    large), it inserts only one single row and updates
    only rows with one corresponding rowid. Other rows are
    silently ignored. 
    2. If multiupdate initially creates MEMORY temporary
    table, fills it with data and reaches size limit for
    MEMORY tables (max_heap_table_size), multiupdate
    converts MEMORY table into MyISAM table and fails
    with an error:
      ERROR 1022 (23000): Can't write; duplicate key in table ''
    Multiupdate has been fixed to update the NULL flag of
    temporary table rowid columns.
Commits on May 17, 2008
  1. Bug #36705 key_buffer_size of >= 2G allocates all availabel virtual m…

    none committed
    …emory on 64-bit wondo.
    temporary variables of 'long' types were used to store ulong values,
    that causes init_key_cache to receive distorted parameters
Commits on May 16, 2008
  1. Merge

    Unknown committed
  2. Merge

    Unknown committed
  3. Merge

    Unknown committed
    into  magare.gmz:/home/kgeorge/mysql/autopush/B36011-take2-5.0-bugteam
  4. Add a test at Andrei's behest. Show the SHOW CREATE on the

    Unknown committed
    master also, so that we can visually see the slave is the same.
  5. Bug #36011: server crash with explain extended on query

    Unknown committed
       with dependent subqueries
    An IN subquery is executed on EXPLAIN when it's not correlated.
    If the subquery required a temporary table for its execution
    not all the internal structures were restored from pointing to
    the items of the temporary table to point back to the items of
    the subquery.
    Fixed by restoring the ref array when a temp tables were used in
    executing the IN subquery during EXPLAIN EXTENDED.
  6. Merge

    Unknown committed
  7. Raise version number after cloning 5.0.62

    Unknown committed
  8. Merge host.loc:/work/bugs/5.0-bugteam-36488

    Unknown committed
    into  host.loc:/work/bk/5.0-bugteam
Commits on May 15, 2008
  1. Bug#36570: Parse error of CREATE PROCEDURE stmt with comments on \

    Unknown committed
    The stored-routine code took the contents of the (lowest) parser
    and copied it directly to the binlog, which causes problems if there
    is a special case of interpretation at the parser level -- which 
    there is, in the "/*!VER */" comments.  The trailing "*/" caused
    errors on the slave, naturally.
    Now, since by that point we have /properly/ created parse-tree (as 
    the rest of the server should do!) for the stored-routine CREATE, we
    can construct a perfect statement from that information, instead of
    writing uncertain information from an unknown parser state.  
    Fortunately, there's already a function nearby that does exactly 
    Update for Bug#36570.  Qualify routine names with db name when
    writing to the binlog ONLY if the source text is qualified.
Commits on May 14, 2008
  1. Merge bk-internal:/home/bk/mysql-5.0

    Unknown committed
    into  magare.gmz:/home/kgeorge/mysql/work/merge-5.0-bugteam
Commits on May 13, 2008
  1. Fixed bug #36488: regexp returns false matches, concatenating

    Unknown committed
                      with previous rows.
    The WHERE clause containing expression:
      CONCAT(empty_field1, empty_field2, ..., 'literal constant', ...)
        REGEXP 'regular expression'
    may return wrong matches.
    Optimization of the CONCAT function has been fixed.
  2. Merge

    none committed
  3. Merge host.loc:/work/bugs/5.0-bugteam-30059

    Unknown committed
    into  host.loc:/work/bk/5.0-bugteam
Commits on May 12, 2008
  1. Merge host.loc:/work/bugs/5.0-bugteam-36055

    Unknown committed
    into  host.loc:/work/bk/5.0-bugteam
  2. Fixed bug #36055: mysql_upgrade doesn't really 'upgrade' tables

    Unknown committed
    The REPAIR TABLE ... USE_FRM query silently corrupts data of tables
    with old .FRM file version.
    The mysql_upgrade client program or the REPAIR TABLE query (without
    the USE_FRM clause) can't prevent this trouble, because in the
    common case they don't upgrade .FRM file to compatible structure.
    1. Evaluation of the REPAIR TABLE ... USE_FRM query has been
       modified to reject such tables with the message:
       "Failed repairing incompatible .FRM file".
    2. REPAIR TABLE query (without USE_FRM clause) evaluation has been
       modified to upgrade .FRM files to current version.
    3. CHECK TABLE ... FOR UPGRADE query evaluation has been modified
       to return error status when .FRM file has incompatible version.
    4. mysql_upgrade and mysqlcheck client programs call CHECK TABLE
       FOR UPGRADE and REPAIR TABLE queries, so their behaviors have
       been changed too to upgrade .FRM files with incompatible
       version numbers.
Commits on May 9, 2008
  1. BUG#35543 does not properly work with tmp files

    none committed
     - Backport to 5.0, use --local-load to instruct myqlbinlog where to 
     put the files it generate
Commits on May 8, 2008
  1. Merge…

    Unknown committed
  2. Bug#32575 - Parse error of stmt with extended comments on slave side

    Unknown committed
    Problem was that mysql_create_view did not remove all comments characters
    when writing to binlog, resulting in parse error of stmt on slave side.
    Solution was to use the recreated select clause
    and add a generated CHECK OPTION clause if needed.
Commits on May 6, 2008
  1. Partial rollback of fix for bug #30059: End-space truncation is incon…

    Unknown committed
    or incorrect.
    For better conformance with standard, truncation procedure of CHAR columns
    has been changed to ignore truncation of trailing whitespace characters
    (note has been removed).
    Finally, for columns with non-binary charsets:
    1. CHAR(N) columns silently ignore trailing whitespace truncation;
    2. VARCHAR and TEXT columns issue Note about truncation.
    BLOBs and other columns with BINARY charset are unaffected.
  2. revert the push of bug 35616.

    Unknown committed
  3. Bug#35616: memory overrun on 64-bit linux on setting large values for…

    Unknown committed
    … keybuffer-size
    We could allocate chunks larger than 4GB, but did our size-accounting in 32-bit
    values. This could lead to spurious warnings, inaccurate accounting, and, in
    theory, data loss.
    Affected: 64-bit platforms. Debug-build (with safemalloc). At least one buffer
    larger than 4GB. For potential data loss, a re-alloc on such a buffer would be
Commits on May 5, 2008
  1. Merge bk-internal:/home/bk/mysql-5.0

    Unknown committed
    into  magare.gmz:/home/kgeorge/mysql/work/merge-5.0-bugteam
Commits on May 2, 2008
  1. Merge

    Unknown committed
  2. Merge

    Unknown committed
Something went wrong with that request. Please try again.