An error occurred fetching the project authors.
  1. 05 Jun, 2007 1 commit
    • svoj@mysql.com/april.(none)'s avatar
      BUG#26976 - Missing table in merge not noted in related error msg + · bd8f81f4
      svoj@mysql.com/april.(none) authored
                  SHOW CREATE TABLE fails
      
      Underlying table names, that merge engine fails to open were not
      reported.
      
      With this fix CHECK TABLE issued against merge table reports all
      underlying table names that it fails to open. Other statements
      are unaffected, that is underlying table names are not included
      into error message.
      
      This fix doesn't solve SHOW CREATE TABLE issue.
      bd8f81f4
  2. 22 Feb, 2007 2 commits
  3. 15 Feb, 2007 1 commit
  4. 14 Feb, 2007 2 commits
  5. 13 Nov, 2006 1 commit
  6. 06 Oct, 2006 1 commit
  7. 28 Sep, 2006 1 commit
    • evgen@moonbone.local's avatar
      Fixed bug#5505: Wrong error message on INSERT into a view · f6fbbf20
      evgen@moonbone.local authored
      On an INSERT into an updatable but non-insertable view an error message was
      issued stating the view being not updatable. This can lead to a confusion of a
      user.
      
      A new error message is introduced. Is is showed when a user tries to insert
      into a non-insertable view.
      f6fbbf20
  8. 27 Sep, 2006 1 commit
  9. 30 Aug, 2006 1 commit
  10. 24 Aug, 2006 1 commit
  11. 23 Aug, 2006 1 commit
  12. 02 Aug, 2006 1 commit
    • svoj@may.pils.ru's avatar
      BUG#14770 - LOAD DATA INFILE doesn't respect default values for · 6c6f435b
      svoj@may.pils.ru authored
                  columns
      Fixed confusing warning.
      
      Quoting INSERT section of the manual:
      ----
      Inserting NULL into a column that has been declared NOT NULL. For
      multiple-row INSERT statements or INSERT INTO ... SELECT statements, the
      column is set to the implicit default value for the column data type. This
      is 0 for numeric types, the empty string ('') for string types, and the
      "zero" value for date and time types. INSERT INTO ... SELECT statements are
      handled the same way as multiple-row inserts because the server does not
      examine the result set from the SELECT to see whether it returns a single
      row. (For a single-row INSERT, no warning occurs when NULL is inserted into
      a NOT NULL column. Instead, the statement fails with an error.)
      ----
      This is also true for LOAD DATA INFILE. For INSERT user can specify
      DEFAULT keyword as a value to set column default. There is no similiar
      feature available for LOAD DATA INFILE.
      6c6f435b
  13. 15 Jul, 2006 1 commit
    • evgen@moonbone.local's avatar
      errmsg.txt: · 5431805c
      evgen@moonbone.local authored
        Fixed bug#10977: No warning issued if a column name is truncated
        New warning message is added.
      5431805c
  14. 28 Jun, 2006 1 commit
  15. 20 Jun, 2006 1 commit
  16. 12 May, 2006 1 commit
  17. 26 Apr, 2006 1 commit
  18. 20 Apr, 2006 1 commit
    • evgen@moonbone.local's avatar
      Fixed bug#18739: non-standard HAVING extension was allowed in strict ANSI sql mode. · 663fee9c
      evgen@moonbone.local authored
      The SQL standard doesn't allow to use in HAVING clause fields that are not 
      present in GROUP BY clause and not under any aggregate function in the HAVING
      clause. However, mysql allows using such fields. This extension assume that 
      the non-grouping fields will have the same group-wise values. Otherwise, the 
      result will be unpredictable. This extension allowed in strict 
      MODE_ONLY_FULL_GROUP_BY sql mode results in misunderstanding of HAVING 
      capabilities.
      
      The new error message ER_NON_GROUPING_FIELD_USED message is added. It says
      "non-grouping field '%-.64s' is used in %-.64s clause". This message is
      supposed to be used for reporting errors when some field is not found in the
      GROUP BY clause but have to be present there. Use cases for this message are 
      this bug and when a field is present in a SELECT item list not under any 
      aggregate function and there is GROUP BY clause present which doesn't mention 
      that field. It renders the ER_WRONG_FIELD_WITH_GROUP error message obsolete as
      being more descriptive.
      The resolve_ref_in_select_and_group() function now reports the 
      ER_NON_GROUPING_FIELD_FOUND error if the strict mode is set and the field for 
      HAVING clause is found in the SELECT item list only.
      663fee9c
  19. 13 Apr, 2006 1 commit
  20. 12 Apr, 2006 2 commits
  21. 10 Mar, 2006 1 commit
  22. 17 Feb, 2006 1 commit
  23. 09 Feb, 2006 1 commit
    • pem@mysql.com's avatar
      Fixed BUG#16896: Stored function: unused AGGREGATE-clause in CREATE FUNCTION · 6f170782
      pem@mysql.com authored
        Check if AGGREGATE was given with a stored (non-UDF) function, and return
        error in that case.
        Also made udf_example/udf_test work again, by adding a missing *_init()
        function. (_init() functions required unless --allow_suspicious_udfs is
        given to the server, since March 2005 - it seems udf_example wasn't updated
        at the time.)
      6f170782
  24. 17 Jan, 2006 1 commit
  25. 11 Jan, 2006 1 commit
  26. 20 Dec, 2005 1 commit
  27. 02 Dec, 2005 1 commit
  28. 25 Nov, 2005 1 commit
  29. 24 Nov, 2005 1 commit
  30. 22 Nov, 2005 2 commits
  31. 20 Nov, 2005 1 commit
    • bell@sanja.is.com.ua's avatar
      Inefficient usage of String::append() fixed. · 806f9e24
      bell@sanja.is.com.ua authored
      Bad examples of usage of a string with its length fixed.
      The incorrect length in the trigger file configuration descriptor
        fixed (BUG#14090).
      A hook for unknown keys added to the parser to support old .TRG files.
      806f9e24
  32. 17 Nov, 2005 1 commit
  33. 10 Nov, 2005 2 commits
  34. 06 Nov, 2005 1 commit
  35. 03 Nov, 2005 1 commit