An error occurred fetching the project authors.
- 14 Jul, 2005 1 commit
-
-
konstantin@mysql.com authored
in cursors.
-
- 13 Jul, 2005 2 commits
-
-
konstantin@mysql.com authored
-
ramil@mysql.com authored
-
- 12 Jul, 2005 2 commits
-
-
georg@lmy002.wdf.sap.corp authored
-
georg@lmy002.wdf.sap.corp authored
Added api function mysql_get_character_set_info which provides information about the current client character set.
-
- 01 Jul, 2005 2 commits
-
-
konstantin@mysql.com authored
Add a test case for Bug#11656 "Server crash with mysql_stmt_fetch (cursors)", the bug itself is no longer present.
-
konstantin@mysql.com authored
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).
-
- 30 Jun, 2005 1 commit
-
-
konstantin@mysql.com authored
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.
-
- 28 Jun, 2005 1 commit
-
-
konstantin@mysql.com authored
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.
-
- 24 Jun, 2005 1 commit
-
-
jimw@mysql.com authored
it can use it to switch to only quoting apostrophes by doubling them when it is in effect. (Bug #10214)
-
- 20 Jun, 2005 1 commit
-
-
konstantin@mysql.com authored
-
- 19 Jun, 2005 2 commits
-
-
konstantin@mysql.com authored
-
konstantin@mysql.com authored
use tabs.
-
- 17 Jun, 2005 1 commit
-
-
konstantin@mysql.com authored
-
- 14 Jun, 2005 2 commits
-
-
bell@sanja.is.com.ua authored
-
evgen@moonbone.local authored
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.
-
- 09 Jun, 2005 1 commit
-
-
konstantin@mysql.com authored
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.
-
- 01 Jun, 2005 1 commit
-
-
serg@serg.mylan authored
-
- 27 May, 2005 1 commit
-
-
gluh@eagle.intranet.mysql.r18.ru authored
set net->no_send_error to 0 before execution of each element of multiquery statement to provide the sending of error to client
-
- 18 May, 2005 1 commit
-
-
monty@mysql.com authored
This makes it easier to give an error in the handler if there was a problem generating an auto-increment value
-
- 16 May, 2005 2 commits
-
-
konstantin@mysql.com authored
- 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.
-
monty@mysql.com authored
Fixed bug in mysql_stmt_fetch() when retrieving rows to return
-
- 12 May, 2005 1 commit
-
-
konstantin@mysql.com authored
(crash on attempt to re-execute a statement with an open cursor) + post-review fixes.
-
- 30 Apr, 2005 1 commit
-
-
konstantin@mysql.com authored
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).
-
- 28 Apr, 2005 1 commit
-
-
jimw@mysql.com authored
-
- 27 Apr, 2005 1 commit
-
-
monty@mysql.com authored
Fixed problem with NULL in VARCHAR/BLOB keys for multi-part keys where VARCHAR/BLOB is first part
-
- 12 Apr, 2005 1 commit
-
-
georg@lmy002.wdf.sap.corp authored
return an error
-
- 04 Apr, 2005 1 commit
-
-
monty@mysql.com authored
Fix that mysql.proc works with new VARCHAR fields Give warnings for wrong zero dates
-
- 25 Mar, 2005 1 commit
-
-
bar@mysql.com authored
Don't run GBK test if not GBK support was compiled.
-
- 24 Mar, 2005 1 commit
-
-
konstantin@mysql.com authored
and Bug#9159 "Server crash during mysql_stmt_close". The patch adds support for single-row result sets in cursors.
-
- 23 Mar, 2005 1 commit
-
-
konstantin@mysql.com authored
server" to the test suite, the bug is no longer repeatable.
-
- 19 Mar, 2005 1 commit
-
-
konstantin@mysql.com authored
-
- 17 Mar, 2005 1 commit
-
-
jimw@mysql.com authored
-
- 25 Feb, 2005 1 commit
-
-
monty@mysql.com authored
(Found during build process)
-
- 15 Feb, 2005 1 commit
-
-
jimw@mysql.com authored
a multibyte character, but was not a valid multibyte character. Refinement of fix for Bug #8378.
-
- 13 Feb, 2005 1 commit
-
-
bell@sanja.is.com.ua authored
-
- 10 Feb, 2005 4 commits
-
-
konstantin@mysql.com authored
-
konstantin@mysql.com authored
reset mysql->net.last_error": the solution is to clear MYSQL->net error before performing COM_CLOSE: if the call succeeds, the connection is usable for other statements. More comprehensive fix is to clear MYSQL->net for all recoverable errors at the time they happen, it will be implemented in 5.0 as it introduces incompatibility in behavior.
-
konstantin@mysql.com authored
-
jimw@mysql.com authored
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)
-