| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
CURSOR_TYPE_READ_ONLY date/datetime filter server crash".
The fix adds support for Item_change_list in cursors (proper rollback
of the modified item tree).
|
|
|
|
|
|
|
|
|
|
| |
open cursor after mysql_stmt_execute" + post-review fixes.
The bug was caused by wrong flags in stmt->server_status on the client
side: if there was no cursor, the server didn't send server_status
flags to the client, and the old flags were used to set up the
fetch function of a statement. Consequently, stmt_read_row_from_cursor was
used when there was no cursor. The fix fixes the server to always
send server flags to the client.
|
|
|
|
|
|
|
|
|
|
|
|
| |
CURSOR_TYPE_READ_ONLY select within select".
The bug was caused by the reset of thd->mem_root to thd->main_mem_root in
Item_subselect::exec, which in turn triggered too early free_root() for
data which was needed on subsequent fetches from a cursor.
This reset also caused a memory leak in stored procedures, as
subsequent executions of instructions containing a subselect
were allocating memory in thd->main_mem_root, which is not freed
until the end of the entire SP, instead of the per-call mem_root,
which is freed in the end of execution of the instruction.
|
| |
|
| |
|
|
|
|
| |
use tabs.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Wrong method for creating temporary field was choosen, which results in
sending int field with int header but lonlong data.
Test case is added to mysql_client_test.c because client library is required
to test the bug.
|
|
|
|
| |
Fix for link failures on boxes with non-gnu compiler.
|
|
|
|
|
|
| |
CURSOR_TYPE_READ_ONLY". The bug was that we (me) don't perform proper
cleanups of the prepared statement when done fetching from a cursor.
Another patch.
|
| |
|
|
|
|
|
| |
set net->no_send_error to 0 before execution of each element of
multiquery statement to provide the sending of error to client
|
|
|
|
|
|
| |
~(ulonglong)
This makes it easier to give an error in the handler if there was a problem generating an auto-increment value
|
|\
| |
| |
| | |
into mysql.com:/opt/local/work/mysql-5.0-9643
|
| |
| |
| |
| |
| |
| |
| | |
- check on the client the unsupported feature and return
an error message if it's been requested.
Additionally added API support for STMT_ATTR_PREFETCH_ROWS.
Post-review fixes.
|
|/
|
|
| |
Fixed bug in mysql_stmt_fetch() when retrieving rows to return
|
|
|
|
|
| |
(crash on attempt to re-execute a statement with an open cursor) +
post-review fixes.
|
|\ |
|
| |\
| | |
| | |
| | | |
into mysql.com:/home/jimw/my/mysql-4.1-clean
|
| | | |
|
|\ \ \
| |/ / |
|
| |/ |
|
|\ \
| | |
| | |
| | | |
into mysql.com:/home/my/mysql-5.0
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
with cursor". The patch refactors do_select/sub_select
functions, which implement the nested loop algorithm, and reuses them to
fetch rows for cursors as well.
Pushing with view.test failing (--ps-protocol).
|
|\ \ \
| |/ /
|/| |
| | | |
into mysql.com:/home/my/mysql-5.0
|
| | |
| | |
| | |
| | | |
Fixed problem with NULL in VARCHAR/BLOB keys for multi-part keys where VARCHAR/BLOB is first part
|
| | |
| | |
| | |
| | | |
return an error
|
|/ /
| |
| |
| |
| | |
Added email threading capabilities to both
programs.
|
| |
| |
| |
| |
| |
| |
| | |
when linking staticly
Fix that mysql.proc works with new VARCHAR fields
Give warnings for wrong zero dates
|
|\ \
| |/
| |
| | |
into eagle.intranet.mysql.r18.ru:/home/bar/mysql-5.0
|
| |
| |
| |
| | |
Don't run GBK test if not GBK support was compiled.
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | | |
and Bug#9159 "Server crash during mysql_stmt_close".
The patch adds support for single-row result sets in cursors.
|
|/ /
| |
| |
| | |
server" to the test suite, the bug is no longer repeatable.
|
| | |
|
|\ \
| | |
| | |
| | | |
into mysql.com:/home/jimw/my/mysql-5.0-clean
|
| |\ \
| | | |
| | | |
| | | | |
into mysql.com:/home/jimw/my/mysql-5.0-build
|
| | | | |
|
|\ \ \ \
| |/ / /
| | | |
| | | | |
into zim.(none):/home/brian/mysql/mysql-5.0
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
First one is related to Bug#7905. One should not be allowed to
create new user with password without UPDATE privilege to
MySQL database. Furthermore, executing the same GRANT statement
twice would actually crash the server and corrupt privilege database.
Other bug was that one could update a column, using the existing
value as basis to calculate the new value (e.g. UPDATE t1 SET a=a+1)
without SELECT privilege to the field (a in the above example)
Fixed tests grant.pl and grant2, which were wrong.
|
|/ /
| |
| |
| | |
wants this feature look at a web-dav hookup).
|
|\ \ |
|
| | |
| | |
| | |
| | | |
(Found during build process)
|
|\ \ \
| |/ / |
|
| |\ \
| | |/ |
|
| | |\ |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
a multibyte character, but was not a valid multibyte character. Refinement
of fix for Bug #8378.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
a character that appears to be a multi-byte character based on its first
byte, but is not actually a valid multi-byte character. (Bug #8378)
|
|/ / / |
|