An error occurred fetching the project authors.
- 27 Jun, 2006 1 commit
-
-
svoj@may.pils.ru authored
Produce a warning if DATA/INDEX DIRECTORY is specified in ALTER TABLE statement. Ignoring of these options is documented in the symbolic links section of the manual.
-
- 19 Jun, 2006 1 commit
-
-
holyfoot@deer.(none) authored
there was two problems about charsets in embedded server 1. mysys/charset.c - defined there default_charset_info variable is modified by both server and client code (particularly when --default-charset option is handled) In embedded server we get two codelines modifying one variable. I created separate default_client_charset_info for client code 2. mysql->charset and mysql->options.charset initialization isn't properly done for embedded server - necessary calls added
-
- 01 Jun, 2006 1 commit
-
-
holyfoot@deer.(none) authored
There actually was 3 different problems - hash_user_connections wasn't cleaned one strdupped database name wasn't freed and stmt->mem_root wasn't cleaned as it was replased with mysql->field_alloc for result For the last one - i made the library using stmt's fields to store result if it's the case.
-
- 28 May, 2006 1 commit
-
-
evgen@moonbone.local authored
In multi-table delete a table for delete can't be used for selecting in subselects. Appropriate error was raised but wasn't checked which leads to a crash at the execution phase. The mysql_execute_command() now checks for errors before executing select for multi-delete.
-
- 26 Apr, 2006 1 commit
-
-
serg@sergbook.mysql.com authored
-
- 25 Apr, 2006 2 commits
-
-
serg@sergbook.mysql.com authored
(based on the fact that packet is ALWAYS \0 terminated, see my_net_read)
-
serg@sergbook.mysql.com authored
(reported by Stefano Di Paola)
-
- 21 Apr, 2006 1 commit
-
-
igor@rurik.mysql.com authored
The bug caused wrong result sets for union constructs of the form (SELECT ... ORDER BY order_list1 [LIMIT n]) ORDER BY order_list2. For such queries order lists were concatenated and limit clause was completely neglected.
-
- 21 Feb, 2006 1 commit
-
-
konstantin@mysql.com authored
column is increasing when table is recreated with PS/SP": make use of create_field::char_length more consistent in the code. Reinit create_field::length from create_field::char_length for every execution of a prepared statement (actually fixes the bug).
-
- 26 Jan, 2006 1 commit
-
-
aelkin@mysql.com authored
-
- 07 Dec, 2005 1 commit
-
-
ingo@mysql.com authored
Problem #1: INSERT...SELECT, Version for 4.1. INSERT ... SELECT with the same table on both sides (hidden below a MERGE table) does now work by buffering the select result. The duplicate detection works now after open_and_lock_tables() on the locks. I did not find a test case that failed without the change in sql_update.cc. I made the change anyway as it should in theory fix a possible MERGE table problem with multi-table update.
-
- 04 Dec, 2005 1 commit
-
-
- 29 Nov, 2005 1 commit
-
-
ingo@mysql.com authored
Problem #1: INSERT...SELECT INSERT ... SELECT with the same table on both sides (hidden below a MERGE table) does now work by buffering the select result. The duplicate detection works now after open_and_lock_tables() on the locks. I did not find a test case that failed without the change in sql_update.cc. I made the change anyway as it should in theory fix a possible MERGE table problem with multi-table update.
-
- 10 Oct, 2005 2 commits
-
-
lars@mysql.com authored
-
lars@mysql.com authored
-
- 08 Oct, 2005 1 commit
-
-
serg@serg.mylan authored
don't allow STOP SLAVE if global read lock is in taken
-
- 19 Sep, 2005 1 commit
-
-
jonas@perch.ndb.mysql.com authored
that dump free list allocation per connection
-
- 14 Sep, 2005 1 commit
-
-
sasha@asksasha.com authored
present): the problem originally was that the tables in auxilliary_tables did not have the correct real_name, which caused problems in the second call to tables_ok(). The fix corrects the real_name problem, and also sets the updating flag properly, which makes the second call to tables_ok() unnecessary.
-
- 10 Sep, 2005 1 commit
-
-
lars@mysql.com authored
-
- 05 Sep, 2005 1 commit
-
-
bar@mysql.com authored
bug#9948 changed client-charset behavior in 4.1.x libmysql, which issue BC prob after review fixes
-
- 03 Sep, 2005 1 commit
-
-
eric@mysql.com authored
Handle systems like default FC4 where 127.0.0.1 doesn't always map to 'localhost' first. (Bug #11822)
-
- 01 Sep, 2005 2 commits
-
-
lars@mysql.com authored
-
dlenev@mysql.com authored
multi-threaded environment". To avoid deadlocks between several simultaneously run account management commands (particularly between FLUSH PRIVILEGES/SET PASSWORD and GRANT commands) we should always take table and internal locks during their execution in the same order. In other words we should first open and lock privilege tables and only then obtain acl_cache::lock/LOCK_grant locks.
-
- 31 Aug, 2005 2 commits
-
-
lars@mysql.com authored
rpl_replicate_do.result: New test case sql_parse.cc: All SET statements should be executed by slave thd rpl_replicate_do.test: New test case
-
bar@mysql.com authored
bug#9948 changed client-charset behavior in 4.1.x libmysql, which issue BC prob sql_parse.cc: mysqld.cc: Added --skip-client-character-set-handshake. When this option is activated, client side character set (which is sent in handshake) is ignored, and server side default-character-set value is used for character_set_client and character_set_results, thus reprodicing 4.0 behaviour.
-
- 29 Aug, 2005 1 commit
-
-
ingo@mysql.com authored
Supplied the default database name for ALTER TABLE ... RENAME for the new table instead of the old tables db like we do for other ALTERs.
-
- 15 Aug, 2005 1 commit
-
-
lars@mysql.com authored
-
- 13 Aug, 2005 1 commit
-
-
tsmith@.mysql.com authored
Don't skip SET command even if --replicate-wild* says to. E.g., SET ONE_SHOT TIME_ZONE = 'XYZ' should be executed (BUG #12542)
-
- 08 Aug, 2005 1 commit
-
-
monty@mysql.com authored
- Fixed some error condtion when handling dates with 'T' - Added extra test for bug #11867 (Wrong result with "... WHERE ROW( a, b ) IN ( SELECT DISTINCT a, b WHERE ...)" to show it's not yet fixed - Safety fixes and cleanups
-
- 07 Aug, 2005 1 commit
-
-
acurtis@xiphis.org authored
"INSERT .. SELECT ... ON DUPLICATE KEY UPDATE fails" Ensure that check_insert_fields() is only called once when doing an INSERT..SELECT
-
- 05 Aug, 2005 1 commit
-
-
ingo@mysql.com authored
Added a check before taking a global read lock if the own thread has a write locked table.
-
- 25 Jul, 2005 1 commit
-
-
jimw@mysql.com authored
was used. (Bug #10724)
-
- 23 Jul, 2005 1 commit
-
-
hf@deer.(none) authored
-
- 13 Jul, 2005 1 commit
-
-
konstantin@mysql.com authored
data": remove the fix for another bug (8807) that added OUTER_REF_TABLE_BIT to all subqueries that used a placeholder to prevent their evaluation at prepare. As this bit hanged in Item_subselect::used_tables_cache for ever, a constant subquery with a placeholder was never evaluated as such, which caused wrong choice of the execution plan for the statement. - to fix Bug#8807 backport a better fix from 5.0 - post-review fixes.
-
- 28 Jun, 2005 2 commits
-
-
monty@mysql.com authored
This fixed a failure of insert_update.test on some platforms
-
jimw@mysql.com authored
max_user_connections is also set. (Bug #9947)
-
- 27 Jun, 2005 2 commits
-
-
monty@mishka.local authored
Fixes while reviewing new pushed code NULL as argument to encrypt/decrypt should return NULL without a warning
-
monty@mishka.local authored
#9728 'Decreased functionality in "on duplicate key update #8147 'a column proclaimed ambigous in INSERT ... SELECT .. ON DUPLICATE' This ensures fields are uniquely qualified and also that one can't update other tables in the ON DUPLICATE KEY UPDATE part
-
- 23 Jun, 2005 1 commit
-
-
evgen@moonbone.local authored
Fix for fix for bug #9728 Error caused server hang on prepared insert ... select
-
- 22 Jun, 2005 1 commit
-
-
evgen@moonbone.local authored
Remove changes made by bug fix #8147. They strips list of insert_table_list to only insert table, which results in error reported in bug #9728. Added flag to Item to resolve ambigous fields reported in bug #8147.
-