1. 28 Feb, 2007 6 commits
  2. 26 Feb, 2007 1 commit
  3. 20 Feb, 2007 2 commits
  4. 19 Feb, 2007 5 commits
  5. 16 Feb, 2007 2 commits
    • unknown's avatar
      Merge 192.168.0.10:mysql/mysql-4.1-maint · c6e1de4c
      unknown authored
      into  pilot.blaudden:/home/msvensson/mysql/mysql-4.1-maint
      
      
      client/mysqltest.c:
        Auto merged
      c6e1de4c
    • unknown's avatar
      Workaround for problem where cygwin's bash/sh randomly fails with error 128 which · a843a05f
      unknown authored
      mainly occurs on win2003 64bit.
       - Execute "exec" commands directly with cmd.exe and replace "--exec echo ..." with "--exec .\echo.exe ..." 
      
      
      client/mysqltest.c:
        Workaround the problem with "echo" in windows not behaving like "echo" in Unix.
        - Replace "--exec echo ..." with "--exec <path to mysqltest>\echo.exe" thus forcing
          use of our own echo implementation which baheves like on Unix.
        - The above change makes it possible to remove the need to execute all --exec's
          inside cygwin. Add ifdefs to only use use cygwin's bash conditionally
      mysql-test/lib/mtr_misc.pl:
        Add function for converting to the OS's native format
      mysql-test/mysql-test-run.pl:
        Convert path to executables to "windows native" (c:\<path>\) instead of "mixed"(c:/<path>) mode
        necessary for pipes and redirects to work properly in cmd.exe
      client/echo.c:
        New BitKeeper file ``client/echo.c''
      a843a05f
  6. 15 Feb, 2007 2 commits
  7. 14 Feb, 2007 2 commits
  8. 13 Feb, 2007 4 commits
  9. 12 Feb, 2007 4 commits
    • unknown's avatar
      Merge bk@192.168.21.1:mysql-4.1-opt · 38fa86a1
      unknown authored
      into  mysql.com:/home/hf/work/25492/my41-25492
      
      
      38fa86a1
    • unknown's avatar
      bug #25492 (Invalid deallocation in mysql_stmt_fetch) · fd76e148
      unknown authored
      
      libmysqld/lib_sql.cc:
        code modified to prevent freeing of memory that wasn't malloc-ed.
        Now we check if MYSQL_STMT::result was used.
      fd76e148
    • unknown's avatar
      Merge tnurnberg@bk-internal.mysql.com:/home/bk/mysql-4.1-maint · 8a34c4bb
      unknown authored
      into  mysql.com:/home/tnurnberg/24660/41-24660
      
      
      sql/table.cc:
        Auto merged
      8a34c4bb
    • unknown's avatar
      Bug#24660: "enum" field type definition problem · 4dc7c1aa
      unknown authored
      ENUMs weren't allowed to have character 0xff, a perfectly good character in some locales.
      This was circumvented by mapping 0xff in ENUMs to ',', thereby prevent actual commas from
      being used. Now if 0xff makes an appearance, we find a character not used in the enum and
      use that as a separator. If no such character exists, we throw an error.
      
      Any solution would have broken some sort of existing behaviour. This solution should
      serve both fractions (those with 0xff and those with ',' in their enums), but
      WILL REQUIRE A DUMP/RESTORE CYCLE FROM THOSE WITH 0xff IN THEIR ENUMS. :-/
      That is, mysqldump with their current server, and restore when upgrading to one with
      this patch.
      
      
      mysql-test/r/type_enum.result:
        Bug#24660: "enum" field type definition problem
        
        Show that enums can now contain NAMES_SEP_CHAR (0xff, which is a perfectly respectable
        char in some locales), or ',', or both.
      mysql-test/t/type_enum.test:
        Bug#24660: "enum" field type definition problem
        
        Show that enums can now contain NAMES_SEP_CHAR (0xff, which is a perfectly respectable
        char in some locales), or ',', or both.
      sql/table.cc:
        Bug#24660: "enum" field type definition problem
        
        Revert fix for Bug#20922.
      sql/unireg.cc:
        Bug#24660: "enum" field type definition problem
        
        Use a field-separator for ENUM-values that is not part of those values. If impossible,
        throw error.
      4dc7c1aa
  10. 09 Feb, 2007 1 commit
    • unknown's avatar
      Bug#25126: Reference to non-existant column in UPDATE...ORDER BY... crashes server · 4c4f5062
      unknown authored
      "update existingtable set anycolumn=nonexisting order by nonexisting" would crash
      the server.
      
      Though we would find the reference to a field, that doesn't mean we can then use
      it to set some values.  It could be a reference to another field.  If it is NULL, 
      don't try to use it to set values in the Item_field and instead return an error.
      
      Over the previous patch, this signals an error at the location of the error, rather
      than letting the subsequent deref signal it.
      
      
      mysql-test/r/order_by.result:
        Verify that all permutations work.
      mysql-test/t/order_by.test:
        Verify that all permutations work.
      sql/item.cc:
        When the field is NULL, don't dereference it when we set_field().  
        Instead, raise an error.
      4c4f5062
  11. 08 Feb, 2007 2 commits
  12. 07 Feb, 2007 2 commits
  13. 06 Feb, 2007 7 commits