- 03 Jul, 2007 2 commits
-
-
antony@ppcg5.local authored
fixes test breakage on sles10-ia64-a which omits charset.
-
antony@ppcg5.local authored
-
- 02 Jul, 2007 3 commits
-
-
svoj@june.mysql.com authored
into mysql.com:/home/svoj/devel/mysql/BUG29299/mysql-5.1-engines
-
svoj@june.mysql.com authored
into mysql.com:/home/svoj/devel/mysql/BUG29299/mysql-5.0-engines
-
antony@anubis.xiphis.org authored
into anubis.xiphis.org:/usr/home/antony/work/mysql-5.1-merge
-
- 01 Jul, 2007 5 commits
-
-
igor@olga.mysql.com authored
-
istruewing@synthia.local authored
Fixed warnings Fixed error numbers
-
igor@olga.mysql.com authored
-
igor@olga.mysql.com authored
-
igor@olga.mysql.com authored
into olga.mysql.com:/home/igor/dev-opt/mysql-5.1-opt
-
- 30 Jun, 2007 5 commits
-
-
igor@olga.mysql.com authored
into olga.mysql.com:/home/igor/mysql-5.0-opt
-
istruewing@synthia.local authored
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/autopush/B29157-5.1-opt
-
istruewing@synthia.local authored
into synthia.local:/home/mydev/mysql-5.1-axmrg
-
istruewing@synthia.local authored
into synthia.local:/home/mydev/mysql-5.0-axmrg
-
- 29 Jun, 2007 21 commits
-
-
istruewing@synthia.local authored
into synthia.local:/home/mydev/mysql-5.1-axmrg
-
istruewing@synthia.local authored
into synthia.local:/home/mydev/mysql-5.1-axmrg
-
istruewing@synthia.local authored
into synthia.local:/home/mydev/mysql-5.1-axmrg
-
antony@anubis.xiphis.org authored
into anubis.xiphis.org:/usr/home/antony/work/5.0-engines-merge
-
antony@ppcg5.local authored
pointer into a BOOL type.
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/5.0-opt
-
gshchepa/uchum@gleb.loc authored
When a UNION statement forced conversion of an UTF8 charset value to a binary charset value, the byte length of the result values was truncated to the CHAR_LENGTH of the original UTF8 value.
-
antony@anubis.xiphis.org authored
into anubis.xiphis.org:/usr/home/antony/work/5.0-engines-merge
-
antony@anubis.xiphis.org authored
into anubis.xiphis.org:/usr/home/antony/work/p2-bug25513.5
-
antony@ppcg5.local authored
-
istruewing@synthia.local authored
into synthia.local:/home/mydev/mysql-5.0-axmrg
-
istruewing@synthia.local authored
into synthia.local:/home/mydev/mysql-5.0-axmrg
-
istruewing@synthia.local authored
into synthia.local:/home/mydev/mysql-5.1-axmrg
-
evgen@moonbone.local authored
into moonbone.local:/mnt/gentoo64/work/29261-bug-5.0-opt-mysql
-
evgen@moonbone.local authored
spaces. When the my_strnncollsp_simple function compares two strings and one is a prefix of another then this function compares characters in the rest of longer key with the space character to find whether the longer key is greater or less. But the sort order of the collation isn't used in this comparison. This may lead to a wrong comparison result, wrongly created index or wrong order of the result set of a query with the ORDER BY clause. Now the my_strnncollsp_simple function uses collation sort order to compare the characters in the rest of longer key with the space character.
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/autopush/B27333-gcov-5.0-opt
-
gkodinov/kgeorge@magare.gmz authored
query / no aggregate of subquery The optimizer counts the aggregate functions that appear as top level expressions (in all_fields) in the current subquery. Later it makes a list of these that it uses to actually execute the aggregates in end_send_group(). That count is used in several places as a flag whether there are aggregates functions. While collecting the above info it must not consider aggregates that are not aggregated in the current context. It must treat them as normal expressions instead. Not doing that leads to incorrect data about the query, e.g. running a query that actually has no aggregate functions as if it has some (and hence is expected to return only one row). Fixed by ignoring the aggregates that are not aggregated in the current context. One other smaller omission discovered and fixed in the process : the place of aggregation was not calculated for user defined functions. Fixed by calling Item_sum::init_sum_func_check() and Item_sum::check_sum_func() as it's done for the rest of the aggregate functions.
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/29247/my51-29247
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/29247/my50-29247
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/29247/my51-29247
-
holyfoot/hf@hfmain.(none) authored
into mysql.com:/home/hf/work/29247/my51-29247
-
- 28 Jun, 2007 4 commits
-
-
antony@ppcg5.local authored
"Federared Transactions Failure" Bug occurs when the user performs an operation which inserts more than one row into the federated table and the federated table references a remote table stored within a transactional storage engine. When the insert operation for any one row in the statement fails due to constraint violation, the federated engine is unable to perform statement rollback and so the remote table contains a partial commit. The user would expect a statement to perform the same so a statement rollback is expected. This bug was fixed by implementing bulk-insert handling into the federated storage engine. This will relieve the bug for most common situations by enabling the generation of a multi-row insert into the remote table and thus permitting the remote table to perform statement rollback when neccessary. The multi-row insert is limited to the maximum packet size between servers and should the size overflow, more than one insert statement will be sent and this bug will reappear. Multi-row insert is disabled when an "INSERT...ON DUPLICATE KEY UPDATE" is being performed. The bulk-insert handling will offer a significant performance boost when inserting a large number of small rows. This patch builds on Bug29019 and Bug25511
-
antony@ppcg5.local authored
"Federated INSERT failures" Federated does not correctly handle "INSERT...ON DUPLICATE KEY UPDATE" However, implementing such support is not reasonably possible without increasing complexity of the storage engine: checking that constraints on remote server match local server and parsing error messages. This patch causes 'ON DUPLICATE KEY' to fail with ER_DUP_KEY message if a conflict occurs and not to fail silently.
-
gkodinov/kgeorge@magare.gmz authored
Sometimes the number of really updated rows (with changed column values) cannot be determined at the server level alone (e.g. if the storage engine does not return enough column values to verify that). So the only dependable way in such cases is to let the storage engine return that information if possible. Fixed the bug at server level by providing a way for the storage engine to return information about wether it actually updated the row or the old and the new column values are the same. It can do that by returning HA_ERR_RECORD_IS_THE_SAME in ha_update_row(). Note that each storage engine may choose not to try to return this status code, so this behaviour remains storage engine specific.
-
gkodinov/kgeorge@magare.gmz authored
into magare.gmz:/home/kgeorge/mysql/autopush/B26564-5.1-opt
-