summaryrefslogtreecommitdiff
path: root/sql/share
Commit message (Collapse)AuthorAgeFilesLines
* Addition to fix for bug#10974. Fixed spelling.svoj@mysql.com/april.(none)2006-10-061-1/+1
|
* Merge svojtovich@bk-internal.mysql.com:/home/bk/mysql-5.0svoj@mysql.com/april.(none)2006-10-021-0/+3
|\ | | | | | | into mysql.com:/home/svoj/devel/mysql/merge/mysql-5.0-engines
| * Merge epotemkin@bk-internal.mysql.com:/home/bk/mysql-5.0-optevgen@moonbone.local2006-09-291-0/+3
| |\ | | | | | | | | | into moonbone.local:/work/5505-bug-5.0-opt-mysql
| | * Fixed bug#5505: Wrong error message on INSERT into a viewevgen@moonbone.local2006-09-291-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | On an INSERT into an updatable but non-insertable view an error message was issued stating the view being not updatable. This can lead to a confusion of a user. A new error message is introduced. Is is showed when a user tries to insert into a non-insertable view.
* | | After merge fix.svoj@mysql.com/april.(none)2006-09-271-1/+1
|/ /
* | Merge svojtovich@bk-internal.mysql.com:/home/bk/mysql-5.0svoj@april.(none)2006-09-181-0/+2
|\ \ | |/ |/| | | into april.(none):/home/svoj/devel/mysql/merge/mysql-5.0-engines
| * Bug#20573acurtis/antony@xiphis.org/ltantony.xiphis.org2006-08-301-0/+2
| | | | | | | | | | "strict mode: inserts autogenerated auto_increment value bigger than max" Strict mode should fail if autoincrement value is out of range
* | Merge bk-internal.mysql.com:/home/bk/mysql-5.0kostja@bodhi.local2006-08-301-0/+6
|\ \ | |/ |/| | | into bodhi.local:/opt/local/work/mysql-5.0-14897
| * Fix for BUG#16899: Possible buffer overflow in handling of DEFINER-clauseanozdrin/alik@alik.2006-08-231-0/+6
| | | | | | | | | | | | | | | | | | User name (host name) has limit on length. The server code relies on these limits when storing the names. The problem was that sometimes these limits were not checked properly, so that could lead to buffer overflow. The fix is to check length of user/host name in parser and if string is too long, throw an error.
* | Merge bk-internal.mysql.com:/data0/bk/mysql-5.0rburnett@bk-internal.mysql.com2006-08-151-2/+2
|\ \ | | | | | | | | | into bk-internal.mysql.com:/data0/bk/mysql-5.0-kt
| * \ Merge xiphis.org:/home/antony/work2/mysql-5.0-enginesacurtis/antony@xiphis.org/ltantony.xiphis.org2006-08-141-2/+2
| |\ \ | | |/ | |/| | | | into xiphis.org:/home/antony/work2/mysql-5.0-merge
| | * BUG#14770 - LOAD DATA INFILE doesn't respect default values forsvoj@may.pils.ru2006-08-021-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | columns Fixed confusing warning. Quoting INSERT section of the manual: ---- Inserting NULL into a column that has been declared NOT NULL. For multiple-row INSERT statements or INSERT INTO ... SELECT statements, the column is set to the implicit default value for the column data type. This is 0 for numeric types, the empty string ('') for string types, and the "zero" value for date and time types. INSERT INTO ... SELECT statements are handled the same way as multiple-row inserts because the server does not examine the result set from the SELECT to see whether it returns a single row. (For a single-row INSERT, no warning occurs when NULL is inserted into a NOT NULL column. Instead, the statement fails with an error.) ---- This is also true for LOAD DATA INFILE. For INSERT user can specify DEFAULT keyword as a value to set column default. There is no similiar feature available for LOAD DATA INFILE.
* | | Merge bk-internal.mysql.com:/data0/bk/mysql-5.0rburnett@bk-internal.mysql.com2006-07-241-13/+13
|\ \ \ | |/ / |/| | | | | into bk-internal.mysql.com:/data0/bk/mysql-5.0-kt
| * | Merge bk@192.168.21.1:mysql-5.0-ktholyfoot/hf@mysql.com/deer.(none)2006-07-211-13/+13
| |\ \ | | |/ | |/| | | | into mysql.com:/home/hf/work/mysql-5.0.19672
| | * bug #19672 (paths in embedded server are trucated in error messages)holyfoot@deer.(none)2006-06-201-13/+13
| | | | | | | | | | | | | | | | | | | | | It fact, filenames are truncated in normal server as well, just we get bigger filenames in embedded server tests, but that can potentially get some problems in both cases. I modified file-related error messages to allow longer filenames
* | | errmsg.txt:evgen@moonbone.local2006-07-161-0/+2
|/ / | | | | | | | | Fixed bug#10977: No warning issued if a column name is truncated New warning message is added.
* | Bug #18005: Creating a trigger on mysql.event leads to server crash on ↵jimw@mysql.com2006-06-271-0/+2
|/ | | | | | | | | | | | scheduler startup Bug #18361: Triggers on mysql.user table cause server crash Because they do not work, we do not allow creating triggers on tables within the 'mysql' schema. (They may be made to work and re-enabled at some later date, but not in 5.0 or 5.1.)
* Merge mysql.com:/opt/local/work/mysql-5.0-rootkonstantin@mysql.com2006-05-151-1/+1
|\ | | | | | | into mysql.com:/opt/local/work/mysql-5.0-runtime-merge
| * Bug#14635: Accept NEW.x as INOUT parameters to stored procedureskroki@mysql.com2006-05-121-1/+1
| | | | | | | | | | | | | | | | | | from within triggers Add support for passing NEW.x as INOUT and OUT parameters to stored procedures. Passing NEW.x as INOUT parameter requires SELECT and UPDATE privileges on that column, and passing it as OUT parameter requires only UPDATE privilege.
* | mergingholyfoot@mysql.com2006-05-031-0/+2
|\ \ | |/ |/|
| * bug #15860 (SPATIAL keys in INNODB)holyfoot@deer.(none)2006-04-121-0/+2
| |
* | Mergeevgen@moonbone.local2006-04-261-1/+1
|\ \
| * | fixed error message textbell@sanja.is.com.ua2006-04-261-1/+1
| | |
* | | Manually mergedevgen@moonbone.local2006-04-241-0/+2
|\ \ \ | |/ / |/| |
| * | Fixed bug#18739: non-standard HAVING extension was allowed in strict ANSI ↵evgen@moonbone.local2006-04-211-0/+2
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | sql mode. The SQL standard doesn't allow to use in HAVING clause fields that are not present in GROUP BY clause and not under any aggregate function in the HAVING clause. However, mysql allows using such fields. This extension assume that the non-grouping fields will have the same group-wise values. Otherwise, the result will be unpredictable. This extension allowed in strict MODE_ONLY_FULL_GROUP_BY sql mode results in misunderstanding of HAVING capabilities. The new error message ER_NON_GROUPING_FIELD_USED message is added. It says "non-grouping field '%-.64s' is used in %-.64s clause". This message is supposed to be used for reporting errors when some field is not found in the GROUP BY clause but have to be present there. Use cases for this message are this bug and when a field is present in a SELECT item list not under any aggregate function and there is GROUP BY clause present which doesn't mention that field. It renders the ER_WRONG_FIELD_WITH_GROUP error message obsolete as being more descriptive. The resolve_ref_in_select_and_group() function now reports the ER_NON_GROUPING_FIELD_FOUND error if the strict mode is set and the field for HAVING clause is found in the SELECT item list only.
* | The check for recursive view definitions added. (BUG#14308)bell@sanja.is.com.ua2006-04-131-0/+2
| |
* | Post-merge fixes. Add a new error message for max_prepared_stmt_countkonstantin@mysql.com2006-04-131-0/+2
|/ | | | limit.
* Merge mysql.com:/usr/home/bar/mysql-4.1.12076bar@mysql.com2006-04-032-9/+12
|\ | | | | | | into mysql.com:/usr/home/bar/mysql-5.0
| * Merge abarkov@bk-internal.mysql.com:/home/bk/mysql-4.1bar@mysql.com2006-04-032-9/+12
| |\ | | | | | | | | | into mysql.com:/usr/home/bar/mysql-4.1.12076
| | * latin1.xml:bar@mysql.com2005-11-072-9/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixing latin1 to cp1252, according to recent changes in ctype-latin1.c. Index.xml: Marking latin1_swedish_ci as "compiled" to avoid its generating into ctype-extra.c. ctype-extra.c: Bug#12076 --with-extra-charsets has no effect All supported dnamic charsets were generated from sql/share/charsets/*.xml under #ifdefs. Compiling is to be activated from "configure" by adding --with-extra-charsets. I'm not including auto-recreating of ctype-extra.c into build process for ease purposes.
* | | Merge msvensson@devsrv-b:/space/magnus/bug17261/my50-bug17261msvensson@neptunus.(none)2006-03-101-38/+38
|\ \ \ | | | | | | | | | | | | into neptunus.(none):/home/msvensson/mysql/bug11835/my50-bug11835
| * | | Bug#17261 Passing a variable from a stored procedure to UDF crashes mysqldmsvensson@devsrv-b.mysql.com2006-03-101-38/+38
| | | | | | | | | | | | | | | | | | | | - Update of test toolsand Makefiles to make it possible to test always test udf's as part of the mysql test suite
* | | | Merge bk-internal.mysql.com:/home/bk/mysql-5.0konstantin@mysql.com2006-02-221-0/+2
|\ \ \ \ | | | | | | | | | | | | | | | into mysql.com:/opt/local/work/mysql-5.0-runtime
| * | | | Fixed BUG#16896: Stored function: unused AGGREGATE-clause in CREATE FUNCTIONpem@mysql.com2006-02-091-0/+2
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Check if AGGREGATE was given with a stored (non-UDF) function, and return error in that case. Also made udf_example/udf_test work again, by adding a missing *_init() function. (_init() functions required unless --allow_suspicious_udfs is given to the server, since March 2005 - it seems udf_example wasn't updated at the time.)
* | | | WL#2645 (CHECK TABLE FOR UPGRADE)holyfoot@deer.(none)2006-02-171-0/+2
|/ / / | | | | | | | | | | | | necessary implementation in the server mysql_upgrade script added
* | | Merge mysql.com:/extern/mysql/bk/mysql-5.0pem@mysql.com2006-01-191-0/+2
|\ \ \ | | | | | | | | | | | | into mysql.com:/extern/mysql/work/bug15658/mysql-5.0
| * | | Fixing BUG#15658: Server crashes after creating function as empty stringpem@mysql.com2006-01-111-0/+2
| | | | | | | | | | | | | | | | Empty strings (and names with trailing spaces) should not be allowed.
* | | | Bug#15206: "Misleading message "No data to FETCH":konstantin@mysql.com2006-01-171-2/+2
|/ / / | | | | | | | | | reword the misleading message.
* | | errmsg.txt:paul@snake-hub.snake.net2005-12-201-1/+1
| | | | | | | | | | | | Fix typo.
* | | Merge mysql.com:/home/jimw/my/mysql-4.1-cleanjimw@mysql.com2005-12-121-9/+4
|\ \ \ | |/ / | | | | | | into mysql.com:/home/jimw/my/mysql-5.0-clean
| * | Bug#13421 problem with sorting turkishbar@mysql.com2005-12-071-9/+4
| | | | | | | | | | | | | | | | | | | | | latin5.xml: - Fixing order thee Turkish letters to conform Turkish rules. - All non-Turkish accented letters are mappend to their non-accented counterparts.
* | | Mergeserg@serg.mylan2005-12-061-5/+8
|\ \ \
| * | | german error messagesserg@serg.mylan2005-12-021-5/+8
| | | |
* | | | Merge mysql.com:/usr/local/bk/mysql-5.0pem@mysql.com2005-12-061-0/+2
|\ \ \ \ | |/ / / |/| | | | | | | into mysql.com:/usr/home/pem/bug14233/mysql-5.0
| * | | Fixed BUG#14233: Crash after tampering with the mysql.proc tablepem@mysql.com2005-11-251-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | Post-review version. Some minor review fixes, but also changed the way some errors are handled: Don't return specific parse errors; instead always use the more general "table corrupt" error (amended accordingly).
| * | | Merge mysql.com:/usr/local/bk/mysql-5.0pem@mysql.com2005-10-281-0/+2
| |\ \ \ | | | | | | | | | | | | | | | into mysql.com:/usr/home/pem/bug14233/mysql-5.0
| | * | | Fixed BUG#14233: Crash after tampering with the mysql.proc tablepem@mysql.com2005-10-261-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Added error checking for errors when attempting to use stored procedures after the mysql.proc table has been dropped, corrupted, or tampered with. Test cases were put in a separate file (sp-destruct.test).
* | | | | Don't use PATH_MAX for FN_REFLEN as this uses too much stack spacemonty@mysql.com2005-11-241-8/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Larger stack size neaded for open table on x86 64 bit Fix failing test cases Deleted symlink from bk
* | | | | mergedserg@serg.mylan2005-11-231-2/+4
|\ \ \ \ \
| * \ \ \ \ Merge sanja.is.com.ua:/home/bell/mysql/bk/work-bug7-5.0bell@sanja.is.com.ua2005-11-231-1/+3
| |\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | into sanja.is.com.ua:/home/bell/mysql/bk/work-merge-5.0
View Lorry Controller Status