| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
- Removed files specific to compiling on OS/2
- Removed files specific to SCO Unix packaging
- Removed "libmysqld/copyright", text is included in documentation
- Removed LaTeX headers for NDB Doxygen documentation
- Removed obsolete NDB files
- Removed "mkisofs" binaries
- Removed the "cvs2cl.pl" script
- Changed a few GPL texts to use "program" instead of "library"
|
|
|
|
|
|
|
|
|
|
|
|
| |
32bit builds with the --enable-assembler flag (enabled by default)
fail with an error message: undefined reference to `strmov_overlapp'.
Since the fix for bug 48866 we use a home-grown strmov function
instead of the ctpcpy function, but the source file for this
function was missed in the Makefile.am.
The strings/Makefile.am file has been modified to include strmov.c
file into ASSEMBLER_x86 and ASSEMBLER_sparc32 sections.
|
|
|
|
|
|
|
|
| |
strmov() is not guaranteed to work correctly on overlapping
source and destination buffers. On some OSes it may work,
but Fedora 12 has a stpcpy() that's not working correctly
on overlapping buffers.
Fixed to use the overlap-safe version of strmov instead.
Re-vitalized the overlap-safe version of strmov.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
with gcc 4.3.2
This patch fixes a number of GCC warnings about variables used
before initialized. A new macro UNINIT_VAR() is introduced for
use in the variable declaration, and LINT_INIT() usage will be
gradually deprecated. (A workaround is used for g++, pending a
patch for a g++ bug.)
GCC warnings for unused results (attribute warn_unused_result)
for a number of system calls (present at least in later
Ubuntus, where the usual void cast trick doesn't work) are
also fixed.
|
| |
|
| |
|
|
|
| |
Fixed the 5.0-bugteam MacOSX warnings.
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
The reference manual has instructions for adding new character
sets, and refers to the string/CHARSET_INFO.txt file. This file
is currently not present in the distribution.
Modify the build to include this file in the distribution.
|
|/
|
|
|
| |
- Remove bothersome warning messages. This change focuses on the warnings
that are covered by the ignore file: support-files/compiler_warnings.supp.
- Strings are guaranteed to be max uint in length
|
|
|
|
|
|
|
|
| |
The MONTHNAME/DAYNAME functions
returns binary string, so the LOWER/UPPER functions
are not effective on the result of MONTHNAME/DAYNAME call.
Character set of the MONTHNAME/DAYNAME function
result has been changed to connection character set.
|
|
|
|
|
|
|
|
| |
When the fractional part in a multiplication of DECIMALs
overflowed, we truncated the first operand rather than the
longest. Now truncating least significant places instead
for more precise multiplications.
(Queuing at demand of Trudy/Davi.)
|
|
|
|
|
| |
Thanks to Paul for preparing the up-to-date files
reflecting 4.1 changes.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Grouping or ordering of long values in not indexed BLOB/TEXT columns
with GBK or BIG5 charsets crashes the server.
MySQL server uses sorting (the filesort procedure) in the temporary
table to evaluate the GROUP BY clause in case of lack of suitable index.
That procedure takes into account only first @max_sort_length bytes
(system variable, usually 1024) of TEXT/BLOB sorting key string.
The my_strnxfrm_gbk and my_strnxfrm_big5 fill temporary keys
with data of whole blob length instead of @max_sort_length bytes
length. That buffer overrun has been fixed.
|
|\
| |
| |
| | |
into mysql.com:/home/bar/mysql-work/mysql-5.0.b32510v2
|
| |
| |
| |
| |
| |
| |
| |
| | |
Problem: some collation handlers called incorrect version
of my_like_range_xxx(), which led to wrong min_str and max_str,
so like range optimizer threw away good records.
Fix: changing the wrong handlers to call proper version of
my_like_range_xxx().
|
|\ \
| | |
| | |
| | | |
into linux-st28.site:/home/martin/mysql/src/bug33143/my50-bug33143-again-pushee
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The ROUND(X, D) function would change the Item::decimals field during
execution to achieve the effect of a dynamic number of decimal digits.
This caused a series of bugs:
Bug #30617:Round() function not working under some circumstances in InnoDB
Bug #33402:ROUND with decimal and non-constant cannot round to 0 decimal places
Bug #30889:filesort and order by with float/numeric crashes server
Fixed by never changing the number of shown digits for DECIMAL when
used with a nonconstant number of decimal digits.
|
|\ \ \
| | | |
| | | |
| | | | |
into mysql.com:/misc/mysql/31752_/50-31752_
|
| |\ \ \
| | |/ /
| |/| |
| | | | |
into mysql.com:/misc/mysql/31752_/50-31752_
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
strmake() calls are easy to get wrong. Add checks in extra
debug mode to identify possible exploits.
Remove some dead code.
Remove some off-by-one errors identified with new checks.
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
into mysql.com:/home/gluh/MySQL/Merge/5.0-opt
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Default values of variables were not subject to upper/lower bounds
and step, while setting variables was. Bounds and step are also
applied to defaults now; defaults are corrected quietly, values
given by the user are corrected, and a correction-warning is thrown
as needed. Lastly, very large values could wrap around, starting
from 0 again. They are bounded at the maximum value for the
respective data-type now if no lower maximum is specified in the
variable's definition.
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | | |
into stella.local:/home2/mydev/mysql-5.0-axmrg
|
| |\ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | | |
into mysql.com:/home/ram/work/b32726/b32726.5.0
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
- fix for #31070 (missed during merging) applied for cp932 charset.
- tests/results adjusted.
|
|\ \ \ \ \ \ \
| |/ / / / / /
| | | | | | |
| | | | | | | |
into ramayana.hindu.god:/home/tsmith/m/bk/maint/50
|
| |\ \ \ \ \ \
| | |/ / / / /
| |/| | | | /
| | | |_|_|/
| | |/| | | |
into dl145h.mysql.com:/data0/mkindahl/mysql-5.0-rpl-merge
|
| | |\ \ \ \
| | | |/ / /
| | |/| | |
| | | | | | |
into mysql.com:/home/bar/mysql-work/mysql-5.0-rpl-merge
|
| | | |\ \ \
| | | | | | |
| | | | | | |
| | | | | | | |
into mysql.com:/home/bar/mysql-work/mysql-5.0-rpl-mr
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Problem: some valid euc-kr characters were rejected because
condition checking multi-byte tail didn't allow
multi-byte characters having the second byte in the ranges
[0x41..0x5A] and [0x61..0x7A].
Fix: allow these byte ranges for mb tails
|
| |\ \ \ \ \ \
| | |/ / / / /
| |/| | | | |
| | | | | | | |
into mysql.com:/home/kent/bk/bug30069/mysql-5.0-build
|
| | | |_|_|/
| | |/| | |
| | | | | |
| | | | | | |
Avoid undefined value when negating (bug#30069)
|
| |\ \ \ \ \
| | |_|/ / /
| |/| | | /
| | | |_|/
| | |/| | |
into mysql.com:/home/gluh/MySQL/Merge/5.0-opt
|
| | | |/
| | |/|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
when a divisor is less than 1 and its fractional part is very long.
For example:
1 % .123456789123456789123456789123456789123456789123456789123456789123456789123456789;
Stack buffer overflow has been fixed in the do_div_mod function.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
An integer overflow in number->string conversion caused completely
wrong output of the number LONGLONG_MIN with gcc 4.2.1.
Fixed by eliminating the overflow, using only operations that are
well-defined in ANSI C.
|
|\ \ \ \
| |/ / /
|/| | |
| | | | |
into polly.(none):/home/kaa/src/maint/mysql-5.0-maint
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem:
my_strntoull10rnd_8bit() handled incorrectly cases when the input
string contains a decimal point and is long enough to overrun the
'unsigned long long' type. The position of the decimal point was not
taken into account which resulted in miscalculated numbers and
truncation to appropriate SQL data type limits.
Solution:
Fix my_strntoull10rnd_8bit() to take the position of a decimal point
into account in such cases.
|
|\ \ \
| |/ /
|/| |
| | | |
into mysql.com:/home/ram/work/b31070/b31070.5.0
|
| |/
| |
| |
| |
| |
| |
| |
| |
| | |
and for bug #31070: crash during conversion of charsets
Problem: passing a 0 byte length string to some my_mb_wc_XXX()
functions leads to server crash due to improper argument check.
Fix: properly check arguments passed to my_mb_wc_XXX() functions.
|
|\ \
| | |
| | |
| | | |
into zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-5.0-maint
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Two character mappings were way off (backtick and tilde were "E"
and "Y"!), and three others were slightly rotated. The first
would cause collisions, and the latter was probably benign.
Now, assign the character mappings exactly to their normal values.
|
|\ \ \
| |/ /
|/| |
| | | |
into mysql.com:/home/bar/mysql-work/mysql-5.0-rpl
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
(Regression, caused by a patch for the bug 22646).
Problem: when result type of date_format() was changed from
binary string to character string, mixing date_format()
with a ascii column in CONCAT() stopped to work.
Fix:
- adding "repertoire" flag into DTCollation class,
to mark items which can return only pure ASCII strings.
- allow character set conversion from pure ASCII to other character sets.
|
|\ \ \
| | | |
| | | |
| | | | |
into olga.mysql.com:/home/igor/dev-opt/mysql-5.0-opt-merge
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
with the space character.
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.
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
into mysql.com:/home/bar/mysql-work/mysql-5.0-rpl
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Problem: wrong comparison with trailing space.
This problem was fixed for all other character sets under terms of
bug 7788 ""Table is full" occurs during a multitable update".
ctype-cp932.c was forgotten.
Fix: applying the same fix for ctype-cp932.c.
(see ctype-sjis.c as an example of a previously correctly fixed file)
|
| | | | |
|
|/ / / |
|