An error occurred fetching the project authors.
  1. 27 May, 2005 2 commits
  2. 04 Mar, 2005 2 commits
    • acurtis@pcgem.rdg.cyberkinetica.com's avatar
      Bug#3788 · 5e1d2ad6
      acurtis@pcgem.rdg.cyberkinetica.com authored
        Crashes with stored procedure return non-string values
        Also fixes Bug#2773
      5e1d2ad6
    • dlenev@brandersnatch.localdomain's avatar
      Better approach for prelocking of tables for stored routines execution · 5a6c7027
      dlenev@brandersnatch.localdomain authored
      and some SP-related cleanups.
      
      - We don't have separate stage for calculation of list of tables
        to be prelocked and doing implicit LOCK/UNLOCK any more.
        Instead we calculate this list at open_tables() and do implicit
        LOCK in lock_tables() (and UNLOCK in close_thread_tables()).
        Also now we support cases when same table (with same alias) is
        used several times in the same query in SP.
      
      - Cleaned up execution of SP. Moved all common code which handles
        LEX and does preparations before statement execution or complex
        expression evaluation to auxilary sp_lex_keeper class. Now 
        all statements in SP (and corresponding instructions) that
        evaluate expression which can contain subquery have their
        own LEX.
      5a6c7027
  3. 08 Feb, 2005 1 commit
    • pem@mysql.comhem.se's avatar
      WL#2130: Table locking for stored FUNCTIONs · 2c26ebe3
      pem@mysql.comhem.se authored
      Collect all tables and SPs refered by a statement, and open all tables
      with an implicit LOCK TABLES. Do find things refered by triggers and views,
      we open them first (and then repeat this until nothing new is found), before
      doing the actual lock tables.
      2c26ebe3
  4. 24 Nov, 2004 1 commit
    • dlenev@brandersnatch.localdomain's avatar
      Fix for bug #5888 "Triggers with nonexistent columns cause packets · d2010746
      dlenev@brandersnatch.localdomain authored
      out of order". (final version)
      
      Now instead of binding Item_trigger_field to TABLE objects during
      trigger definition parsing at table open, we perform pass through
      special list of all such objects in trigger. This allows easily check
      all references to fields in old/new version of row in trigger during
      execution of CREATE TRIGGER statement (this is more courtesy for users
      since we can't check everything anyway).
      We also report that such reference is bad by returning error from
      Item_trigger_field::fix_fields() method (instead of setup_field())
      This means that if trigger is broken we will bark during trigger
      execution instead of trigger definition parsing at table open.
      (i.e. now we allow to open tables with broken triggers).
      d2010746
  5. 09 Nov, 2004 1 commit
    • monty@mysql.com's avatar
      After merge fixes · 2bba55b5
      monty@mysql.com authored
      Added push_back(void *, MEM_ROOT *) to make some list-handling code easier that needs to be allocated in a different mem-root
      (Before one had to change thd->mem_root ; push_back(); restore mem_root.
      2bba55b5
  6. 17 Sep, 2004 1 commit
  7. 10 Sep, 2004 1 commit
  8. 08 Sep, 2004 1 commit
  9. 07 Sep, 2004 1 commit
    • dlenev@brandersnatch.localdomain's avatar
      WL#1218 "Triggers". Some very preliminary version of patch. · 9ed038dd
      dlenev@brandersnatch.localdomain authored
      Mostly needed for Monty for him getting notion what needed for triggers 
      from new .FRM format. 
      
      Things to be done:
      - Right placement of trigger's invocations
      - Right handling of errors in triggers (including transaction rollback)
      - Support for priviliges
      - Right handling of DROP/RENAME table (hope that it will be handled automatically
        with merging of .TRG into .FRM file)
      - Saving/restoring some information critical for trigger creation and replication
        with their definitions (e.g. sql_mode, creator, ...)
      - Replication
      
      Already has some known bugs so probably not for general review.
      9ed038dd
  10. 26 Aug, 2004 1 commit
  11. 24 Aug, 2004 1 commit
  12. 17 Aug, 2004 1 commit
  13. 06 Aug, 2004 1 commit
  14. 02 Aug, 2004 1 commit
  15. 09 Jun, 2004 1 commit
  16. 26 May, 2004 1 commit
  17. 19 May, 2004 1 commit
  18. 06 Apr, 2004 1 commit
  19. 05 Apr, 2004 1 commit
  20. 29 Mar, 2004 1 commit
  21. 11 Mar, 2004 1 commit
  22. 17 Feb, 2004 1 commit
  23. 16 Dec, 2003 1 commit
  24. 15 Dec, 2003 1 commit
  25. 13 Dec, 2003 1 commit
  26. 12 Dec, 2003 1 commit
    • pem@mysql.comhem.se's avatar
      In order to make ALTER PROCEDURE|FUNCTION work correctly, and in general to · 7a20e528
      pem@mysql.comhem.se authored
      make characteristics (and SHOW) work right, we had to separate the old
      definition blob in the mysql.proc table into separate fields for parameters,
      return type, and body, and handle the characteristics (like SQL SECURITY)
      separately... and then reassemble the CREATE string for parsing, of course.
      This is rather ugly, mostly the parser bit. (Hopefully that will be better
      with the new parser.)
      7a20e528
  27. 10 Dec, 2003 1 commit
  28. 17 Nov, 2003 1 commit
  29. 10 Oct, 2003 1 commit
  30. 03 Oct, 2003 1 commit
  31. 16 Sep, 2003 1 commit
  32. 27 Aug, 2003 1 commit
  33. 07 Jul, 2003 1 commit
  34. 03 Jul, 2003 1 commit
  35. 01 Jul, 2003 1 commit
  36. 29 Jun, 2003 1 commit
  37. 23 May, 2003 1 commit
  38. 06 May, 2003 1 commit