An error occurred fetching the project authors.
  1. 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
  2. 13 May, 2006 1 commit
  3. 31 Oct, 2005 1 commit
  4. 27 Sep, 2005 1 commit
    • pem@mysql.com's avatar
      Fixed BUG#12589: Assert when creating temp. table from decimal stored · 2f3682db
      pem@mysql.com authored
                       procedure variable
        Second version, after review.
        Keep the unsigned_flag in Item_decimal updated. Note that this also changed
        the result of several old test results - creating tables from decimal
        templates now gives unsigned columns and different sizes. (Several tests
        had Length > Max_length before.)
      2f3682db
  5. 09 Sep, 2005 2 commits
  6. 23 Aug, 2005 1 commit
    • timour@mysql.com's avatar
      WL#2486 - natural and using join according to SQL:2003 · e0403003
      timour@mysql.com authored
      * Provide backwards compatibility extension to name resolution of
        coalesced columns. The patch allows such columns to be qualified
        with a table (and db) name, as it is in 4.1.
        Based on a patch from Monty.
      
      * Adjusted tests accordingly to test both backwards compatible name
        resolution of qualified columns, and ANSI-style resolution of
        non-qualified columns.
        For this, each affected test has two versions - one with qualified
        columns, and one without. 
      e0403003
  7. 12 Aug, 2005 1 commit
    • timour@mysql.com's avatar
      Implementation of WL#2486 - · a247282a
      timour@mysql.com authored
      "Process NATURAL and USING joins according to SQL:2003".
      
      * Some of the main problems fixed by the patch:
        - in "select *" queries the * expanded correctly according to
          ANSI for arbitrary natural/using joins
        - natural/using joins are correctly transformed into JOIN ... ON
          for any number/nesting of the joins.
        - column references are correctly resolved against natural joins
          of any nesting and combined with arbitrary other joins.
      
      * This patch also contains a fix for name resolution of items
        inside the ON condition of JOIN ... ON - in this case items must
        be resolved only against the JOIN operands. To support such
        'local' name resolution, the patch introduces a stack of
        name resolution contexts used at parse time.
      
      NOTICE:
      - This patch is not complete in the sense that
        - there are 2 test cases that still do not pass -
          one in join.test, one in select.test. Both are marked
          with a comment "TODO: WL#2486".
        - it does not include a new test specific for the task
      a247282a
  8. 19 Jul, 2005 1 commit
  9. 18 Jul, 2005 1 commit
  10. 14 Jul, 2005 1 commit
    • konstantin@mysql.com's avatar
      A fix and a test case for Bug#9735. · 62b8e6fd
      konstantin@mysql.com authored
      No separate typecode for MEDIUMTEXT/LONGTEXT is added, as we
      have no sound decision yet what typecodes and for what types are
      sent by the server (aka what constitutes a distinct type in MySQL).
      62b8e6fd
  11. 12 Jul, 2005 1 commit
  12. 20 Jun, 2005 1 commit
  13. 14 Jun, 2005 1 commit
  14. 07 Jun, 2005 2 commits
  15. 05 May, 2005 1 commit
  16. 30 Mar, 2005 1 commit
    • msvensson@neptunus.(none)'s avatar
      BUG#8807 Select crash server · 382a8c00
      msvensson@neptunus.(none) authored
       - Add function Item_param::fix_fields which will update any subselect they are part of and indicate that the subsleect is not const during prepare phase, and thus should not be executed during prepare.
      382a8c00
  17. 23 Mar, 2005 1 commit
    • serg@serg.mylan's avatar
      client/mysqltest.c · f21f8f98
      serg@serg.mylan authored
          corrected number of fields for --enable_metadata
      sql/sql_union.cc
          fixed a apparent typo in assert
      f21f8f98
  18. 16 Mar, 2005 1 commit
    • heikki@hundin.mysql.fi's avatar
      data0type.h, row0sel.c: · cb88409e
      heikki@hundin.mysql.fi authored
        Fix a crash in a simple search with a key: the dtype->len of a true VARCHAR is the payload maximum len in bytes: it does not include the 2 bytes MySQL uses to store the string length
      ha_innodb.cc:
        Fix a crash in true VARCHARs in test-innodb: we passed a wrong pointer to the column conversion in an UPDATE
      rowid_order_innodb.result, ps_3innodb.result, innodb.result, endspace.result:
        Edit InnoDB test results to reflect the arrival of true VARCHARs
      cb88409e
  19. 10 Feb, 2005 1 commit
  20. 08 Feb, 2005 1 commit
  21. 18 Jan, 2005 2 commits
    • bar@mysql.com's avatar
      After-merge clean-up · 05204a9b
      bar@mysql.com authored
      05204a9b
    • bar@mysql.com's avatar
      1. Item now uses my_charset_bin by default, · 8cfe7296
      bar@mysql.com authored
      not default_charset_into. It fixes the
      problem that in some cases numbers where
      treated as CHAR(N), not as BINARY(N), e.g.
      wrong 'charsetnr' when sent to the client side.
      2. IFNULL didn't aggregate argument charsets
      and collations, so IFNULL(1,'a') produced
      a CHAR(N). Now produces a BINARY(N).
      3. SELECT PROCEDURE ANALIZE now returns
      BINARY columns, which is much better than it worked
      previously: CHAR with the default character set.
      But in the future it's worth to fix the fields
      'Field_name' and 'Optimal_fieldtype' to use UTF8,
      and 'Min_value' and 'Max_value' to inherit their charsets
      from the original items. But it is not important,
      and BINARY(N) is OK for now.
      4. Tests were fixed accordingly. No new tests were
      made, as the old onces cover everything.
      8cfe7296
  22. 30 Dec, 2004 2 commits
  23. 17 Dec, 2004 1 commit
  24. 13 Dec, 2004 1 commit
    • mleich@mysql.com's avatar
      Small bug fix · 3b5a741a
      mleich@mysql.com authored
      ps-modify1 used the user variables @1, @2, @100 set within ps_query and 
                 ps_modify. That architecture was wrong, because the dependence
                 of ps_modify1 on ps_query and ps_modify makes the test script
                 maintenance and the use of these test cases during bug fixing/
                 debugging of single sub test cases very uncomfortable.
      Therefore these user variables (@1, @2, @100) are also set within ps-modify1.
      
      The result files of the test cases ps_2myisam, ps_3innodb, ps_4heap, ps_6bdb,
      ps_7ndb will be affected by that change and show 3 additional lines, but
      nothing else will change.    
      3b5a741a
  25. 08 Dec, 2004 1 commit
  26. 07 Dec, 2004 1 commit
  27. 06 Dec, 2004 2 commits
  28. 10 Nov, 2004 1 commit
    • bar@mysql.com's avatar
      1. When mixing NULL to a character string, · c51d7acf
      bar@mysql.com authored
      the result takes its charset/collation
      attributes from the character string,
      e.g.  SELECT func(NULL, _latin2'string')
      now returns a latin2 result. This is
      done by introducing a new derivation
      (aka coercibility) level DERIVATION_IGNORABLE,
      which is used with Item_null.
      2. 'Pure' NULL is now BINARY(0), not CHAR(0).
      I.e. NULL is now more typeless.
      c51d7acf
  29. 05 Nov, 2004 1 commit
    • bar@mysql.com's avatar
      As it is wrong and confusing to associate any · 5543f312
      bar@mysql.com authored
      character set with NULL, @A should be latin2
      after this query sequence:
      
         SET @A=_latin2'string';
         SET @A=NULL;
      
      I.e. the second query should not change the charset
      to the current default value, but should keep the
      original value assigned during the first query.
      In order to do it, we don't copy charset
      from the argument if the argument is NULL
      and the variable has previously been initialized.
      5543f312
  30. 03 Nov, 2004 1 commit
    • monty@mysql.com's avatar
      Fixes after merge with 4.1 · 47bbf768
      monty@mysql.com authored
      FOUND is not a reserved keyword anymore
      Added Item_field::set_no_const_sub() to be able to mark fields that can't be substituted
      Added 'simple_select' method to be able to quickly determinate if a select_result is a normal SELECT
      Note that the 5.0 tree is not yet up to date: Sanja will have to fix multi-update-locks for this merge to be complete
      47bbf768
  31. 30 Oct, 2004 1 commit
  32. 11 Oct, 2004 1 commit
  33. 07 Oct, 2004 3 commits