An error occurred fetching the project authors.
- 06 Apr, 2009 1 commit
-
-
Satya B authored
-
- 02 Apr, 2009 6 commits
-
-
Satya B authored
-
Timothy Smith authored
-
Alexander Nozdrin authored
It was a test case problem: one 'reap' statement was forgotten.
-
Timothy Smith authored
-
Timothy Smith authored
-
Timothy Smith authored
-
- 01 Apr, 2009 16 commits
-
-
Ignacio Galarza authored
- Link against setargv.obj for wild-card expansion.
-
Ignacio Galarza authored
- Link against setargv.obj for wild-card expansion.
-
Bernt M. Johnsen authored
-
Bernt M. Johnsen authored
-
Bernt M. Johnsen authored
-
Bernt M. Johnsen authored
-
Daniel Fischer authored
-
Gleb Shchepa authored
-
Gleb Shchepa authored
Original commentary: Bug #37348: Crash in or immediately after JOIN::make_sum_func_list The optimizer pulls up aggregate functions which should be aggregated in an outer select. At some point it may substitute such a function for a field in the temporary table. The setup_copy_fields function doesn't take this into account and may overrun the copy_field buffer. Fixed by filtering out the fields referenced through the specialized reference for aggregates (Item_aggregate_ref). Added an assertion to make sure bugs that cause similar discrepancy don't go undetected.
-
Georgi Kodinov authored
-
Georgi Kodinov authored
-
Georgi Kodinov authored
-
Georgi Kodinov authored
-
Bernt M. Johnsen authored
-
Sergey Glukhov authored
The problem is that XML functions(items) do not reset null_value before their execution and further item excution may use null_value value of the previous result. The fix is to reset null_value.
-
Ramil Kalimullin authored
Problem: we don't prune a LESS THAN partition if MAXVALUE is given and given value is equal to a LESS THAN value. Fix: prune partitions in such cases.
-
- 31 Mar, 2009 6 commits
-
-
Ignacio Galarza authored
-
Ignacio Galarza authored
- Link against setargv.obj for wild-card expansion.
-
Daniel Fischer authored
Merged from 5.0 version of this patch: - Removed entire isamchk section. Support for ISAM tables was removed in 5.0. - Replaced key_buffer with key_buffer_size (correct spelling). - Removed skip-bdb, as BDB is no longer included in 5.0 and above. - Removed commented-out bdb_cache_size and bdb_max_lock for the same reason. - Removed commented-out innodb_log_arch_dir, deprecated in 5.0.24. - Removed myisam_max_extra_sort_file_size, deprecated in 5.0.6. - Removed log_long_format, deprecated in 4.1. - Replaced default_table_type with default-storage-engine. New in 5.1: - Replaced table_cache with table_open_cache. - Removed skip-federated, should have been in 5.0 only. - Replaced log_slow_queries with slow_query_log, deprecated in 5.1.29.
-
Staale Smedseng authored
mysql_setpermission is modified to honor the $db variable as suggested when doing a REVOKE ALL for menu option 7.
-
Daniel Fischer authored
- Removed entire isamchk section. Support for ISAM tables was removed in 5.0. - Replaced key_buffer with key_buffer_size (correct spelling). - Removed skip-bdb, as BDB is no longer included in 5.0 and above. - Removed commented-out bdb_cache_size and bdb_max_lock for the same reason. - Removed commented-out innodb_log_arch_dir, deprecated in 5.0.24. - Removed myisam_max_extra_sort_file_size, deprecated in 5.0.6. - Removed log_long_format, deprecated in 4.1. - Replaced default_table_type with default-storage-engine.
-
Bernt M. Johnsen authored
-
- 30 Mar, 2009 8 commits
-
-
Matthias Leich authored
-
Matthias Leich authored
-
Joerg Bruehe authored
more for completeness than for relevance. Also, update copyright notices.
-
Joerg Bruehe authored
-
Matthias Leich authored
-
Jonathan Perkin authored
-
Matthias Leich authored
+ disable the funcs_1.charset_collation_* tests which are broken because of bug 38346, 40209, 40545, 40618
-
Kristofer Pettersson authored
-
- 27 Mar, 2009 3 commits
-
-
Kristofer Pettersson authored
on 5.0 The server crashes on an assert in net_end_statement indicating that the Diagnostics area wasn't set properly during execution. This happened on a multi table DELETE operation using the IGNORE keyword. The keyword is suppose to allow for execution to continue on a best effort despite some non-fatal errors. Instead execution stopped and no client response was sent which would have led to a protocol error if it hadn't been for the assert. This patch corrects this issue by checking for the existence of an IGNORE option before setting an error state during row-by-row delete iteration.
-
Georgi Kodinov authored
-
Georgi Kodinov authored
-