1. 24 May, 2005 8 commits
  2. 23 May, 2005 10 commits
  3. 21 May, 2005 1 commit
    • unknown's avatar
      BUG# 9148: Denial of service · 442c072f
      unknown authored
      This is a second patch needing another review.  The first patch didn't solve
      the entire problem.  open and fopen on Windows will still open
      files like "com1.sym" when they shouldn't.  This patch
      checks that the file exists before trying to open it.
      
      
      
      mysys/my_fopen.c:
        on Windows, if we are not creating a file the we call my_access to make sure the
        file exists before trying to open it.
      mysys/my_open.c:
        on Windows, if we are not creating a file the we call my_access to make sure the
        file exists before trying to open it.
      442c072f
  4. 20 May, 2005 5 commits
    • unknown's avatar
      9b8e0274
    • unknown's avatar
      BUG# 9148: Denial of service · c1ae672a
      unknown authored
      The problem was that on Windows the access method indicates that access to file 
      such as "com1" and "lpt1" is allowed (since they are device names) and
      this causes mysql to attempt to open them as databases or tables.
      
      The fix was to write our own my_access method that uses other Win32 functions
      to determine if the given argument is indeed a file and has to requested
      mode.
      
      
      VC++Files/mysys/mysys.dsp:
        added my_access
      VC++Files/mysys/mysys_ia64.dsp:
        added my_access.c
      include/my_sys.h:
        if on windows, we use my_access.
        if not on windows, then my_access points to the native access method
      mysys/Makefile.am:
        added my_access to mysys build file
      mysys/mf_pack.c:
        changed call to access to my_access
      sql/sql_db.cc:
        changed call to access to my_access
      c1ae672a
    • unknown's avatar
      Merge mysql.com:/usr/home/ram/work/mysql-4.1-build · 25d661ad
      unknown authored
      into mysql.com:/usr/home/ram/work/mysql-4.1
      
      
      25d661ad
    • unknown's avatar
      a fix (bug #10757: gis-rtree.test fails) · 2ef41d3d
      unknown authored
      
      
      myisam/sp_key.c:
        a fix (bug #10757: gis-rtree.test fails)
        float8get() doesn't properly work with local variables sometimes.
      2ef41d3d
    • unknown's avatar
  5. 19 May, 2005 8 commits
  6. 18 May, 2005 8 commits
    • unknown's avatar
      merged · 7e507270
      unknown authored
      
      sql/unireg.cc:
        Auto merged
      7e507270
    • unknown's avatar
      Merge book.sanja.is.com.ua:/Users/bell/mysql/bk/mysql-4.1 · 9e8cad1d
      unknown authored
      into book.sanja.is.com.ua:/Users/bell/mysql/bk/work-4.1
      
      
      9e8cad1d
    • unknown's avatar
      Merge bk-internal:/home/bk/mysql-4.0/ · dae940d1
      unknown authored
      into serg.mylan:/usr/home/serg/Abk/mysql-4.0
      
      
      dae940d1
    • unknown's avatar
      udf: when banning paths from soname in CREATE FUNCTION, check for \ on windows. · e507f6a1
      unknown authored
      when reporting an error, use an appropriate buffer for udf->name
      
      
      e507f6a1
    • unknown's avatar
      Merge mysql.com:/home/mydev/mysql-4.1 · 7a223fe8
      unknown authored
      into mysql.com:/home/mydev/mysql-4.1-4100
      
      
      7a223fe8
    • unknown's avatar
      Bug#10400 - Improperly-defined MERGE table crashes with INSERT ... ON DUPLICATE KEY UPDATE · 0461b482
      unknown authored
      After review version.
      Added a condition for MERGE tables. These do not have unique
      indexes. But every key could be a unique key on the underlying
      MyISAM table. So get the maximum key length for MERGE tables
      instead of the maximum unique key length. This is used for
      buffer allocation in write_record().
      
      
      mysql-test/r/merge.result:
        Bug#10400 - Improperly-defined MERGE table crashes with INSERT ... ON DUPLICATE KEY UPDATE
        The test result.
      mysql-test/t/merge.test:
        Bug#10400 - Improperly-defined MERGE table crashes with INSERT ... ON DUPLICATE KEY UPDATE
        The test case does not in all cases show the problem
        without the bugfix. The improper memory allocation
        might get through undetected in many cases.
      sql/ha_myisammrg.h:
        Bug#10400 - Improperly-defined MERGE table crashes with INSERT ... ON DUPLICATE KEY UPDATE
        Set a table_flag for the MERGE engine telling that any index
        might be unique without being specified as such.
      sql/handler.h:
        Bug#10400 - Improperly-defined MERGE table crashes with INSERT ... ON DUPLICATE KEY UPDATE
        Added a new table_flag telling that any index
        might be unique without being specified as such.
      sql/sql_insert.cc:
        Bug#10400 - Improperly-defined MERGE table crashes with INSERT ... ON DUPLICATE KEY UPDATE
        Changed the freeing of the memory to be symmetric to its
        allocation (my_safe_alloc -> my_safe_afree).
        This is not directly related to the bug.
      sql/table.cc:
        Bug#10400 - Improperly-defined MERGE table crashes with INSERT ... ON DUPLICATE KEY UPDATE
        Added a condition for MERGE tables. These do not have unique
        indexes. But every key could be a unique key on the underlying
        MyISAM table. So get the maximum key length for MERGE tables
        instead of the maximum unique key length. This is used for
        buffer allocation in write_record().
      0461b482
    • unknown's avatar
      Merge bk-internal:/home/bk/mysql-4.1 · d104149c
      unknown authored
      into mysql.com:/home/jimw/my/mysql-4.1-clean
      
      
      d104149c
    • unknown's avatar
      Merge sinisa@bk-internal.mysql.com:/home/bk/mysql-4.1 · a2174048
      unknown authored
      into sinisa.nasamreza.org:/mnt/work/mysql-4.1
      
      
      a2174048