- 23 Mar, 2009 5 commits
-
-
Georgi Kodinov authored
-
Tatiana A. Nurnberg authored
-
Tatiana A. Nurnberg authored
-
Tatiana A. Nurnberg authored
When asking what database is selected, client expected to *always* get an answer from the server. We now handle failure more gracefully. See comments in ticket for a discussion of what happens, and how things interlock.
-
Alfranio Correia authored
-
- 22 Mar, 2009 1 commit
-
-
Alfranio Correia authored
-
- 20 Mar, 2009 6 commits
-
-
Tatiana A. Nurnberg authored
-
Tatiana A. Nurnberg authored
-
Georgi Kodinov authored
-
Georgi Kodinov authored
-
Georgi Kodinov authored
fix for 29125).
-
Georgi Kodinov authored
-
- 19 Mar, 2009 28 commits
-
-
Chad MILLER authored
-
Tatiana A. Nurnberg authored
mysql-client used static buffer to concatenate server- version and version_comment. Sufficiently long comments could get cut off. This was harmless, but looked daft. Now using a dynamic buffer instead.
-
Sergey Petrunia authored
-
Ignacio Galarza authored
-
Chad MILLER authored
Antony Dovgal <tony @ daylessday.org> . SCA signed and faxed to tel:+1-408-715-2540. Patches tweaked by Chad.
-
Bernt M. Johnsen authored
-
Ignacio Galarza authored
-
Chad MILLER authored
continue to update it at make-time. One shouldn't need to run "make" on server source to get the stuff we say plugins should use.
-
Sergey Petrunia authored
-
Alexander Nozdrin authored
-
Magnus Svensson authored
-
Horst Hunger authored
-
Horst Hunger authored
-
Staale Smedseng authored
-
Staale Smedseng authored
functions Unknown timezone specifications are properly rejected by the server, but are copied into tz_storage before rejection, and hence is retained until end of server life. With sufficiently large bogus timezone specs, it is easy to exhaust system memory. Allocation of memory for a copy of the timezone name is delayed until after verification of validity, at the cost of a memcpy of the timezone info. This only happens once, future lookups will hit the cached structure.
-
Bernt M. Johnsen authored
-
Alexey Kopytov authored
-
Alexey Kopytov authored
-
Alexey Kopytov authored
-
Alexey Kopytov authored
-
Alexey Kopytov authored
for bug #41486. Session max_allowed_packet is read-only as of MySQL 5.1.31. In addition, the global variable now has no effect on the current session.
-
Sergey Glukhov authored
-
Satya B authored
-
Sergey Glukhov authored
-
Sergey Glukhov authored
fixed help message
-
Satya B authored
-
Sergey Glukhov authored
Don't throw an error after checking the first and the second arguments. Continue with checking the third and higher arguments and if some of them is stronger according to coercibility rules, then this argument's collation is set as result collation.
-
Satya B authored
When loading dump created by mysqldump tool an error is thrown saying storage engine for the table doesn't have an option. mysqldump tries to re-insert the data into the federated table which causes the error. Since the data is already available on the remote server, mysqldump shouldn't try to dump the data again for FEDERATED tables. As stated in the bug page, it can be considered similar to the MERGE ENGINE with "view only" nature. Fixed by adding the "FEDERATED ENGINE" to the exception list to ignore the data.
-