An error occurred fetching the project authors.
- 27 Nov, 2006 1 commit
-
-
monty@mysql.com/nosik.monty.fi authored
Initialize key_part->type on open. This caused key_copy() to fail for bit_fields. (key_copy is used in HANDLER and opt_range)
-
- 20 Nov, 2006 1 commit
-
-
monty@mysql.com/nosik.monty.fi authored
(Mostly in DBUG_PRINT() and unused arguments) Fixed bug in query cache when used with traceing (--with-debug) Fixed memory leak in mysqldump Removed warnings from mysqltest scripts (replaced -- with #)
-
- 30 Oct, 2006 2 commits
-
-
kroki/tomash@moonlight.intranet authored
If the user has specified --max-connections=N or --table-open-cache=M options to the server, a warning could be given that some values were recalculated, and table-open-cache could be assigned greater value. Note that both warning and increase of table-open-cache were totally harmless. This patch fixes recalculation code to ensure that table-open-cache will be never increased automatically and that a warning will be given only if some values had to be decreased due to operating system limits. No test case is provided because we neither can't predict nor control operating system limits for maximal number of open files.
-
msvensson@shellback.(none) authored
It's not possible to flush the global status variables in 5.0 Update test case so it works by recording the value of handle_rollback before and compare it to the value after
-
- 15 Sep, 2006 1 commit
-
-
msvensson@shellback.(none) authored
-
- 06 Sep, 2006 1 commit
-
-
tsmith@maint1.mysql.com authored
Fix OPT_MYISAM_STATS_METHOD case, where the NULLS_EQUAL and NULLS_NOT_EQUAL methods were mixed up
-
- 21 Aug, 2006 1 commit
-
-
rburnett@production.mysql.com authored
var was already defined so had to remove extra one
-
- 17 Aug, 2006 1 commit
-
-
jimw@rama.(none) authored
Fix when __attribute__() is stubbed out, add ATTRIBUTE_FORMAT() for specifying __attribute__((format(...))) safely, make more use of the format attribute, and fix some of the warnings that this turns up (plus a bonus unrelated one).
-
- 11 Aug, 2006 1 commit
-
-
didn't work as expected: collation_server was set not to xxx, but to the default collation of character set "yyy". With different argument order it worked as expected: mysqld --character-set-server=yyy --collation-server=yyy Fix: initializate default_collation_name to 0 when processing --character-set-server only if --collation-server has not been specified in command line.
-
- 04 Aug, 2006 1 commit
-
-
rburnett@production.mysql.com authored
set properly. This patch should fix that. mysqld.cc: Call test_if_case_insensitive in all cases so lower_case_file_system always gets set
-
- 03 Aug, 2006 3 commits
-
-
iggy@rolltop.ignatz42.dyndns.org authored
-
msvensson@neptunus.(none) authored
- Backport patch from 5.0
-
malff/marcsql@weblab.(none) authored
Before this fix, - a runtime error in a statement in a stored procedure with no error handlers was properly detected (as expected) - a runtime error in a statement with an error handler inherited from a non local runtime context (i.e., proc a with a handler, calling proc b) was properly detected (as expected) - a runtime error in a statement with a *local* error handler was executed as follows : a) the statement would succeed, regardless of the error condition, (bug) b) the error handler would be called (as expected). The root cause is that functions like my_messqge_sql would "forget" to set the thread flag thd->net.report_error to 1, because of the check involving sp_rcontext::found_handler_here(). Failure to set this flag would cause, later in the call stack, in Item_func::fix_fields() at line 190, the code to return FALSE and consider that executing the statement was successful. With this fix : - error handling code, that was duplicated in different places in the code, is now implemented in sp_rcontext::handle_error(), - handle_error() correctly sets thd->net.report_error when a handler is present, regardless of the handler location (local, or in the call stack). A test case, bug8153_subselect, has been written to demonstrate the change of behavior before and after the fix. Another test case, bug8153_function_a, as also been writen. This test has the same behavior before and after the fix. This test has been written to demonstrate that the previous expected result of procedure bug18787, was incorrect, since select no_such_function() should fail and therefore not produce a result. The incorrect result for bug18787 has the same root cause as Bug#8153, and the expected result has been adjusted.
-
- 31 Jul, 2006 1 commit
-
-
msvensson@neptunus.(none) authored
By default lowercase_table_names are 1 on windows, and that makes the initialization of lower_case_filesystem variable to be skipped. Add an else bracnh that does the initialization.
-
- 21 Jul, 2006 1 commit
-
-
tsmith@maint1.mysql.com authored
-
- 20 Jul, 2006 1 commit
-
-
tsmith/tim@siva.hindu.god authored
- Adapt it to work with the handlerton class
-
- 14 Jul, 2006 1 commit
-
-
to avoid the potential security problem. (see bug #15195: Security Breach with MERGE table)
-
- 23 Jun, 2006 1 commit
-
-
bar@mysql.com authored
Problem: mysqld --collation-server=xxx --character-set-server=yyy didn't work as expected: collation_server was set not to xxx, but to the default collation of character set "yyy". With different argument order it worked as expected: mysqld --character-set-server=yyy --collation-server=yyy Fix: initializate default_collation_name to 0 when processing --character-set-server only if --collation-server has not been specified in command line.
-
- 21 Jun, 2006 1 commit
-
-
jani@ua141d10.elisa.omakaista.fi authored
-
- 20 Jun, 2006 1 commit
-
-
jani@ua141d10.elisa.omakaista.fi authored
-
- 07 Jun, 2006 1 commit
-
-
svoj@may.pils.ru authored
read buffer Setting read buffer to values greater than SSIZE_MAX results in unexpected behavior. According to read(2) manual: If count is greater than SSIZE_MAX, the result is unspecified. Set upper limit for read_buffer_size and read_rnd_buffer_size to SSIZE_MAX.
-
- 31 May, 2006 1 commit
-
-
tnurnberg@mysql.com authored
Two threads both try a shutdown sequence which creates a race to the de-init/free of certain resources. This exists in similar form in the client as 17926: "mysql.exe crashes when ctrl-c is pressed in windows."
-
- 24 May, 2006 1 commit
-
-
monty@mysql.com authored
Replaced COND_refresh with COND_global_read_lock becasue of a bug in NTPL threads when using different mutexes as arguments to pthread_cond_wait() The original code caused a hang in FLUSH TABLES WITH READ LOCK in some circumstances because pthread_cond_broadcast() was not delivered to other threads. This fixes: Bug#16986: Deadlock condition with MyISAM tables Bug#20048: FLUSH TABLES WITH READ LOCK causes a deadlock
-
- 23 May, 2006 1 commit
-
-
msvensson@neptunus.(none) authored
-
- 19 May, 2006 2 commits
-
-
iggy@mysql.com authored
-
msvensson@neptunus.(none) authored
- A segfault occured when the function 'kill_server' called 'my_sigset' with signal number 0. 'my_sigset' is a macro which uses 'sigaction' to install the signal handler with an invalid signal number will on most platforms return EINVAL but yields a segfauilt on IRIX 6.5 - The server crash was detected by mysqld_safe and it was restarted although a shutdown was requested. - Semantics of kill_server(0) is not known, leaving it intact
-
- 15 May, 2006 1 commit
-
-
knielsen@mysql.com authored
-
- 08 May, 2006 2 commits
-
-
jimw@mysql.com authored
Bug #19606: ssl variables are not displayed in show variables Bug #19616: log_queries_not_using_indexes is not listed in show variables Make basedir, datadir, tmpdir, log_queries_not_using_indexes, ssl_ca, ssl_capath, ssl_cert, ssl_cipher, and ssl_key all available both from SHOW VARIABLES and as @@variables. As a side-effect of this change, log_queries_not_using_indexes can be changed at runtime (but only globally, not per-connection).
-
msvensson@neptunus.(none) authored
Add function 'vio_end' that will cleanup resources allocated by vio and the components it uses.
-
- 28 Apr, 2006 1 commit
-
-
elliot@mysql.com authored
Removed duplication (not a user-visible change)
-
- 13 Apr, 2006 3 commits
-
-
konstantin@mysql.com authored
-
grog@mysql.com[grog] authored
-
grog@mysql.com[grog] authored
-
- 12 Apr, 2006 1 commit
-
-
msvensson@neptunus.(none) authored
- Add variable "have_dynamic_loading" and use it to check if the udf test should be run.
-
- 10 Apr, 2006 1 commit
-
-
aivanov@mysql.com authored
Applied changes due Heikki Tuuri.
-
- 07 Apr, 2006 2 commits
-
-
konstantin@mysql.com authored
too many open statements". The patch adds a new global variable @@max_prepared_stmt_count. This variable limits the total number of prepared statements in the server. The default value of @@max_prepared_stmt_count is 16382. 16382 small statements (a select against 3 tables with GROUP, ORDER and LIMIT) consume 100MB of RAM. Once this limit has been reached, the server will refuse to prepare a new statement and return ER_UNKNOWN_ERROR (unfortunately, we can't add new errors to 4.1 without breaking 5.0). The limit is changeable after startup and can accept any value from 0 to 1 million. In case the new value of the limit is less than the current statement count, no new statements can be added, while the old still can be used. Additionally, the current count of prepared statements is now available through a global read-only variable @@prepared_stmt_count.
-
kroki@mysql.com authored
After FLUSH STATUS max_used_connections was reset to 0, and haven't been updated while cached threads were reused, until the moment a new thread was created. The first suggested fix from original bug report was implemented: a) On flushing the status, set max_used_connections to threads_connected, not to 0. b) Check if it is necessary to increment max_used_connections when taking a thread from the cache as well as when creating new threads
-
- 16 Mar, 2006 1 commit
-
-
acurtis@xiphis.org authored
¨MySQL server crashes if you try to access to InnoDB table¨ crash caused by schizophrenic mysqld - 2 memory locations for logically same function with conflicting values. Fixed by backporting from 5.1 changes to have_xyz_db declarations.
-
- 14 Mar, 2006 1 commit
-
-
paul@kite-hub.kitebird.com authored
Backport option description change from 5.1 to 5.0.
-
- 10 Mar, 2006 1 commit
-
-
msvensson@neptunus.(none) authored
Remove duplicate code Merge common functions Enforce MySQL coding standard
-