An error occurred fetching the project authors.
- 30 May, 2006 1 commit
-
-
igor@rurik.mysql.com authored
refers to a column name.
-
- 28 May, 2006 1 commit
-
-
igor@rurik.mysql.com authored
refers to a column name. Added a new error message ER_INDEX_DOES_NOT_EXIST.
-
- 08 May, 2005 1 commit
-
-
mwagner@ultrafly.mysql.com authored
Add newline at EOF for proper processing by comp-err.exe on Windows where fgets() works differently than Linux (Bug #6195).
-
- 07 May, 2005 1 commit
-
-
mwagner@ultrafly.mysql.com authored
Add newline at EOF for proper processing by comp-err.exe on Windows where fgets() works differently than Linux (Bug #6195).
-
- 10 Nov, 2004 2 commits
-
-
guilhem@mysql.com authored
no new message in 4.1 (causes merge issues with 5.0). Using ER_UNKNOW_ERROR and hardcoded message string instead.
-
guilhem@mysql.com authored
WL#1596 "make mysqldump --master-data --single-transaction able to do online dump of InnoDB AND report reliable binlog coordinates corresponding to the dump". The good news is that now mysqldump can be used to get an online backup of InnoDB *which works for point-in-time recovery and replication slave creation*. Formerly, mysqldump --master-data --single-transaction used to call in fact mysqldump --master-data, so the dump was not an online dump (took big lock all time of dump). The only lock which is now taken in this patch is at the beginning of the dump: mysqldump does: FLUSH TABLES WITH READ LOCK; START TRANSACTION WITH CONSISTENT SNAPSHOT; SHOW MASTER STATUS; UNLOCK TABLES; so the lock time is in fact the time FLUSH TABLES WITH READ LOCK takes to return (can be 0 or very long, if a table is undergoing a huge update). I have done some more minor changes listed in the paragraph of mysqldump.c. WL#2237 "WITH CONSISTENT SNAPSHOT clause for START TRANSACTION": it's a START TRANSACTION which additionally starts a consistent read on all capable storage engine (i.e. InnoDB). So, can serve as a replacement for BEGIN; SELECT * FROM some_innodb_table LIMIT 1; which starts a consistent read too.
-
- 02 Sep, 2004 1 commit
-
-
paul@kite-hub.kitebird.com authored
Add GPL comment
-
- 31 Aug, 2004 1 commit
-
-
bar@mysql.com authored
-
- 27 Aug, 2004 1 commit
-
-
bar@mysql.com authored
-
- 23 Aug, 2004 1 commit
-
-
monty@mysql.com authored
Fixed error messages
-
- 21 Jul, 2004 1 commit
-
-
hf@deer.(none) authored
-
- 07 Jul, 2004 1 commit
-
-
bar@mysql.com authored
-
- 29 Jun, 2004 1 commit
-
-
hf@deer.(none) authored
-
- 18 Jun, 2004 1 commit
-
-
dlenev@brandersnatch.localdomain authored
Added basic per-thread time zone functionality (based on public domain elsie-code). Now user can select current time zone (from the list of time zones described in system tables). All NOW-like functions honor this time zone, values of TIMESTAMP type are interpreted as values in this time zone, so now our TIMESTAMP type behaves similar to Oracle's TIMESTAMP WITH LOCAL TIME ZONE (or proper PostgresSQL type). WL#1266 "CONVERT_TZ() - basic time with time zone conversion function". Fixed problems described in Bug #2336 (Different number of warnings when inserting bad datetime as string or as number). This required reworking of datetime realted warning hadling (they now generated at Field object level not in conversion functions). Optimization: Now Field class descendants use table->in_use member instead of current_thd macro.
-
- 16 Jun, 2004 2 commits
-
-
paul@kite-hub.kitebird.com authored
-
paul@ice.snake.net authored
and affected test results.
-
- 15 Jun, 2004 1 commit
-
-
paul@kite-hub.kitebird.com authored
and affected test results.
-
- 21 May, 2004 1 commit
-
-
sergefp@mysql.com authored
-
- 13 May, 2004 1 commit
-
-
magnus@neptunus.(none) authored
- New solution after discussions with Sergei, no handler specific code or error messages should be in sql layer. next_result, only check for error if check is -1 Improved index_read
-
- 11 May, 2004 1 commit
-
-
magnus@neptunus.(none) authored
- Close an open scan if index_read is called without closing the previous one. - Removed some errors that occured during previous merge
-
- 07 Apr, 2004 1 commit
-
-
bell@sanja.is.com.ua authored
fixed IN subselect with basic constant left expression SQLCOM_CREATE_TABLE, SQLCOM_UPDATE_MULTI, SQLCOM_REPLACE_SELECT, SQLCOM_INSERT_SELECT, QLCOM_DELETE_MULTI fixed to be compatible with PS (BUG#3398, BUG#3406) fixed multiupdate privelege check (BUG#3408) fixed multiupdate tables check (BUG#3411) unchecked commands now is rejected by PS protocol to avoid serever crash fixed cleunup procedure to be compatible sith DO/SET (BUG#3393)
-
- 02 Apr, 2004 1 commit
-
-
dlenev@jabberwock.localdomain authored
Final version of patch. Adds support for specifying of DEFAULT NOW() and/or ON UPDATE NOW() clauses for TIMESTAMP field definition. Current implementation allows only one such field per table and uses several unireg types for storing info about this properties of field. It should be replaced with better implementation when new .frm format is introduced.
-
- 15 Mar, 2004 1 commit
-
-
gluh@gluh.mysql.r18.ru authored
-
- 13 Mar, 2004 1 commit
-
-
vva@eagle.mysql.r18.ru authored
-
- 07 Mar, 2004 1 commit
-
-
paul@ice.local authored
-
- 02 Mar, 2004 1 commit
-
-
serg@serg.mylan authored
-
- 29 Feb, 2004 1 commit
-
-
paul@ice.snake.net authored
-
- 28 Feb, 2004 1 commit
-
-
guilhem@mysql.com authored
-
- 22 Feb, 2004 1 commit
-
-
guilhem@mysql.com authored
-
- 21 Feb, 2004 1 commit
-
-
guilhem@mysql.com authored
"--read-only gives weird error on update". It is not fixable in 4.0 because it requires modifying the sql/share/*/errmsg.txt files. So it is fixed in 4.1 like this: the ER_SKIP_GRANT_TABLES is replaced by a more generic ER_OPTION_PREVENTS_STATEMENT which can be used both for "can't do this because of --skip-grant-tables" and "can't do this because of --read-only" (for this we don't use ER_CANT_UPDATE_WITH_READLOCK anymore). So now the message for --read-only is: "The MySQL server is running with the --read-only option so cannot execute this statement".
-
- 15 Feb, 2004 1 commit
-
-
serg@serg.mylan authored
--disable-warning in union.test
-
- 26 Jan, 2004 1 commit
-
-
gluh@gluh.mysql.r18.ru authored
when DROP USER if --skip-grant-tables
-
- 23 Jan, 2004 1 commit
-
-
hf@deer.(none) authored
-
- 06 Jan, 2004 1 commit
-
-
guilhem@mysql.com authored
I had not corrected these languages. As it has been discussed with the docs team, the new messages will be merged to 4.1, and then will be translated in 4.1 (they will remain in English in 4.0).
-
- 04 Jan, 2004 1 commit
-
-
bell@sanja.is.com.ua authored
allow UPDATE and DELETE stetements with tables derived from subquery if they are not updated (BUG#2117) allow delete table by alias in multi-delete statement
-
- 23 Dec, 2003 1 commit
-
-
paul@teton.kitebird.com authored
using syntax that is not actually legal in GRANT.
-
- 19 Dec, 2003 1 commit
-
-
monty@mysql.com authored
Cleaned up embedded library access and query cache handling Changed min stack size to 128K (to allow longer MyISAM keys) Fixed wrong priority for XOR (should be less than NEG to get -1^1 to work)
-
- 17 Dec, 2003 1 commit
-
-
vva@eagle.mysql.r18.ru authored
(bug #2086)
-
- 10 Dec, 2003 1 commit
-
-
Deprecate the use of TYPE=... Preferred syntax is ENGINE=
-
- 08 Dec, 2003 1 commit
-
-
monty@mysql.com authored
-