An error occurred fetching the project authors.
- 05 Jun, 2007 1 commit
-
-
svoj@mysql.com/april.(none) authored
SHOW CREATE TABLE fails Underlying table names, that merge engine fails to open were not reported. With this fix CHECK TABLE issued against merge table reports all underlying table names that it fails to open. Other statements are unaffected, that is underlying table names are not included into error message. This fix doesn't solve SHOW CREATE TABLE issue.
-
- 22 Feb, 2007 2 commits
-
-
msvensson@pilot.blaudden authored
-
msvensson@pilot.blaudden authored
- Add check of format specifiers in error message strings - Update error message text accordingly to be equal between all translations
-
- 15 Feb, 2007 1 commit
-
-
msvensson@pilot.mysql.com authored
-
- 14 Feb, 2007 2 commits
-
-
msvensson@pilot.mysql.com authored
Update error message text accordingly to be equal between all translations
-
msvensson@pilot.mysql.com authored
- Implement --secure-file-priv=<dir> option that limits "load_file", "LOAD DATA" and "SELECT .. INTO OUTFILE" to work with files in specified dir. - Use above option for mysqld in mysql-test-run.pl
-
- 13 Nov, 2006 1 commit
-
-
holyfoot/hf@mysql.com/deer.(none) authored
-
- 06 Oct, 2006 1 commit
-
-
svoj@mysql.com/april.(none) authored
-
- 28 Sep, 2006 1 commit
-
-
evgen@moonbone.local authored
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.
-
- 27 Sep, 2006 1 commit
-
-
svoj@mysql.com/april.(none) authored
-
- 30 Aug, 2006 1 commit
-
-
"strict mode: inserts autogenerated auto_increment value bigger than max" Strict mode should fail if autoincrement value is out of range
-
- 24 Aug, 2006 1 commit
-
-
anozdrin/alik@alik. authored
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.
-
- 23 Aug, 2006 1 commit
-
-
anozdrin/alik@alik. authored
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.
-
- 02 Aug, 2006 1 commit
-
-
svoj@may.pils.ru authored
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.
-
- 15 Jul, 2006 1 commit
-
-
evgen@moonbone.local authored
Fixed bug#10977: No warning issued if a column name is truncated New warning message is added.
-
- 28 Jun, 2006 1 commit
-
-
jimw@mysql.com authored
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.)
-
- 20 Jun, 2006 1 commit
-
-
holyfoot@deer.(none) authored
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
-
- 12 May, 2006 1 commit
-
-
kroki@mysql.com authored
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.
-
- 26 Apr, 2006 1 commit
-
-
bell@sanja.is.com.ua authored
-
- 20 Apr, 2006 1 commit
-
-
evgen@moonbone.local authored
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.
-
- 13 Apr, 2006 1 commit
-
-
bell@sanja.is.com.ua authored
-
- 12 Apr, 2006 2 commits
-
-
konstantin@mysql.com authored
limit.
-
holyfoot@deer.(none) authored
-
- 10 Mar, 2006 1 commit
-
-
msvensson@devsrv-b.mysql.com authored
- Update of test toolsand Makefiles to make it possible to test always test udf's as part of the mysql test suite
-
- 17 Feb, 2006 1 commit
-
-
holyfoot@deer.(none) authored
necessary implementation in the server mysql_upgrade script added
-
- 09 Feb, 2006 1 commit
-
-
pem@mysql.com authored
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.)
-
- 17 Jan, 2006 1 commit
-
-
konstantin@mysql.com authored
reword the misleading message.
-
- 11 Jan, 2006 1 commit
-
-
pem@mysql.com authored
Empty strings (and names with trailing spaces) should not be allowed.
-
- 20 Dec, 2005 1 commit
-
-
paul@snake-hub.snake.net authored
Fix typo.
-
- 02 Dec, 2005 1 commit
-
-
serg@serg.mylan authored
-
- 25 Nov, 2005 1 commit
-
-
pem@mysql.com authored
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).
-
- 24 Nov, 2005 1 commit
-
-
monty@mysql.com authored
Larger stack size neaded for open table on x86 64 bit Fix failing test cases Deleted symlink from bk
-
- 22 Nov, 2005 2 commits
-
-
bell@sanja.is.com.ua authored
-
serg@serg.mylan authored
-
- 20 Nov, 2005 1 commit
-
-
bell@sanja.is.com.ua authored
Bad examples of usage of a string with its length fixed. The incorrect length in the trigger file configuration descriptor fixed (BUG#14090). A hook for unknown keys added to the parser to support old .TRG files.
-
- 17 Nov, 2005 1 commit
-
-
serg@serg.mylan authored
-
- 10 Nov, 2005 2 commits
-
-
anozdrin@mysql.com authored
checks on trigger activation)
-
guilhem@mysql.com authored
Indeed now that stored procedures CALL is not binlogged, but instead the invoked substatements are, the restrictions applied by log-bin-trust-routine-creators=0 are superfluous for procedures. They still need to apply to functions where function calls are written to the binlog (for example as "DO myfunc(3)"). We rename the variable to log-bin-trust-function-creators but allow the old name until some future version (and issue a warning if old name is used).
-
- 06 Nov, 2005 1 commit
-
-
igor@rurik.mysql.com authored
-
- 03 Nov, 2005 1 commit
-
-
igor@rurik.mysql.com authored
-