An error occurred fetching the project authors.
  1. 04 Apr, 2005 2 commits
    • unknown's avatar
      ha_innodb.cc: · a64487fc
      unknown authored
        Correct the fix of Bug #9526 : InnoDB must use its own internal type info for old tables, so that old ENUMs and SETs still are (incorrectly) seen as char strings; we do not dare to allow InnoDB sometimes to see the type as an integer type for those old tables
      
      
      sql/ha_innodb.cc:
        Correct the fix of Bug #9526 : InnoDB must use its own internal type info for old tables, so that old ENUMs and SETs still are (incorrectly) seen as char strings; we do not dare to allow InnoDB sometimes to see the type as an integer type for those old tables
      a64487fc
    • unknown's avatar
      ha_innodb.cc: · 9ce74a80
      unknown authored
        Fix bug #9526 in InnoDB: the internal type of an ENUM or SET is an unsigned integer type, not a character string
      
      
      sql/ha_innodb.cc:
        Fix bug #9526 in InnoDB: the internal type of an ENUM or SET is an unsigned integer type, not a character string
      9ce74a80
  2. 04 Mar, 2005 1 commit
    • unknown's avatar
      ha_innodb.cc: · 8ef8cd76
      unknown authored
        write_row(): Detect SQLCOM_OPTIMIZE, so that also OPTIMIZE TABLE
        will commit at every 10,000 copied rows.
      
      
      sql/ha_innodb.cc:
        write_row(): Detect SQLCOM_OPTIMIZE, so that also OPTIMIZE TABLE
        will commit at every 10,000 copied rows.
      8ef8cd76
  3. 01 Mar, 2005 1 commit
    • unknown's avatar
      InnoDB: Commit inserts to the temporary tables created by · 22e0b300
      unknown authored
      CREATE INDEX and DROP INDEX every 10,000 rows,
      similar to ALTER TABLE.
      
      
      sql/ha_innodb.cc:
        Commit inserts to the temporary tables created by
        CREATE INDEX and DROP INDEX every 10,000 rows, similar
        to ALTER TABLE.
      sql/ha_innodb.h:
        Remove duplicate declaration of srv_max_purge_lag.
      22e0b300
  4. 15 Feb, 2005 1 commit
  5. 08 Feb, 2005 1 commit
    • unknown's avatar
      Relaxed locking in INSERT...SELECT, single table UPDATE...SELECT and · 6cee60ea
      unknown authored
      single table DELETE...SELECT clauses when innobase_locks_unsafe_for_binlog
      is used and isolation level of the transaction is not serializable. 
      InnoDB uses consistent read in these cases for a selected table.
      Backported from 5.0.x.
      
      
      sql/ha_innodb.cc:
        Relaxed locking in INSERT...SELECT, single table UPDATE...SELECT and 
        single table DELETE...SELECT clauses when innobase_locks_unsafe_for_binlog
        is used and isolation level of the transaction is not serializable. 
        InnoDB uses consistent read in these cases for a selected table.
      6cee60ea
  6. 27 Jan, 2005 1 commit
  7. 13 Jan, 2005 2 commits
    • unknown's avatar
      ha_innodb.cc: · 97f5b326
      unknown authored
        Merge from 4.0:     Fix a theoretical hang over the adaptive hash latch in InnoDB if one runs INSERT ... SELECT ... (binlog not enabled), or a multi-table UPDATE or DELETE, and only the read tables are InnoDB type, the rest are MyISAM; this also fixes bug #7879 for InnoDB type tables
      
      
      sql/ha_innodb.cc:
        Merge from 4.0:     Fix a theoretical hang over the adaptive hash latch in InnoDB if one runs INSERT ... SELECT ... (binlog not enabled), or a multi-table UPDATE or DELETE, and only the read tables are InnoDB type, the rest are MyISAM; this also fixes bug #7879 for InnoDB type tables
      97f5b326
    • unknown's avatar
      ha_innodb.cc: · d90e3b49
      unknown authored
        Fix a theoretical hang over the adaptive hash latch in InnoDB if one runs INSERT ... SELECT ... (binlog not enabled), or a multi-table UPDATE or DELETE, and only the read tables are InnoDB type, the rest are MyISAM; this also fixes bug #7879 for InnoDB type tables
      
      
      sql/ha_innodb.cc:
        Fix a theoretical hang over the adaptive hash latch in InnoDB if one runs INSERT ... SELECT ... (binlog not enabled), or a multi-table UPDATE or DELETE, and only the read tables are InnoDB type, the rest are MyISAM; this also fixes bug #7879 for InnoDB type tables
      d90e3b49
  8. 12 Jan, 2005 1 commit
  9. 27 Dec, 2004 3 commits
    • unknown's avatar
      ha_innodb.cc: · 562df4ee
      unknown authored
        Return a sensible error code from DISCARD TABLESPACE, if it fails because the table is referenced by a FOREIGN KEY
      
      
      sql/ha_innodb.cc:
        Return a sensible error code from DISCARD TABLESPACE, if it fails because the table is referenced by a FOREIGN KEY
      562df4ee
    • unknown's avatar
      ha_innodb.cc, row0ins.c, fil0fil.c: · 1b7282e3
      unknown authored
        Correct typo
      
      
      innobase/fil/fil0fil.c:
        Correct typo
      innobase/row/row0ins.c:
        Correct typo
      sql/ha_innodb.cc:
        Correct typo
      1b7282e3
    • unknown's avatar
      Many files: · 708eebea
      unknown authored
        Fix InnoDB critical bug #7496; we scan the InnoDB data dictionary also at a normal mysqld startup, and create the spaces, so that we know the mapping space id -> .ibd file name; fix an infinite loop if DISCARD TABLESPACE coincides with INSERT or some other table operation; fix a potential crash if DISCARD TABLESPACE coincides with a cascaded FOREIGN KEY operation in the same table; do not allow DISCARD TABLESPACE of a referenced table if FOREIGN_KEY_CHECKS=1
      
      
      innobase/buf/buf0rea.c:
        Fix InnoDB critical bug #7496; we scan the InnoDB data dictionary also at a normal mysqld startup, and create the spaces, so that we know the mapping space id -> .ibd file name; fix an infinite loop if DISCARD TABLESPACE coincides with INSERT or some other table operation; fix a potential crash if DISCARD TABLESPACE coincides with a cascaded FOREIGN KEY operation in the same table; do not allow DISCARD TABLESPACE of a referenced table if FOREIGN_KEY_CHECKS=1
      innobase/include/dict0load.h:
        Fix InnoDB critical bug #7496; we scan the InnoDB data dictionary also at a normal mysqld startup, and create the spaces, so that we know the mapping space id -> .ibd file name; fix an infinite loop if DISCARD TABLESPACE coincides with INSERT or some other table operation; fix a potential crash if DISCARD TABLESPACE coincides with a cascaded FOREIGN KEY operation in the same table; do not allow DISCARD TABLESPACE of a referenced table if FOREIGN_KEY_CHECKS=1
      innobase/include/fil0fil.h:
        Fix InnoDB critical bug #7496; we scan the InnoDB data dictionary also at a normal mysqld startup, and create the spaces, so that we know the mapping space id -> .ibd file name; fix an infinite loop if DISCARD TABLESPACE coincides with INSERT or some other table operation; fix a potential crash if DISCARD TABLESPACE coincides with a cascaded FOREIGN KEY operation in the same table; do not allow DISCARD TABLESPACE of a referenced table if FOREIGN_KEY_CHECKS=1
      innobase/include/row0mysql.h:
        Fix InnoDB critical bug #7496; we scan the InnoDB data dictionary also at a normal mysqld startup, and create the spaces, so that we know the mapping space id -> .ibd file name; fix an infinite loop if DISCARD TABLESPACE coincides with INSERT or some other table operation; fix a potential crash if DISCARD TABLESPACE coincides with a cascaded FOREIGN KEY operation in the same table; do not allow DISCARD TABLESPACE of a referenced table if FOREIGN_KEY_CHECKS=1
      innobase/include/trx0trx.h:
        Fix InnoDB critical bug #7496; we scan the InnoDB data dictionary also at a normal mysqld startup, and create the spaces, so that we know the mapping space id -> .ibd file name; fix an infinite loop if DISCARD TABLESPACE coincides with INSERT or some other table operation; fix a potential crash if DISCARD TABLESPACE coincides with a cascaded FOREIGN KEY operation in the same table; do not allow DISCARD TABLESPACE of a referenced table if FOREIGN_KEY_CHECKS=1
      innobase/dict/dict0load.c:
        Fix InnoDB critical bug #7496; we scan the InnoDB data dictionary also at a normal mysqld startup, and create the spaces, so that we know the mapping space id -> .ibd file name; fix an infinite loop if DISCARD TABLESPACE coincides with INSERT or some other table operation; fix a potential crash if DISCARD TABLESPACE coincides with a cascaded FOREIGN KEY operation in the same table; do not allow DISCARD TABLESPACE of a referenced table if FOREIGN_KEY_CHECKS=1
      innobase/fil/fil0fil.c:
        Fix InnoDB critical bug #7496; we scan the InnoDB data dictionary also at a normal mysqld startup, and create the spaces, so that we know the mapping space id -> .ibd file name; fix an infinite loop if DISCARD TABLESPACE coincides with INSERT or some other table operation; fix a potential crash if DISCARD TABLESPACE coincides with a cascaded FOREIGN KEY operation in the same table; do not allow DISCARD TABLESPACE of a referenced table if FOREIGN_KEY_CHECKS=1
      innobase/row/row0ins.c:
        Fix InnoDB critical bug #7496; we scan the InnoDB data dictionary also at a normal mysqld startup, and create the spaces, so that we know the mapping space id -> .ibd file name; fix an infinite loop if DISCARD TABLESPACE coincides with INSERT or some other table operation; fix a potential crash if DISCARD TABLESPACE coincides with a cascaded FOREIGN KEY operation in the same table; do not allow DISCARD TABLESPACE of a referenced table if FOREIGN_KEY_CHECKS=1
      innobase/row/row0mysql.c:
        Fix InnoDB critical bug #7496; we scan the InnoDB data dictionary also at a normal mysqld startup, and create the spaces, so that we know the mapping space id -> .ibd file name; fix an infinite loop if DISCARD TABLESPACE coincides with INSERT or some other table operation; fix a potential crash if DISCARD TABLESPACE coincides with a cascaded FOREIGN KEY operation in the same table; do not allow DISCARD TABLESPACE of a referenced table if FOREIGN_KEY_CHECKS=1
      innobase/row/row0sel.c:
        Fix InnoDB critical bug #7496; we scan the InnoDB data dictionary also at a normal mysqld startup, and create the spaces, so that we know the mapping space id -> .ibd file name; fix an infinite loop if DISCARD TABLESPACE coincides with INSERT or some other table operation; fix a potential crash if DISCARD TABLESPACE coincides with a cascaded FOREIGN KEY operation in the same table; do not allow DISCARD TABLESPACE of a referenced table if FOREIGN_KEY_CHECKS=1
      innobase/srv/srv0start.c:
        Fix InnoDB critical bug #7496; we scan the InnoDB data dictionary also at a normal mysqld startup, and create the spaces, so that we know the mapping space id -> .ibd file name; fix an infinite loop if DISCARD TABLESPACE coincides with INSERT or some other table operation; fix a potential crash if DISCARD TABLESPACE coincides with a cascaded FOREIGN KEY operation in the same table; do not allow DISCARD TABLESPACE of a referenced table if FOREIGN_KEY_CHECKS=1
      innobase/trx/trx0trx.c:
        Fix InnoDB critical bug #7496; we scan the InnoDB data dictionary also at a normal mysqld startup, and create the spaces, so that we know the mapping space id -> .ibd file name; fix an infinite loop if DISCARD TABLESPACE coincides with INSERT or some other table operation; fix a potential crash if DISCARD TABLESPACE coincides with a cascaded FOREIGN KEY operation in the same table; do not allow DISCARD TABLESPACE of a referenced table if FOREIGN_KEY_CHECKS=1
      sql/ha_innodb.cc:
        Fix InnoDB critical bug #7496; we scan the InnoDB data dictionary also at a normal mysqld startup, and create the spaces, so that we know the mapping space id -> .ibd file name; fix an infinite loop if DISCARD TABLESPACE coincides with INSERT or some other table operation; fix a potential crash if DISCARD TABLESPACE coincides with a cascaded FOREIGN KEY operation in the same table; do not allow DISCARD TABLESPACE of a referenced table if FOREIGN_KEY_CHECKS=1
      708eebea
  10. 22 Dec, 2004 2 commits
    • unknown's avatar
      ha_innodb.cc: · ef1971ec
      unknown authored
        Add a comment that no InnoDB table lock is now acquired in LOCK TABLES if AUTOCOMMIT=1. This helps to avoid deadlocks when porting old MyISAM applications to InnoDB.
      
      
      sql/ha_innodb.cc:
        Add a comment that no InnoDB table lock is now acquired in LOCK TABLES if AUTOCOMMIT=1. This helps to avoid deadlocks when porting old MyISAM applications to InnoDB.
      ef1971ec
    • unknown's avatar
      ha_innodb.cc: · e6dfed9f
      unknown authored
        If AUTOCOMMIT=1, do not acquire an InnoDB table lock in LOCK TABLES; this makes porting of old MyISAM applications to InnoDB easier, since in that mode InnoDB table locks caused deadlocks very easily
      
      
      sql/ha_innodb.cc:
        If AUTOCOMMIT=1, do not acquire an InnoDB table lock in LOCK TABLES; this makes porting of old MyISAM applications to InnoDB easier, since in that mode InnoDB table locks caused deadlocks very easily
      e6dfed9f
  11. 17 Dec, 2004 1 commit
    • unknown's avatar
      InnoDB: Fixed bugs in the padding and trimming of trailing spaces · 7b063137
      unknown authored
      that affected the UCS2 character set. (Bug #7350)
      
      
      innobase/data/data0type.c:
        Added dtype_get_charset_coll_noninline()
      innobase/include/data0type.h:
        Added dtype_get_charset_coll_noninline()
      innobase/include/row0mysql.h:
        Added charset field to mysql_row_templ_struct.
      innobase/include/row0mysql.ic:
        row_mysql_store_col_in_innobase_format():
        When removing trailing spaces, treat the UCS2 character set properly.
      innobase/rem/rem0cmp.c:
        cmp_whole_field(): Do not remove trailing 0x20 bytes, as
        innobase_mysql_cmp() implicitly pads the strings with trailing
        spaces as necessary.
      innobase/row/row0sel.c:
        row_sel_field_store_in_mysql_format(): Do not pad with 0x20 bytes.
        row_sel_store_mysql_rec(): Pad VARCHARs with trailing spaces
        (0x20, or 0x0020 in UCS2).
      sql/ha_innodb.cc:
        build_template(): Initialize templ->charset
      7b063137
  12. 10 Dec, 2004 1 commit
    • unknown's avatar
      dict0dict.h, dict0dict.c, ha_innodb.cc: · c486461e
      unknown authored
        Fix for the 0xA0 character problem in the InnoDB FOREIGN KEY parser: if my_isspace() treats 0xA0 as space, then let InnoDB do the same; this might break some multi-byte charset id's, though for big5, ujis, sjis this seems not to change the current behavior (I checked the tables in /share/charsets); this fix must NOT be merged to 4.1 because in 4.1 everything is in UTF-8
      
      
      sql/ha_innodb.cc:
        Fix for the 0xA0 character problem in the InnoDB FOREIGN KEY parser: if my_isspace() treats 0xA0 as space, then let InnoDB do the same; this might break some multi-byte charset id's, though for big5, ujis, sjis this seems not to change the current behavior (I checked the tables in /share/charsets); this fix must NOT be merged to 4.1 because in 4.1 everything is in UTF-8
      innobase/dict/dict0dict.c:
        Fix for the 0xA0 character problem in the InnoDB FOREIGN KEY parser: if my_isspace() treats 0xA0 as space, then let InnoDB do the same; this might break some multi-byte charset id's, though for big5, ujis, sjis this seems not to change the current behavior (I checked the tables in /share/charsets); this fix must NOT be merged to 4.1 because in 4.1 everything is in UTF-8
      innobase/include/dict0dict.h:
        Fix for the 0xA0 character problem in the InnoDB FOREIGN KEY parser: if my_isspace() treats 0xA0 as space, then let InnoDB do the same; this might break some multi-byte charset id's, though for big5, ujis, sjis this seems not to change the current behavior (I checked the tables in /share/charsets); this fix must NOT be merged to 4.1 because in 4.1 everything is in UTF-8
      c486461e
  13. 30 Nov, 2004 1 commit
    • unknown's avatar
      InnoDB: Allow ALTER TABLE to do intermediate COMMIT also when the table · d6180d37
      unknown authored
      contains auto_increment columns.  (Bug #6633)
      
      
      innobase/include/lock0lock.h:
        Replaced lock_get_table()
        with lock_get_src_table() and lock_is_table_exclusive()
      innobase/lock/lock0lock.c:
        Replaced lock_get_table()
        with lock_get_src_table() and lock_is_table_exclusive()
      sql/ha_innodb.cc:
        ha_innobase::write_row(): Improve the ALTER TABLE optimization
        (do intermediate COMMIT also if table contains auto_increment columns)
      d6180d37
  14. 26 Nov, 2004 1 commit
    • unknown's avatar
      InnoDB: Make intermediate COMMITs in ALTER TABLE more robust (Bug #6633) · 346dce93
      unknown authored
      innobase/include/lock0lock.h:
        Replaced lock_get_ix_table() with lock_get_table().
      innobase/lock/lock0lock.c:
        Replaced lock_get_ix_table() with lock_get_table().
      innobase/include/row0mysql.h:
        row_lock_table_for_mysql(): Added parameter mode.
      innobase/row/row0mysql.c:
        row_lock_table_for_mysql(): Added parameter mode.
      sql/ha_innodb.cc:
        ha_innobase::write_row(): Make ALTER TABLE commits more robust:
        account for conversions from non-InnoDB format,
        do not attempt to commit if there are other than
        a single IX or IS lock on the source table, and
        the source table is in InnoDB format.  This
        prohibits intermediate commits for OPTIMIZE TABLE
        if the table contains an auto_increment field.
      346dce93
  15. 25 Nov, 2004 1 commit
    • unknown's avatar
      ha_innodb.cc: · 5557ae74
      unknown authored
        Add conversion of the InnoDB error DB_LOCK_TABLE_FULL to the corresponding MySQL error
      
      
      sql/ha_innodb.cc:
        Add conversion of the InnoDB error DB_LOCK_TABLE_FULL to the corresponding MySQL error
      5557ae74
  16. 16 Nov, 2004 3 commits
    • unknown's avatar
      ha_innodb.cc: · d711df11
      unknown authored
        Anthony's http://lists.mysql.com/internals/18505 patch for DROP DATABASE broke caused it to return errno if .ibd files were present (bas_ext() was obsolete in ha_innodb.cc); fix this
      
      
      sql/ha_innodb.cc:
        Anthony's http://lists.mysql.com/internals/18505 patch for DROP DATABASE broke caused it to return errno if .ibd files were present (bas_ext() was obsolete in ha_innodb.cc); fix this
      d711df11
    • unknown's avatar
      ha_innodb.cc: · 7d074100
      unknown authored
      Manually ported this bug fix from 4.0: 
       Fix InnoDB bug #6287: if one uses INSERT IGNORE to insert several rows at a time, and the first inserts are ignored because of a duplicate key collision, then InnoDB in a replication slave assigns AUTO_INCREMENT values 1 bigger than in the master
      
      
      sql/ha_innodb.cc:
        Fix InnoDB bug #6287: if one uses INSERT IGNORE to insert several rows at a time, and the first inserts are ignored because of a duplicate key collision, then InnoDB in a replication slave assigns AUTO_INCREMENT values 1 bigger than in the master
      7d074100
    • unknown's avatar
      ha_innodb.cc: · 16d735ad
      unknown authored
        Fix InnoDB bug #6287: if one uses INSERT IGNORE to insert several rows at a time, and the first inserts are ignored because of a duplicate key collision, then InnoDB in a replication slave assigns AUTO_INCREMENT values 1 bigger than in the master
      
      
      sql/ha_innodb.cc:
        Fix InnoDB bug #6287: if one uses INSERT IGNORE to insert several rows at a time, and the first inserts are ignored because of a duplicate key collision, then InnoDB in a replication slave assigns AUTO_INCREMENT values 1 bigger than in the master
      16d735ad
  17. 04 Nov, 2004 1 commit
    • unknown's avatar
      ha_innodb.cc: · f2be61f5
      unknown authored
        write_row(): document the ALTER TABLE tweak better,
        and commit every n*10000 rows, not n*10000-1 rows.
      
      
      sql/ha_innodb.cc:
        write_row(): document the ALTER TABLE tweak better,
        and commit every n*10000 rows, not n*10000-1 rows.
      f2be61f5
  18. 03 Nov, 2004 1 commit
    • unknown's avatar
      InnoDB: commit after every 10000 rows in ALTER TABLE · d07f96cf
      unknown authored
      innobase/include/lock0lock.h:
        Added function lock_get_ix_table()
      innobase/include/row0mysql.h:
        Added parameter "table" to row_lock_table_for_mysql()
      innobase/lock/lock0lock.c:
        Added function lock_get_ix_table()
      innobase/row/row0mysql.c:
        Added parameter "table" to row_lock_table_for_mysql()
      sql/ha_innodb.cc:
        write_row(): commit every 10000 rows in ALTER TABLE
      sql/ha_innodb.h:
        Added member variable num_write_row
      d07f96cf
  19. 02 Nov, 2004 2 commits
    • unknown's avatar
      ha_innodb.cc: · b3042ccb
      unknown authored
        Correct English grammar
      
      
      sql/ha_innodb.cc:
        Correct English grammar
      b3042ccb
    • unknown's avatar
      ha_innodb.cc: · 9c06c80d
      unknown authored
        Backport Jan's fix of the LOAD DATA INFILE REPLACE duplicate key error bug (Bug #5835) to 4.0
      
      
      sql/ha_innodb.cc:
        Backport Jan's fix of the LOAD DATA INFILE REPLACE duplicate key error bug (Bug #5835) to 4.0
      9c06c80d
  20. 22 Oct, 2004 1 commit
  21. 21 Oct, 2004 1 commit
    • unknown's avatar
      SHOW TABLE STATUS now prints create_time, update_time and check_time · 81b97c48
      unknown authored
      for InnoDB tables. Note that these times may always be correct ones,
      because for example ALTER TABLE creates a table again.
      
      
      
      innobase/include/os0file.h:
        Added information of file timestamps and a function os_file_get_status
        to get that information using stat().
      innobase/os/os0file.c:
        Added function that return information obout the specified file.
      sql/ha_innodb.cc:
        Get timestamps for the file where the table is stored.
      81b97c48
  22. 20 Oct, 2004 1 commit
    • unknown's avatar
      Code cleanups (done during review of new code) · ed8ec2cf
      unknown authored
      Rename innodb_table_locks_old_behavior -> innodb_table_locks
      Set innodb_table_locks to off by default to get same behaviour as in MySQL 4.0.20
      (This means that Innodb ignore table locks by default, which makes it easier to combine MyISAM and InnoDB to simulate a transaction)
      
      
      libmysql/libmysql.c:
        Use ulong instead of unsigned long
        Reuse _dig_vec()
      myisam/myisampack.c:
        Simplify code
      mysql-test/r/innodb-lock.result:
        new test case
      mysql-test/t/innodb-lock.test:
        new test case
      sql/ha_innodb.cc:
        Rename innodb_table_locks_old_behavior -> innodb_table_locks
      sql/mysqld.cc:
        Rename innodb_table_locks_old_behavior -> innodb_table_locks
        Set this off by default to get same behaviour as in MySQL 4.0.20
      sql/set_var.cc:
        Rename innodb_table_locks_old_behavior -> innodb_table_locks
      sql/sql_class.h:
        Rename innodb_table_locks_old_behavior -> innodb_table_locks
      ed8ec2cf
  23. 19 Oct, 2004 2 commits
    • unknown's avatar
      Review of all code pushed since last review · 4736d0fe
      unknown authored
      Simple optimzations and cleanups
      Removed compiler warnings and fixed portability issues
      Added client functions 'mysql_embedded()' to allow client to check if we are using embedded server
      Fixes for purify
      
      
      client/mysqlimport.c:
        Remove not used variable
      client/mysqltest.c:
        Remove usage of MAXPATHLEN (all MySQL code uses FN_REFLEN)
        Simplified code
        Remove usage of sprintf("%llu") as this is not portable
      include/mysql.h:
        Added mysql_embedded() to be able to easily check if we are using the embedded server
      innobase/srv/srv0start.c:
        Don't use memcmp() when using purify (to avoid false warnings)
      libmysql/libmysql.c:
        Added mysql_embedded() to be able to easily check if we are using the embedded server
      libmysql/libmysql.def:
        Added mysql_embedded() to be able to easily check if we are using the embedded server
      myisam/myisam_ftdump.c:
        Remove compiler warning
      myisam/myisamchk.c:
        Remove compiler warning
      myisam/rt_test.c:
        #ifdef not used code
      mysys/hash.c:
        Remove compiler warning (from last push)
      mysys/my_gethwaddr.c:
        Remove compiler warning
      ndb/src/ndbapi/ndberror.c:
        #ifdef not used code
      regex/regcomp.c:
        Remove not used code
      regex/regcomp.ih:
        Remove not used code (to remove compiler warnings)
      sql-common/client.c:
        Remove compiler warnings
      sql/field.cc:
        Simple optimization
      sql/ha_innodb.cc:
        Rename mysql_embedded -> mysqld_embedded
      sql/item.cc:
        Fix comments
        Move variables first on block
        Remove else after return
        Simple optimizations
        (no logic changes)
      sql/item_cmpfunc.cc:
        Added comment
      sql/mysql_priv.h:
        Rename mysql_embedded -> mysqld_embedded
      sql/mysqld.cc:
        Rename mysql_embedded -> mysqld_embedded
      sql/sql_acl.cc:
        Added comments
        simple optimization
        Fixed 'very unlikely' bug when doing REVOKE ALL PRIVILEGES
      sql/sql_select.cc:
        More comments
        Simple optimization
      sql/sql_show.cc:
        Simple changes to make similar code similar
        More comments
      sql/sql_string.cc:
        Trivial optimization and better code layout
      strings/Makefile.am:
        Change xml.c to use bcmp to avoid warnings from purify
      strings/xml.c:
        Change xml.c to use bcmp to avoid warnings from purify
      tests/client_test.c:
        Remove usage of MAXPATHLEN (all MySQL code uses FN_REFLEN)
      4736d0fe
    • unknown's avatar
      Fixed bug #5835 load data infile...replace error with InnoDB table. · c144e1a2
      unknown authored
      sql/ha_innodb.cc:
        Note that LOAD DATA INFILE REPLACE also handles a duplicate key error
        itself, and we must not decrement the autoinc counter if we are
        performing that statement.
      c144e1a2
  24. 18 Oct, 2004 2 commits
    • unknown's avatar
      ha_innodb.cc: · 0cef3945
      unknown authored
        Replace a tolower() loop with innobase_casedn_str()
      
      
      sql/ha_innodb.cc:
        Replace a tolower() loop with innobase_casedn_str()
      0cef3945
    • unknown's avatar
      InnoDB: Treat UTF-8 strings properly in case insensitive operations · e4938933
      unknown authored
      innobase/dict/dict0dict.c:
        Use innobase_strcasecmp() and innobase_casedn_str()
        instead of ut_cmp_in_lower_case() and ut_cpy_in_lower_case()
      innobase/include/ut0byte.h:
        Remove ut_cpy_in_lower_case() and ut_cmp_in_lower_case()
      innobase/ut/ut0byte.c:
        Remove ut_cpy_in_lower_case() and ut_cmp_in_lower_case()
      sql/ha_innodb.cc:
        Add innobase_strcasecmp() and innobase_casedn_str()
        Replace tolower() loop with innobase_casedn_str()
        Replace my_casedn_str() with innobase_casedn_str()
        Replace ut_cmp_in_lower_case() with innobase_strcasecmp()
      e4938933
  25. 15 Oct, 2004 1 commit
    • unknown's avatar
      Use already parsed SQL-query in the current thread when determining · 1927d24e
      unknown authored
      was the query REPLACE or LOAD DATA INFILE REPLACE.
      
      
      innobase/row/row0ins.c:
        Find SQL-query directly from current thread and see if the
        query was REPLACE or LOAD DATA INFILE REPLACE.
      sql/ha_innodb.cc:
        Find current thread and return true if SQL-query in the current
        thread was either REPLACE or LOAD DATA INFILE REPLACE.
      1927d24e
  26. 13 Oct, 2004 2 commits
    • unknown's avatar
      Added startup option and settable session variable · f0ed73d8
      unknown authored
      innodb_table_locks_old_behavior: do not acquire an
      InnoDB table lock for LOCK TABLES, as in mysql-4.0.18
      and earlier.
      
      
      sql/ha_innodb.cc:
        Do not acquire an InnoDB table lock for LOCK TABLES if
        innodb_table_locks_old_behavior is enabled.
      sql/mysqld.cc:
        Added innodb_table_locks_old_behavior
      sql/set_var.cc:
        Added innodb_table_locks_old_behavior
      sql/sql_class.h:
        Added innodb_table_locks_old_behavior
      f0ed73d8
    • unknown's avatar
      srv0srv.c, log0log.c, srv0srv.h, ha_innodb.cc, ha_innodb.h: · 7b1f818d
      unknown authored
        Implement innobase_very_fast_shutdown and innobase_start_trx_and_assign_read_view(); these were requested by Guilhem
      
      
      sql/ha_innodb.h:
        Implement innobase_very_fast_shutdown and innobase_start_trx_and_assign_read_view(); these were requested by Guilhem
      sql/ha_innodb.cc:
        Implement innobase_very_fast_shutdown and innobase_start_trx_and_assign_read_view(); these were requested by Guilhem
      innobase/include/srv0srv.h:
        Implement innobase_very_fast_shutdown and innobase_start_trx_and_assign_read_view(); these were requested by Guilhem
      innobase/log/log0log.c:
        Implement innobase_very_fast_shutdown and innobase_start_trx_and_assign_read_view(); these were requested by Guilhem
      innobase/srv/srv0srv.c:
        Implement innobase_very_fast_shutdown and innobase_start_trx_and_assign_read_view(); these were requested by Guilhem
      7b1f818d
  27. 12 Oct, 2004 1 commit
    • unknown's avatar
      ha_innodb.cc: · eb3b0480
      unknown authored
        Change error code to HA_ERR_ROW_IS_REFERENCED if we cannot DROP a parent table referenced by a FOREIGN KEY constraint; this error number is less misleading than the previous value HA_ERR_CANNOT_ADD_FOREIGN, but misleading still; we should introduce to 5.0 a proper MySQL error code
      
      
      sql/ha_innodb.cc:
        Change error code to HA_ERR_ROW_IS_REFERENCED if we cannot DROP a parent table referenced by a FOREIGN KEY constraint; this error number is less misleading than the previous value HA_ERR_CANNOT_ADD_FOREIGN, but misleading still; we should introduce to 5.0 a proper MySQL error code
      eb3b0480
  28. 07 Oct, 2004 2 commits
    • unknown's avatar
      Many files: · 7efa215e
      unknown authored
        Fix bug #5137: if innodb_file_per_table was specified, CREATE TEMPORARY TABLE ... TYPE=InnoDB said that cannot find path specified, and made mysqld to exit(1)
      
      
      sql/ha_innodb.cc:
        Fix bug #5137: if innodb_file_per_table was specified, CREATE TEMPORARY TABLE ... TYPE=InnoDB said that cannot find path specified, and made mysqld to exit(1)
      innobase/row/row0mysql.c:
        Fix bug #5137: if innodb_file_per_table was specified, CREATE TEMPORARY TABLE ... TYPE=InnoDB said that cannot find path specified, and made mysqld to exit(1)
      innobase/fil/fil0fil.c:
        Fix bug #5137: if innodb_file_per_table was specified, CREATE TEMPORARY TABLE ... TYPE=InnoDB said that cannot find path specified, and made mysqld to exit(1)
      innobase/dict/dict0crea.c:
        Fix bug #5137: if innodb_file_per_table was specified, CREATE TEMPORARY TABLE ... TYPE=InnoDB said that cannot find path specified, and made mysqld to exit(1)
      innobase/dict/dict0dict.c:
        Fix bug #5137: if innodb_file_per_table was specified, CREATE TEMPORARY TABLE ... TYPE=InnoDB said that cannot find path specified, and made mysqld to exit(1)
      innobase/dict/dict0load.c:
        Fix bug #5137: if innodb_file_per_table was specified, CREATE TEMPORARY TABLE ... TYPE=InnoDB said that cannot find path specified, and made mysqld to exit(1)
      innobase/dict/dict0mem.c:
        Fix bug #5137: if innodb_file_per_table was specified, CREATE TEMPORARY TABLE ... TYPE=InnoDB said that cannot find path specified, and made mysqld to exit(1)
      innobase/include/mem0mem.ic:
        Fix bug #5137: if innodb_file_per_table was specified, CREATE TEMPORARY TABLE ... TYPE=InnoDB said that cannot find path specified, and made mysqld to exit(1)
      innobase/include/dict0mem.h:
        Fix bug #5137: if innodb_file_per_table was specified, CREATE TEMPORARY TABLE ... TYPE=InnoDB said that cannot find path specified, and made mysqld to exit(1)
      innobase/include/fil0fil.h:
        Fix bug #5137: if innodb_file_per_table was specified, CREATE TEMPORARY TABLE ... TYPE=InnoDB said that cannot find path specified, and made mysqld to exit(1)
      innobase/include/mem0mem.h:
        Fix bug #5137: if innodb_file_per_table was specified, CREATE TEMPORARY TABLE ... TYPE=InnoDB said that cannot find path specified, and made mysqld to exit(1)
      innobase/mem/mem0mem.c:
        Fix bug #5137: if innodb_file_per_table was specified, CREATE TEMPORARY TABLE ... TYPE=InnoDB said that cannot find path specified, and made mysqld to exit(1)
      7efa215e
    • unknown's avatar
      ha_innodb.cc: · ff879b93
      unknown authored
        Merge manually the InnoDB mysqldump -l crash patch (crash with LOCK TABLES ... LOCAL) from 4.0 to 4.1; some code cleanup
      
      
      sql/ha_innodb.cc:
        Merge manually the mysqldump -l crash pacth from 4.0 to 4.1; some code cleanup
      ff879b93