An error occurred fetching the project authors.
  1. 06 Dec, 2004 1 commit
    • monty@mysql.com's avatar
      Add support for up to VARCHAR (size up to 65535) · 67ce2479
      monty@mysql.com authored
      Renamed HA_VAR_LENGTH to HA_VAR_LENGTH_PART
      Renamed in all files FIELD_TYPE_STRING and FIELD_TYPE_VAR_STRING to MYSQL_TYPE_STRING and MYSQL_TYPE_VAR_STRING to make it easy to catch all possible errors
      Added support for VARCHAR KEYS to heap
      Removed support for ISAM
      Now only long VARCHAR columns are changed to TEXT on demand (not CHAR)
      Internal temporary files can now use fixed length tables if the used VARCHAR columns are short
      67ce2479
  2. 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
  3. 07 Nov, 2004 1 commit
    • monty@mysql.com's avatar
      Simpler arena swapping code · b903a129
      monty@mysql.com authored
      Now thd->mem_root is a pointer to thd->main_mem_root and THR_MALLOC is a pointer to thd->mem_root.
      This gives us the following benefits:
      - Allow us to easily detect if arena has already been swapped before (this fixes a bug in setup_conds() where arena was swaped twice in some cases)
      - Faster swaps of arenas (as we don't have to copy the whole MEM_ROOT)
      - We don't anymore have to call my_pthread_setspecific_ptr(THR_MALLOC,...) to change where memory is alloced. Now it's enough to set thd->mem_root
      b903a129
  4. 03 Nov, 2004 2 commits
    • pem@mysql.comhem.se's avatar
      Various syntax fixes in sql/sql_yacc.yy for stored procedures: · 327eb9bb
      pem@mysql.comhem.se authored
        - No RESTICT|CASCADE in DROP SP (since it's not implemented)
        - Added optional "noise" to FETCH: [[NEXT] FROM]
        - At least one statement required in all block constructs except BEGIN-END
          (where zero is allowed)
      327eb9bb
    • 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
  5. 28 Oct, 2004 1 commit
  6. 26 Oct, 2004 2 commits
  7. 22 Oct, 2004 2 commits
  8. 21 Oct, 2004 2 commits
  9. 20 Oct, 2004 1 commit
  10. 14 Oct, 2004 2 commits
  11. 10 Oct, 2004 3 commits
  12. 08 Oct, 2004 1 commit
  13. 07 Oct, 2004 3 commits
  14. 06 Oct, 2004 1 commit
  15. 02 Oct, 2004 2 commits
  16. 01 Oct, 2004 1 commit
    • dlenev@brandersnatch.localdomain's avatar
      Support for TIMESTAMP columns holding NULL values. Unlike all other · 2511990c
      dlenev@brandersnatch.localdomain authored
      column types TIMESTAMP is NOT NULL by default, so in order to have 
      TIMESTAMP column holding NULL valaues you have to specify NULL as
      one of its attributes (this needed for backward compatibility).
      
      Main changes:
      Replaced TABLE::timestamp_default_now/on_update_now members with
      TABLE::timestamp_auto_set_type flag which is used everywhere
      for determining if we should auto-set value of TIMESTAMP field 
      during this operation or not. We are also use Field_timestamp::set_time()
      instead of handler::update_timestamp() in handlers.
      2511990c
  17. 17 Sep, 2004 1 commit
  18. 13 Sep, 2004 2 commits
  19. 10 Sep, 2004 2 commits
  20. 08 Sep, 2004 2 commits
  21. 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
  22. 04 Sep, 2004 1 commit
  23. 03 Sep, 2004 2 commits
  24. 31 Aug, 2004 2 commits
  25. 30 Aug, 2004 1 commit