| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
If using \$(srcdir)/mysql.info in action, use same in rule.
|
| |\
| |
| |
| | |
into mysql.com:/home/kent/bk/mysql-4.1-merge
|
| | |
| |
| |
| | |
BSD compatibility
|
| | |
| |
| |
| |
| |
| | |
Fix undefined behaviour.
Many files:
Reenabled build outside ource tree
|
| | | |
|
| | | |
|
| | |\
| | |
| | |
| | | |
into trift2.:/MySQL/M41/push-4.1
|
| | | |
| | |
| | |
| | | |
RPMs (bug#22081).
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| |\ \ \
| |/ /
|/| |
| | | |
into mysql.com:/home/hf/work/mysql-4.1-mrg
|
| | |\ \
| | | |
| | | |
| | | | |
into rakia.gmz:/home/kgeorge/mysql/autopush/B19216-4.1-opt
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The server sends a number of columns to the client.
It uses a limited "fast" function for that instead of the
general one. This fast function cannot send numbers larger
than 2 bytes.
This causes the client to expect smaller number of columns.
The client writes outside of the allocated memory buffer
as a result.
Fixed the server to use the general function to send column
count.
Fixed the client to check the column count before writing
column data.
|
| | |\ \ \
| | | | |
| | | | |
| | | | | |
into macbook.gmz:/Users/kgeorge/mysql/work/mem-test-4.1-opt
|
| | | | | | |
|
| | |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- When returning metadata for scalar subqueries the actual type of the
column was calculated based on the value type, which limits the actual
type of a scalar subselect to the set of (currently) 3 basic types :
integer, double precision or string. This is the reason that columns
of types other then the basic ones (e.g. date/time) are reported as
being of the corresponding basic type.
Fixed by storing/returning information for the column type in addition
to the result type.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The parser is allocating Item_field for references by name in ORDER BY
expressions. Such expressions however may point not only to Item_field
in the select list (or to a table column) but also to an arbitrary Item.
This causes Item_field::fix_fields to throw an error about missing
column.
The fix substitutes Item_field for the reference with an Item_ref when
not pointing to Item_field.
|
| | |\ \ \
| | | | |
| | | | |
| | | | | |
into mysql.com:/usersnfs/abotchkov/mysql-4.1-opt1
|
| | | |\ \ \
| | | |/ /
| | |/| |
| | | | | |
into mysql.com:/home/hf/work/0current_stmt/my41-current_stmt
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
the incompatibility was caused by current_stmt member added to the MYSQL
structure.
It's possible to move it to THD structure instead which saves ABI
|
| | |\ \ \ \
| | |/ / /
| |/| | |
| | | | | |
into mysql.com:/home/hf/work/w3475/my41-w3475
|
| | | | | | |
|
| | | |/ /
| | | |
| | | |
| | | |
| | | | |
Necessary code added to mysqltest.c.
Disabled tests are available now.
|
| | |\ \ \
| | |/ /
| |/| |
| | | | |
into rurik.mysql.com:/home/igor/mysql-4.1-opt
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
If elements a not top-level IN subquery were accessed by an index and
the subquery result set included a NULL value then the quantified
predicate that contained the subquery was evaluated to NULL when
it should return a non-null value.
|
| |\ \ \ \
| | |_|/
| |/| |
| | | | |
into mysql.com:/home/bk/MERGE/mysql-4.1-merge
|
| | | | |
| | | |
| | | |
| | | | |
mysql-test/include
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
mending windows test.
|
| |\ \ \ \
| |/ / /
| | | |
| | | | |
into mysql.com:/home/bk/MERGE/mysql-4.1-merge
|
| | | | |
| | | |
| | | |
| | | | |
Test for base directory when a RPM install corrected
|
| | |\ \ \
| | | | |
| | | | |
| | | | | |
into trift2.:/MySQL/M41/push-4.1
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Adapt to the different path of the server program, if installation was by RPM.
Missing in the first changeset for bug#17194.
|
| | |\ \ \ \
| | | | | |
| | | | | |
| | | | | | |
into trift2.:/MySQL/M41/push-4.1
|
| | | |\ \ \ \
| | | | | | |
| | | | | | |
| | | | | | | |
into trift2.:/MySQL/M41/clone-4.1
|
| | | | | | | | |
|
| | | |\ \ \ \ \
| | | | |/ / /
| | | |/| | |
| | | | | | | |
into trift2.:/MySQL/M41/clone-4.1
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Necessary changes if one of the test scripts is to be used with a RPM installation (bug#17194).
This change handles finding the server and the other programs,
but it does not solve the problem to get a writable "var" directory.
If we want to avoid world-writable directories below "/usr/share/mysql-test" (and we do!),
any automatic solution would require fixed decisions which may not match the local installation.
For the Perl script, use "--vardir"; for the shell script, create "mysql-test/var" manually.
|
| | | | | | | | |
|
| | | | |/ / /
| | |/| | |
| | | | | |
| | | | | | |
Create block around DBUG_ENTER late in function
|
| | |\ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | | |
into kahlann.erinye.com:/home/df/mysql/build/mtr-4.1
|
| | | | | | | | |
|
| | |\ \ \ \ \ \
| | |/ / / / /
| |/| | | | |
| | | | | | | |
into outpost.site:/home/cps/mysql/trees/4.1-runtime-bug9191
|
| | | |\ \ \ \ \
| | | | | | | |
| | | | | | | |
| | | | | | | | |
into outpost.site:/home/cps/mysql/trees/4.1-runtime-bug9191
|
| | | | | | | | | |
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
(4.1 version, with post-review fixes)
The fix for another Bug (6439) limited FROM_UNIXTIME() to
TIMESTAMP_MAX_VALUE which is 2145916799 or 2037-12-01 23:59:59 GMT,
however unix timestamp in general is not considered to be limited
by this value. All dates up to power(2,31)-1 are valid.
This patch extends allowed TIMESTAMP range so, that max
TIMESTAMP value is power(2,31)-1. It also corrects
FROM_UNIXTIME() and UNIX_TIMESTAMP() functions, so that
max allowed UNIX_TIMESTAMP() is power(2,31)-1. FROM_UNIXTIME()
is fixed accordingly to allow conversion of dates up to
2038-01-19 03:14:07 UTC. The patch also fixes CONVERT_TZ()
function to allow extended range of dates.
The main problem solved in the patch is possible overflows
of variables, used in broken-time representation to time_t
conversion (required for UNIX_TIMESTAMP).
|
| | | | |/ / / /
| | |/| | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Added --force-restart pseudo server argument to shell version as well
|
