1. 25 Sep, 2006 1 commit
  2. 22 Sep, 2006 2 commits
  3. 19 Sep, 2006 3 commits
  4. 18 Sep, 2006 1 commit
  5. 06 Sep, 2006 4 commits
  6. 01 Sep, 2006 1 commit
  7. 15 Aug, 2006 1 commit
    • cmiller@maint1.mysql.com's avatar
      Bug #20908: Crash if select @@"" · 53bb6a47
      cmiller@maint1.mysql.com authored
      Zero-length variables caused failures when using the length to look
      up the name in a hash.  Instead, signal that no zero-length name can
      ever be found and that to encounter one is a syntax error.
      53bb6a47
  8. 01 Aug, 2006 3 commits
  9. 31 Jul, 2006 2 commits
  10. 29 Jul, 2006 6 commits
  11. 28 Jul, 2006 9 commits
  12. 27 Jul, 2006 5 commits
  13. 26 Jul, 2006 2 commits
    • tsmith/tim@siva.hindu.god's avatar
      Merge siva.hindu.god:/usr/home/tim/m/bk/global-41 · 80465ab6
      tsmith/tim@siva.hindu.god authored
      into  siva.hindu.god:/usr/home/tim/m/bk/global-50
      80465ab6
    • kroki/tomash@moonlight.intranet's avatar
      BUG#21206: memory corruption when too many cursors are opened at once · 4e845ccc
      kroki/tomash@moonlight.intranet authored
      Too many cursors (more than 1024) could lead to memory corruption.
      This affects both, stored routines and C API cursors, and the
      threshold is per-server, not per-connection.  Similarly, the
      corruption could happen when the server was under heavy load
      (executing more than 1024 simultaneous complex queries), and this is
      the reason why this bug is fixed in 4.1, which doesn't support
      cursors.
      
      The corruption was caused by a bug in the temporary tables code, when
      an attempt to create a table could lead to a write beyond allocated
      space.  Note, that only internal tables were affected (the tables
      created internally by the server to resolve the query), not tables
      created with CREATE TEMPORARY TABLE.  Another pre-condition for the
      bug is TRUE value of --temp-pool startup option, which, however, is a
      default.
      
      The cause of a bug was that random memory was overwritten in
      bitmap_set_next() due to out-of-bound memory access.
      4e845ccc