An error occurred fetching the project authors.
- 25 Nov, 2004 1 commit
-
-
ingo@mysql.com authored
Added new commands CREATE USER and RENAME USER. Changed behaviour of DROP USER. Changed an error messages for the new commands.
-
- 21 Nov, 2004 1 commit
-
-
bell@sanja.is.com.ua authored
-
- 13 Nov, 2004 1 commit
-
-
bell@sanja.is.com.ua authored
used only one implementation of format parser of (printf) fixed multistatement
-
- 12 Nov, 2004 1 commit
-
-
serg@serg.mylan authored
-
- 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.
-
- 22 Oct, 2004 1 commit
-
-
pem@mysql.comhem.se authored
...and no ALTER privilege either. For now, only the definer and root can drop or alter an SP.
-
- 20 Oct, 2004 1 commit
-
-
bell@sanja.is.com.ua authored
net_printf/send_error calls replaced by my_error family functions -1/1 (sent/unsent) error reporting removed (WL#2133)
-
- 02 Oct, 2004 1 commit
-
-
monty@mishka.local authored
More tests. Better error messages. Fixed bug when checking if we updated all needed columns for INSERT. Give an error if we encounter a wrong float value during parsing. Don't print DEFAULT for columns without a default value in SHOW CREATE/SHOW FIELDS. Fixed UPDATE IGNORE when using STRICT mode.
-
- 29 Sep, 2004 1 commit
-
-
bell@sanja.is.com.ua authored
CHECK OPTION moved to one function view name added to error messages
-
- 28 Sep, 2004 1 commit
-
-
monty@mishka.local authored
Under strict mode MySQL will generate an error message if there was any conversion when assigning data to a field. Added checking of date/datetime fields. If strict mode, give error if we have not given value to field without a default value (for INSERT)
-
- 15 Sep, 2004 1 commit
-
-
bell@sanja.is.com.ua authored
-
- 07 Sep, 2004 1 commit
-
-
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.
-
- 03 Sep, 2004 1 commit
-
-
bell@sanja.is.com.ua authored
-
- 02 Sep, 2004 2 commits
-
-
paul@kite-hub.kitebird.com authored
Add GPL comment
-
bell@sanja.is.com.ua authored
-
- 31 Aug, 2004 1 commit
-
-
bar@mysql.com authored
-
- 27 Aug, 2004 1 commit
-
-
bar@mysql.com authored
-
- 26 Aug, 2004 1 commit
-
-
pem@mysql.comhem.se authored
This finishes (almost) WL#2002: Implement stored procedure GOTO. Only the syntax issue for free labels remains ("label L;" vs "L:").
-
- 23 Aug, 2004 1 commit
-
-
monty@mysql.com authored
Fixed error messages
-
- 10 Aug, 2004 1 commit
-
-
paul@kite-hub.kitebird.com authored
fix error message
-
- 04 Aug, 2004 1 commit
-
-
tim@sand.box authored
-
- 29 Jul, 2004 1 commit
-
-
pem@mysql.comhem.se authored
Simply disallow it, just as we disallow creation of routines from within other SPs.
-
- 21 Jul, 2004 2 commits
-
-
hf@deer.(none) authored
-
bell@sanja.is.com.ua authored
error handling of view initialization fixed (Bug#4599)
-
- 15 Jul, 2004 1 commit
-
-
bell@sanja.is.com.ua authored
two TABLE_LIST copy eliminated
-
- 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 5 commits
-
-
paul@kite-hub.kitebird.com authored
-
paul@kite-hub.kitebird.com authored
-
pem@mysql.comhem.se authored
-
paul@ice.snake.net 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 2 commits
-
-
bell@sanja.is.com.ua authored
-
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)
-