1. 07 Jul, 2006 1 commit
    • unknown's avatar
      ndb - bug#20847 : DbtupTabDesMan: add merge with left buddies · 2c48aaa1
      unknown authored
      
      ndb/src/kernel/blocks/ERROR_codes.txt:
        DbtupTabDesMan: add merge with left buddies
      ndb/src/kernel/blocks/dbtup/Dbtup.hpp:
        DbtupTabDesMan: add merge with left buddies
      ndb/src/kernel/blocks/dbtup/DbtupMeta.cpp:
        DbtupTabDesMan: add merge with left buddies
      ndb/src/kernel/blocks/dbtup/DbtupTabDesMan.cpp:
        DbtupTabDesMan: add merge with left buddies
      ndb/test/ndbapi/testDict.cpp:
        DbtupTabDesMan: add merge with left buddies
      ndb/test/run-test/daily-basic-tests.txt:
        DbtupTabDesMan: add merge with left buddies
      2c48aaa1
  2. 04 Jul, 2006 2 commits
  3. 30 Jun, 2006 14 commits
  4. 29 Jun, 2006 9 commits
  5. 28 Jun, 2006 3 commits
  6. 27 Jun, 2006 6 commits
    • unknown's avatar
      Bug#19298 mysqld_safe still uses obsolete --skip-locking parameter · 7b064953
      unknown authored
      
      configure.in:
        Replaced skip-locking with newer skip-external-locking option.  Removed extra quotes.
      scripts/mysqld_safe-watch.sh:
        Replaced skip-locking with newer skip-external-locking option.
      7b064953
    • unknown's avatar
      BUG#1662 - ALTER TABLE LIKE ignores DATA/INDEX DIRECTPORY · f4a07612
      unknown authored
      Produce a warning if DATA/INDEX DIRECTORY is specified in
      ALTER TABLE statement.
      
      Ignoring of these options is documented in the symbolic links
      section of the manual.
      
      
      mysql-test/r/symlink.result:
        Modified test result according to fix for BUG#1662.
      sql/sql_parse.cc:
        Produce a warning if DATA/INDEX DIRECTORY is specified in
        ALTER TABLE statement.
      f4a07612
    • unknown's avatar
      Merge mysql.com:/home/kgeorge/mysql/4.1/teamclean · 2eb16be0
      unknown authored
      into  mysql.com:/home/kgeorge/mysql/4.1/B16458
      
      
      2eb16be0
    • unknown's avatar
      Dec. 31st, 9999 is still a valid date, only starting with Jan 1st 10000 things... · 82d127b5
      unknown authored
      Dec. 31st, 9999 is still a valid date, only starting with Jan 1st 10000 things become invalid (Bug #12356)
      
      
      mysql-test/r/func_sapdb.result:
        test cases for date range edge cases added
      mysql-test/r/func_time.result:
        test cases for date range edge cases added
      mysql-test/t/func_sapdb.test:
        test cases for date range edge cases added
      mysql-test/t/func_time.test:
        test cases for date range edge cases added
      82d127b5
    • unknown's avatar
      Bug #16458: Simple SELECT FOR UPDATE causes "Result Set not updatable" error · 4b36c1d8
      unknown authored
      'SELECT DISTINCT a,b FROM t1' should not use temp table if there is unique 
      index (or primary key) on a.
      There are a number of other similar cases that can be calculated without the
      use of a temp table : multi-part unique indexes, primary keys or using GROUP BY 
      instead of DISTINCT.
      When a GROUP BY/DISTINCT clause contains all key parts of a unique
      index, then it is guaranteed that the fields of the clause will be
      unique, therefore we can optimize away GROUP BY/DISTINCT altogether.
      This optimization has two effects:
      * there is no need to create a temporary table to compute the
         GROUP/DISTINCT operation (or the temporary table will be smaller if only GROUP 
         is removed and DISTINCT stays or if DISTINCT is removed and GROUP BY stays)
      * this causes the statement in effect to become updatable in Connector/Java
      because the result set columns will be direct reference to the primary key of 
      the table (instead to the temporary table that it currently references). 
      
      Implemented a check that will optimize away GROUP BY/DISTINCT for queries like 
      the above.
      Currently it will work only for single non-constant table in the FROM clause.
      
      
      mysql-test/r/distinct.result:
        Bug #16458: Simple SELECT FOR UPDATE causes "Result Set not updatable" error
          - test case
      mysql-test/t/distinct.test:
        Bug #16458: Simple SELECT FOR UPDATE causes "Result Set not updatable" error
          - test case
      sql/sql_select.cc:
        Bug #16458: Simple SELECT FOR UPDATE causes "Result Set not updatable" error
          - disable GROUP BY if contains the fields of a unique index.
      4b36c1d8
    • unknown's avatar
      Merge abotchkov@bk-internal.mysql.com:/home/bk/mysql-4.1 · 79952ec0
      unknown authored
      into mysql.com:/home/hf/work/mysql-4.1.clean
      
      
      79952ec0
  7. 26 Jun, 2006 4 commits
  8. 23 Jun, 2006 1 commit
    • unknown's avatar
      Bug#11228: DESC shows arbitrary column as "PRI" · 89e41595
      unknown authored
        An UNIQUE KEY consisting of NOT NULL columns
        was displayed as PRIMARY KEY in "DESC t1".
        According to the code, that was intentional
        behaviour for some reasons unknown to me.
        This code was written before bitkeeper time,
        so I cannot check who and why made this.
        After discussing on dev-public, a decision
        was made to remove this code
      
      
      mysql-test/r/key.result:
        Adding test case.
      mysql-test/t/key.test:
        Adding test case.
      sql/table.cc:
        Removing old wrong code
      89e41595