An error occurred fetching the project authors.
  1. 20 Jan, 2006 1 commit
  2. 12 Jan, 2006 1 commit
  3. 11 Jan, 2006 2 commits
  4. 10 Jan, 2006 1 commit
  5. 28 Dec, 2005 3 commits
    • andrey@lmy004.'s avatar
      WL #1034 update · 3cd5a23f
      andrey@lmy004. authored
      - fix problem with too long identifier name
      3cd5a23f
    • andrey@lmy004.'s avatar
      WL#1034 update · 02983835
      andrey@lmy004. authored
      - fix crash of an event that alters itself
      - make "alter event xyz;" invalid because at least 1 clause is needed.
      02983835
    • andrey@lmy004.'s avatar
      WL #1034 update · b5d583ae
      andrey@lmy004. authored
      - enable/disable -> enabled/disabled
      - fixed error message
      b5d583ae
  6. 26 Dec, 2005 1 commit
  7. 22 Dec, 2005 3 commits
  8. 21 Dec, 2005 1 commit
  9. 15 Dec, 2005 1 commit
    • andrey@lmy004.'s avatar
      WL#1034 update · 533180d7
      andrey@lmy004. authored
      - fix EVENT_ACL problem that GRANT ALL on some_db.* to someone@somewhere did not get to mysql.db
      - fix crash when the following is executed :
        CREATE EVENT P() CREATE EVENT E ON SCHEDULER 1 SECOND DO ROLLBACK;
        (creation works as well as calling P() which creates the event).
      533180d7
  10. 08 Dec, 2005 1 commit
    • konstantin@mysql.com's avatar
      A fix and a test case for Bug#15441 "Running SP causes Server · bbf3a593
      konstantin@mysql.com authored
      to Crash": the bug was that due to non-standard name
      resolution precedence in stored procedures (See Bug#5967)
      a stored procedure variable took precedence over a table column
      when the arguments for VALUES() function were resolved.
      The implementation of VALUES() function was not designed to work
      with Item_splocal and crashed.
      VALUES() function is non-standard. It can refer to, and
      is meaningful for, table columns only. The patch disables SP 
      variables as possible arguments of VALUES() function.
      bbf3a593
  11. 07 Dec, 2005 3 commits
    • andrey@lmy004.'s avatar
      WL #1034 updates after review · 3d854641
      andrey@lmy004. authored
      (strip m_ as prefix from member variables' names)
      3d854641
    • andrey@lmy004.'s avatar
      WL#1034 ongoing updates after review · bee85987
      andrey@lmy004. authored
      bee85987
    • anozdrin@mysql.com's avatar
      Patch for WL#2894: Make stored routine variables work · 0ff8f60b
      anozdrin@mysql.com authored
      according to the standard.
      
      The idea is to use Field-classes to implement stored routines
      variables. Also, we should provide facade to Item-hierarchy
      by Item_field class (it is necessary, since SRVs take part
      in expressions).
      
      The patch fixes the following bugs:
        - BUG#8702: Stored Procedures: No Error/Warning shown for inappropriate data 
          type matching; 
       
        - BUG#8768: Functions: For any unsigned data type, -ve values can be passed 
          and returned; 
       
        - BUG#8769: Functions: For Int datatypes, out of range values can be passed 
          and returned; 
       
        - BUG#9078: STORED PROCDURE: Decimal digits are not displayed when we use 
          DECIMAL datatype; 
       
        - BUG#9572: Stored procedures: variable type declarations ignored; 
       
        - BUG#12903: upper function does not work inside a function; 
       
        - BUG#13705: parameters to stored procedures are not verified; 
       
        - BUG#13808: ENUM type stored procedure parameter accepts non-enumerated
          data; 
       
        - BUG#13909: Varchar Stored Procedure Parameter always BINARY string (ignores 
          CHARACTER SET); 
       
        - BUG#14161: Stored procedure cannot retrieve bigint unsigned;
      
        - BUG#14188: BINARY variables have no 0x00 padding;
      
        - BUG#15148: Stored procedure variables accept non-scalar values;
      0ff8f60b
  12. 05 Dec, 2005 1 commit
    • andrey@lmy004.'s avatar
      WL#1034 updated · 7120d43c
      andrey@lmy004. authored
      - split into several files
      - forbid parallel execution (before analyse is done how to make it possible)
        because the same sp_head instance cannot be executed in parallel
      - added GPL headers
      - changed EVENT_ACL to be per DB variable
      - fixed minor problems
      7120d43c
  13. 03 Dec, 2005 1 commit
  14. 02 Dec, 2005 3 commits
  15. 28 Nov, 2005 1 commit
  16. 25 Nov, 2005 1 commit
  17. 23 Nov, 2005 1 commit
  18. 22 Nov, 2005 2 commits
  19. 18 Nov, 2005 1 commit
  20. 17 Nov, 2005 1 commit
    • pem@mysql.com's avatar
      Background: · c518a240
      pem@mysql.com authored
      Since long, the compiled code of stored routines has been printed in the trace file
      when starting mysqld with the "--debug" flag. (At creation time only, and only in
      debug builds of course.) This has been helpful when debugging stored procedure
      execution, but it's a bit awkward to use. Also, the printing of some of the
      instructions is a bit terse, in particular for sp_instr_stmt where only the command
      code was printed.
      
      This improves the printout of several of the instructions, and adds the debugging-
      only commands "show procedure code <name>" and "show function code <name>".
      (In non-debug builds they are not available.)
      c518a240
  21. 16 Nov, 2005 1 commit
    • bell@sanja.is.com.ua's avatar
      Issuing error about presence of commit/rollback statements in stored functions... · a60a6b0f
      bell@sanja.is.com.ua authored
      Issuing error about presence of commit/rollback statements in stored functions and triggers added to SP parsing procedure (BUG#13627)
      
      The crash mentioned in original bug report is already prevented by one
      of previous patches (fix for bug #13343 "CREATE|etc TRIGGER|VIEW|USER
      don't commit the transaction (inconsistency)"), this patch only improve
      error returning.
      a60a6b0f
  22. 10 Nov, 2005 2 commits
  23. 09 Nov, 2005 1 commit
  24. 07 Nov, 2005 1 commit
  25. 06 Nov, 2005 2 commits
  26. 01 Nov, 2005 1 commit
  27. 28 Oct, 2005 1 commit
  28. 25 Oct, 2005 1 commit