An error occurred fetching the project authors.
- 23 Aug, 2004 1 commit
-
-
monty@mysql.com authored
Fixed error messages
-
- 04 Aug, 2004 1 commit
-
-
tim@sand.box authored
-
- 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
-
- 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)
-
- 16 Dec, 2003 1 commit
-
-
guilhem@mysql.com authored
more general message when slave can't start because of incorrect replication information, the previous one was sometimes a misleading indication (i.e. sometimes the problem had nothing to do with system permissions). The perfect fix would be to report the exact error to the client (instead of pointing the client to the error log); this is a bit of work so it's more a development task: WL#1088 "Move all hardcoded messages of replication to share/errmsg.txt". I was not able to modify the errmsg.txt in these sql/ subdirectories: danish dutch german italian portuguese russian spanish swedish ukrainian
-
- 10 Dec, 2003 1 commit
-
-
Deprecate the use of TYPE=... Preferred syntax is ENGINE=
-
- 08 Dec, 2003 1 commit
-
-
monty@mysql.com authored
-
- 02 Dec, 2003 1 commit
-
-
- 26 Nov, 2003 1 commit
-
-
hf@deer.(none) authored
WL#1284 (warnings about --skip-name-resolve) Messages corrected
-
- 20 Nov, 2003 1 commit
-
-
hf@deer.(none) authored
WL#1284 (warnings about --skip-name-resolve) Now MySQL will issue warnings during startup about entries in grant tables with hostnames that require resolve, and after GRANT commands with that kind of hostnames.
-
- 18 Nov, 2003 3 commits
-
-
monty@mashka.mysql.fi authored
-
monty@mashka.mysql.fi authored
New multi-key-cache handling. This was needed becasue the old one didn't work reliable with MERGE tables. ALTER TABLE table_name ... CHARACTER SET ... now changes all char/varchar/text columns to the given character set (One must use ALTER TABLE ... DEFAULT CHARACTER SET ... to change the default character set) Fixed that have_compress is detected properly (fixes problems with func_compress.test on platforms without zlib) New syntax for CACHE INDEX ('keys' is optional if no index name is given and one mentions the key cache name only ones) Removed compiler warnings Added mysql_set_server_option() to allow clients like PHP to easaily set/reset the multi-statement flag.
-
serg@serg.mylan authored
-
- 04 Nov, 2003 1 commit
-
-
pem@mysql.comhem.se authored
as an error message (which is harmless, but confusing when you compare the output from comp_err for different language files).
-
- 03 Nov, 2003 1 commit
-
-
monty@narttu.mysql.fi authored
Cleaned up (and disabled part of) date/time/datetime format patch. One can't anymore change default read/write date/time/formats. This is becasue the non standard datetime formats can't be compared as strings and MySQL does still a lot of datetime comparisons as strings Changed flag argument to str_to_TIME() and get_date() from bool to uint Removed THD from str_to_xxxx functions and Item class. Fixed core dump when doing --print-defaults Move some common string functions to strfunc.cc Dates as strings are now of type my_charset_bin instead of default_charset() Introduce IDENT_QUOTED to not have to create an extra copy of simple identifiers (all chars < 128) Removed xxx_FORMAT_TYPE enums and replaced them with the old TIMESTAMP_xxx enums Renamed some TIMESTAMP_xxx enums to more appropriate names Use defines instead of integers for date/time/datetime string lengths Added to build system and use the new my_strtoll10() function.
-