An error occurred fetching the project authors.
  1. 28 Apr, 2007 1 commit
    • gshchepa/uchum@gshchepa.loc's avatar
      Fixed bug #13191. · 3adcb94e
      gshchepa/uchum@gshchepa.loc authored
      INSERT...ON DUPLICATE KEY UPDATE may cause error 1032: 
      "Can't find record in ..." if we are inserting into
      InnoDB table unique index of partial key with
      underlying UTF-8 string field.
      
      This error occurs because INSERT...ON DUPLICATE uses a wrong
      procedure to copy string fields of multi-byte character sets
      for index search.
      3adcb94e
  2. 14 Apr, 2007 1 commit
  3. 12 Apr, 2007 1 commit
  4. 11 Apr, 2007 4 commits
  5. 10 Apr, 2007 1 commit
  6. 07 Apr, 2007 2 commits
  7. 05 Apr, 2007 1 commit
  8. 04 Apr, 2007 1 commit
  9. 03 Apr, 2007 1 commit
    • igor@olga.mysql.com's avatar
      Fixed bug #27532: wrong results with ORDER/GROUP BY queries containing · 90aa05d2
      igor@olga.mysql.com authored
      IN/BETWEEN predicates in sorting expressions.
      Wrong results may occur when the select list contains an expression
      with IN/BETWEEN predicate that differs from a sorting expression by
      an additional NOT only.
       
      Added the method Item_func_opt_neg::eq to compare correctly expressions
      containing [NOT] IN/BETWEEN.
      The eq method inherited from the Item_func returns TRUE when comparing
      'a IN (1,2)' with 'a NOT IN (1,2)' that is not, of course, correct.  
      90aa05d2
  10. 02 Apr, 2007 2 commits
  11. 31 Mar, 2007 1 commit
  12. 30 Mar, 2007 2 commits
  13. 29 Mar, 2007 4 commits
  14. 28 Mar, 2007 10 commits
  15. 27 Mar, 2007 2 commits
    • kent@mysql.com/kent-amd64.(none)'s avatar
      mysql.spec.sh, Makefile.am: · ef530348
      kent@mysql.com/kent-amd64.(none) authored
        Don't use explicit calls to mysql-test-run in spec
      ef530348
    • istruewing@chilla.local's avatar
      Bug#24985 - UTF8 ENUM primary key on MEMORY using BTREE · 8934e4f3
      istruewing@chilla.local authored
                  causes incorrect duplicate entries
      
      Keys for BTREE indexes on ENUM and SET columns of MEMORY tables
      with character set UTF8 were computed incorrectly. Many
      different column values got the same key value.
      
      Apart of possible performance problems, it made unique indexes
      of this type unusable because it rejected many different
      values as duplicates.
      
      The problem was that multibyte character detection was tried
      on the internal numeric column value. Many values were not
      identified as characters. Their key value became blank filled.
      
      Thanks to Alexander Barkov and Ramil Kalimullin for the patch,
      which sets the character set of ENUM and SET key segments to
      the pseudo binary character set.
      8934e4f3
  16. 26 Mar, 2007 2 commits
  17. 25 Mar, 2007 2 commits
  18. 24 Mar, 2007 1 commit
  19. 23 Mar, 2007 1 commit