1. 15 Mar, 2007 5 commits
  2. 14 Mar, 2007 23 commits
    • unknown's avatar
      Merge mysql.com:/home/kent/bk/tmp/mysql-5.0-build · 7304af7b
      unknown authored
      into  mysql.com:/home/kent/bk/tmp/mysql-5.1-build
      
      
      7304af7b
    • unknown's avatar
      Merge mysql.com:/home/kent/bk/tmp/mysql-4.1-build · 26a7c7ed
      unknown authored
      into  mysql.com:/home/kent/bk/tmp/mysql-5.0-build
      
      
      26a7c7ed
    • unknown's avatar
      Merge mysql.com:/home/kent/bk/tmp/mysql-4.0 · eddf23e0
      unknown authored
      into  mysql.com:/home/kent/bk/tmp/mysql-4.1-build
      
      
      eddf23e0
    • unknown's avatar
      EXCEPTIONS-CLIENT: · 377853e2
      unknown authored
        Updated to version 0.6 of the text
      
      
      EXCEPTIONS-CLIENT:
        Updated to version 0.6 of the text
      377853e2
    • unknown's avatar
      merge 5.0->5.1 · 480a4ef9
      unknown authored
      480a4ef9
    • unknown's avatar
      Bug #26794: fixed valgrind warning · 7e237e4f
      unknown authored
      7e237e4f
    • unknown's avatar
      Merge bk-internal:/home/bk/mysql-5.1-opt · 21e580a1
      unknown authored
      into  magare.gmz:/home/kgeorge/mysql/autopush/B26794-merge-5.1-opt
      
      
      21e580a1
    • unknown's avatar
      Merge magare.gmz:/home/kgeorge/mysql/autopush/B26794-5.0-opt · f3a731ca
      unknown authored
      into  magare.gmz:/home/kgeorge/mysql/autopush/B26794-merge-5.1-opt
      
      
      mysql-test/r/select.result:
        Auto merged
      mysql-test/t/select.test:
        Auto merged
      sql/field.cc:
        Auto merged
      sql/filesort.cc:
        Auto merged
      sql/item.cc:
        Auto merged
      sql/item.h:
        Auto merged
      sql/sql_show.cc:
        Auto merged
      sql/sql_table.cc:
        Auto merged
      mysql-test/r/alter_table.result:
        merged 5.0-opt -> 5.1-opt
      mysql-test/r/gis-rtree.result:
        merged 5.0-opt -> 5.1-opt
      mysql-test/r/order_by.result:
        merged 5.0-opt -> 5.1-opt
      mysql-test/r/subselect.result:
        merged 5.0-opt -> 5.1-opt
      mysql-test/t/alter_table.test:
        merged 5.0-opt -> 5.1-opt
      mysql-test/t/order_by.test:
        merged 5.0-opt -> 5.1-opt
      mysql-test/t/subselect.test:
        merged 5.0-opt -> 5.1-opt
      f3a731ca
    • unknown's avatar
      Bug #26794: fixed valgrind warning · ff810fb9
      unknown authored
      ff810fb9
    • unknown's avatar
      Merge mysql.com:/home/kent/bk/tmp/mysql-5.0-build · b249782b
      unknown authored
      into  mysql.com:/home/kent/bk/tmp/mysql-5.1-build
      
      
      configure.in:
        Auto merged
      storage/ndb/src/ndbapi/NdbBlob.cpp:
        Auto merged
      storage/ndb/test/ndbapi/testBlobs.cpp:
        Auto merged
      b249782b
    • unknown's avatar
      Merge kboortz@bk-internal.mysql.com:/home/bk/mysql-5.1 · 2b183b55
      unknown authored
      into  mysql.com:/home/kent/bk/tmp/mysql-5.1-build
      
      
      2b183b55
    • unknown's avatar
      Merge mysql.com:/home/kent/bk/tmp/mysql-4.1-build · 29e6d308
      unknown authored
      into  mysql.com:/home/kent/bk/tmp/mysql-5.0-build
      
      
      configure.in:
        Auto merged
      29e6d308
    • unknown's avatar
      Merge kboortz@bk-internal.mysql.com:/home/bk/mysql-5.0 · 1c02d8c0
      unknown authored
      into  mysql.com:/home/kent/bk/tmp/mysql-5.0-build
      
      
      1c02d8c0
    • unknown's avatar
      Merge kboortz@bk-internal.mysql.com:/home/bk/mysql-4.1 · f4656c37
      unknown authored
      into  mysql.com:/home/kent/bk/tmp/mysql-4.1-build
      
      
      f4656c37
    • unknown's avatar
      Merge mysql.com:/home/kent/bk/tmp/mysql-4.0 · 9be5d518
      unknown authored
      into  mysql.com:/home/kent/bk/tmp/mysql-4.1-build
      
      
      configure.in:
        SCCS merged
      9be5d518
    • unknown's avatar
      configure.in: · 0f7f7ff8
      unknown authored
        Added test for sched_yield() possibly in -lposix4 on Solaris
      
      
      configure.in:
        Added test for sched_yield() possibly in -lposix4 on Solaris
      0f7f7ff8
    • unknown's avatar
      Merge mhansson@bk-internal.mysql.com:/home/bk/mysql-5.1-opt · 8fa44178
      unknown authored
      into  dl145s.mysql.com:/users/mhansson/mysql/autopush/5.1o-bug24778
      
      
      8fa44178
    • unknown's avatar
      WL#3527 : inspected a 5.1 covarage report · f0c50440
      unknown authored
      
      sql/item.cc:
        WL#3527 : inspected a covarage report
      f0c50440
    • unknown's avatar
      Bug #24778: Innodb: No result when using ORDER BY · 7a3148a7
      unknown authored
      This bug was intruduced by the fix for bug#17212 (in 4.1). It is not 
      ok to call test_if_skip_sort_order since this function will 
      alter the execution plan. By contract it is not ok to call 
      test_if_skip_sort_order in this context.
      
      This bug appears only in the case when the optimizer has chosen 
      an index for accessing a particular table but finds a covering 
      index that enables it to skip ORDER BY. This happens in 
      test_if_skip_sort_order.
      
      
      mysql-test/r/key.result:
        Bug#24778
        
        test case.
        
        The bug causes the result to be the empty set.
      mysql-test/t/key.test:
        Bug#24778
        
        The minimal test case that reveals the bug. The reason for such a 
        complicated schema is that we have to convince the optimizer to 
        pick one index, then discard it in order to be able to skip 
        ORDER BY.
      sql/sql_select.cc:
        bug#24778
        
        Removed the call to test_if_skip_sort_order that constituted the
        bug.
      7a3148a7
    • unknown's avatar
      Bug #26794: 5.1 part · 6e10a204
      unknown authored
       It was syntactically correct to define 
       spatial keys over parts of columns (e.g.
       ALTER TABLE t1 ADD x GEOMETRY NOT NULL, 
         ADD SPATIAL KEY (x(32))).
       This may lead to undefined results and/or
       interpretation.
       Fixed by not allowing partial column 
       specification in a SPATIAL index definition.
      
      
      mysql-test/r/alter_table.result:
        Bug #26794: 5.1 part
         test case
      mysql-test/r/gis-rtree.result:
        Bug #26794: 5.1 part
         updated the tests to the new syntax
      mysql-test/t/alter_table.test:
        Bug #26794: 5.1 part
         test case
      mysql-test/t/gis-rtree.test:
        Bug #26794: 5.1 part
         updated the tests to the new syntax
      sql/sql_table.cc:
        Bug #26794: 5.1 part
         Disable defining SPATIAL KEYS with sub-key parts
      6e10a204
    • unknown's avatar
      Merge gkodinov@bk-internal.mysql.com:/home/bk/mysql-5.0-opt · 347e832a
      unknown authored
      into  magare.gmz:/home/kgeorge/mysql/autopush/B26794-5.0-opt
      
      
      sql/field.cc:
        Auto merged
      347e832a
    • unknown's avatar
      Bug #26794: · a22f257e
      unknown authored
      Different set of conditions is used to verify
      the validity of index definitions over a GEOMETRY
      column in ALTER TABLE and CREATE TABLE. 
      The difference was on how sub-keys notion validity
      is checked.
      Fixed by extending the CREATE TABLE condition to
      support the cases allowed in ALTER TABLE.
      Made the SHOW CREATE TABLE not to display spatial
      indexes using the sub-key notion.
      
      
      mysql-test/r/alter_table.result:
        Bug #26794: test case
      mysql-test/r/gis-rtree.result:
        Bug #26794: fixed SHOW CREATE TABLE output.
      mysql-test/t/alter_table.test:
        Bug #26794: test case
      sql/field.cc:
        Bug #26794: Allow sub-keys for GEOMETRY
      sql/sql_show.cc:
        Bug #26794: Don't show sub-key notion 
         in SHOW CREATE TABLE for SPATIAL indexes.
      sql/sql_table.cc:
        Bug #26794: Allow sub-keys for GEOMETRY
      a22f257e
    • unknown's avatar
      Merge mysql.com:/home/svoj/devel/mysql/BUG26881/mysql-5.0-engines · 8deff6b0
      unknown authored
      into  mysql.com:/home/svoj/devel/mysql/BUG26881/mysql-5.1-engines
      
      
      storage/myisam/mi_open.c:
        Auto merged
      8deff6b0
  3. 13 Mar, 2007 10 commits
    • unknown's avatar
      Removed tabs. · 8205e16c
      unknown authored
      8205e16c
    • unknown's avatar
      Merge gkodinov@bk-internal.mysql.com:/home/bk/mysql-5.0-opt · 4108ca96
      unknown authored
      into  magare.gmz:/home/kgeorge/mysql/autopush/B26672-5.0-opt
      
      
      mysql-test/r/order_by.result:
        Auto merged
      mysql-test/t/order_by.test:
        Auto merged
      4108ca96
    • unknown's avatar
      Merge mysql.com:/home/svoj/devel/mysql/BUG26881/mysql-5.0-engines · 6095508b
      unknown authored
      into  mysql.com:/home/svoj/devel/mysql/BUG26881/mysql-5.1-engines
      
      
      mysql-test/r/merge.result:
        Auto merged
      mysql-test/t/merge.test:
        Auto merged
      sql/sql_parse.cc:
        Auto merged
      storage/myisam/ha_myisam.cc:
        Auto merged
      storage/myisam/mi_create.c:
        Auto merged
      6095508b
    • unknown's avatar
      Merge mysql.com:/home/svoj/devel/mysql/BUG26881/mysql-4.1-engines · 968d1695
      unknown authored
      into  mysql.com:/home/svoj/devel/mysql/BUG26881/mysql-5.0-engines
      
      
      myisam/mi_create.c:
        Auto merged
      mysql-test/t/merge.test:
        Auto merged
      sql/ha_myisam.cc:
        Auto merged
      sql/sql_parse.cc:
        Use local.
      mysql-test/r/merge.result:
        SCCS merged
      968d1695
    • unknown's avatar
      BUG#26881 - Large MERGE tables report incorrect specification when no · 969b7165
      unknown authored
                  differences in tables
      Certain merge tables were wrongly reported as having incorrect definition:
      - Some fields that are 1 byte long (e.g. TINYINT, CHAR(1)), might
        be internally casted (in certain cases) to a different type on a
        storage engine layer. (affects 4.1 and up)
      - If tables in a merge (and a MERGE table itself) had short VARCHAR column (less
        than 4 bytes) and at least one (but not all) tables were ALTER'ed (even to an
        identical table: ALTER TABLE xxx ENGINE=yyy), table definitions went ouf of
        sync. (affects 4.1 only)
      
      This is fixed by relaxing a check for underlying conformance and setting
      field type to FIELD_TYPE_STRING in case varchar is shorter than 4
      when a table is created.
      
      
      myisam/mi_create.c:
        Added a comment.
      mysql-test/r/merge.result:
        A test case for bug#26881.
      mysql-test/t/merge.test:
        A test case for bug#26881.
      sql/ha_myisam.cc:
        Relaxed some checks performed by check_definition():
        As comparing of fulltext keys (and key segments) is not yet implemented,
        only return an error in case one of keys is fulltext and other is not.
        Otherwise, if both keys are fulltext, accept them as is.
        
        As comparing of spatial keys (and key segments) is not yet implemented,
        only return an error in case one of keys is spatial and other is not.
        Otherwise, if both keys are spatial, accept them as is.
        
        A workaround to handle situation when field is casted from FIELD_SKIP_ZERO
        to FIELD_NORMAL. This could happen only in case field length is 1 and row
        format is fixed.
      sql/sql_parse.cc:
        When a table that has varchar field shorter than 4 is created, field type is
        set to FIELD_TYPE_VAR_STRING. Later, when a table is modified using alter
        table, field type is changed to FIELD_TYPE_STRING (see Field_string::type).
        That means HA_OPTION_PACK_RECORD flag might be lost and thus null_bit might
        be shifted by alter table, in other words alter table doesn't create 100%
        equal table definition.
        
        This is usually not a problem, since when a table is created/altered,
        definition on a storage engine layer is based on one that is passed from
        sql layer. But it is a problem for merge engine - null_bit is shifted when
        a table (merge or underlying) is altered.
        
        Set field type to FIELD_TYPE_STRING in case FIELD_TYPE_VAR_STRING is shorter
        than 4 when a table is created as it is done in Field::type.
      969b7165
    • unknown's avatar
      Merge mysql.com:/home/svoj/devel/mysql/BUG26881/mysql-5.0-engines · 4f20ff2f
      unknown authored
      into  mysql.com:/home/svoj/devel/mysql/BUG26881/mysql-5.1-engines
      
      
      sql/field.h:
        Auto merged
      storage/myisam/rt_index.c:
        Auto merged
      4f20ff2f
    • unknown's avatar
      Merge mysql.com:/home/svoj/devel/bk/mysql-5.1 · 36a27948
      unknown authored
      into  mysql.com:/home/svoj/devel/mysql/BUG26881/mysql-5.1-engines
      
      
      storage/myisam/mi_open.c:
        Use local.
      36a27948
    • unknown's avatar
      Merge mysql.com:/home/svoj/devel/mysql/BUG26881/mysql-4.1-engines · 063c95e6
      unknown authored
      into  mysql.com:/home/svoj/devel/mysql/BUG26881/mysql-5.0-engines
      
      
      063c95e6
    • unknown's avatar
      Merge mysql.com:/home/svoj/devel/bk/mysql-5.0 · d496ab15
      unknown authored
      into  mysql.com:/home/svoj/devel/mysql/BUG26881/mysql-5.0-engines
      
      
      myisam/rt_index.c:
        Auto merged
      sql/field.h:
        Auto merged
      d496ab15
    • unknown's avatar
      Merge mysql.com:/home/svoj/devel/bk/mysql-4.1 · e266365c
      unknown authored
      into  mysql.com:/home/svoj/devel/mysql/BUG26881/mysql-4.1-engines
      
      
      e266365c
  4. 12 Mar, 2007 2 commits