An error occurred fetching the project authors.
- 04 Nov, 2009 1 commit
-
-
Luis Soares authored
NOTE: Backport of: bzr log -r revid:sp1r-serg@sergbook.mysql.com-20070505200319-38337 ------------------------------------------------------------ revno: 2469.263.4 committer: serg@sergbook.mysql.com timestamp: Sat 2007-05-05 13:03:19 -0700 message: Removing deprecated features: --master-XXX command-line options log_bin_trust_routine_creators table_type BACKUP TABLE ... RESTORE TABLE ... SHOW PLUGIN LOAD TABLE ... FROM MASTER LOAD DATA FROM MASTER SHOW INNODB STATUS SHOW MUTEX STATUS SHOW TABLE TYPES ... TIMESTAMP(N) ... TYPE=engine RESET SLAVE don't reset connection parameters anymore LOAD DATA: check opt_secure_file_priv before access(filename) improved WARN_DEPRECATED macro
-
- 30 Sep, 2009 1 commit
-
-
Sven Sandberg authored
-
- 07 Jun, 2007 1 commit
-
-
msvensson@pilot.(none) authored
- Turn on binlog only for tests that need it - Skip those tests if --skip-binlog is used
-
- 06 Jun, 2007 1 commit
-
-
jimw@rama.(none) authored
The patch for WL 1563 added a new duplicate key error message so that the key name could be provided instead of the key number. But the error code for the new message was used even though that did not need to change. This could cause unnecessary problems for applications that used the old ER_DUP_ENTRY error code to detect duplicate key errors.
-
- 31 May, 2007 1 commit
-
-
df@pippilotta.erinye.com authored
-
- 18 May, 2007 2 commits
-
-
holyfoot/hf@mysql.com/hfmain.(none) authored
-
serg@sergbook.mysql.com authored
-
- 16 Apr, 2007 1 commit
-
-
aelkin@dl145j.mysql.com authored
tests for the bug and associated is moved into another file because they appeared to be binlog-format sensitive.
-
- 05 Apr, 2007 1 commit
-
-
jani@ua141d10.elisa.omakaista.fi authored
-
- 24 Mar, 2007 2 commits
-
-
removing test host sensitive stuff for pushbuild
-
aelkin/elkin@andrepl.(none) authored
eliminating the unnecessary option; and replacing site-dependant stuff in the test
-
- 23 Mar, 2007 1 commit
-
-
aelkin/elkin@andrepl.(none) authored
thd->options' OPTION_STATUS_NO_TRANS_UPDATE bit was not restored at the end of SF() invocation, where SF() modified non-ta table. As the result of this artifact it was not possible to detect whether there were any side-effects when top-level query ends. If the top level query table was not modified and the bit is lost there would be no binlogging. Fixed with preserving the bit inside of thd->no_trans_update struct. The struct agregates two bool flags telling whether the current query and the current transaction modified any non-ta table. The flags stmt, all are dropped at the end of the query and the transaction.
-
- 22 Jan, 2007 1 commit
-
-
monty@mysql.com/narttu.mysql.fi authored
Changed error message to be compatible with old error file Added new error message for new DUP_ENTRY syntax
-
- 18 May, 2006 1 commit
-
-
msvensson@shellback.(none) authored
-
- 09 Mar, 2006 1 commit
-
-
msvensson@neptunus.(none) authored
-Add test case Move testcase that needs innodb from sp.test => sp_trans.test
-
- 19 Jan, 2006 1 commit
-
-
pem@mysql.com authored
Lowered the parameter to 10, and also renamed non-standard table names to t3.
-
- 23 Nov, 2005 1 commit
-
-
pem@mysql.com authored
Don't set thd->is_fatal_error in sql_update for duplicate key errors.
-
- 19 Nov, 2005 1 commit
-
-
dlenev@mysql.com authored
handling of savepoints in stored routines. Fixed ha_rollback_to_savepoint()/ha_savepoint()/ha_release_savepoint() functions to properly handle savepoints inside of stored functions and triggers. Also now when we invoke stored function or trigger we create new savepoint level. We destroy it at the end of function/trigger execution and return back to old savepoint level.
-
- 07 Jun, 2005 2 commits
-
-
lars@mysql.com authored
-
dlenev@brandersnatch.localdomain authored
We should not allow explicit or implicit transaction commits inside of stored functions or triggers (so in autocommit mode we should not do commits after execution of sub-statement). Also since we don't support nested statement transactions in 5.0, we shouldn't commit or rollback stmt transactions while we are inside stored functions or triggers. This should be fixed in later (>=5.1) releases.
-
- 18 Mar, 2005 1 commit
-
-
pem@mysql.comhem.se authored
and removed a have_innodb.inc inclusion which was left by mistake in an earlier change.
-
- 17 Mar, 2005 1 commit
-
-
mysqldev@mysql.com authored
transactional test removed sp_trans.test, sp_trans.result: new file
-