- 16 Mar, 2004 22 commits
-
-
bell@sanja.is.com.ua authored
into sanja.is.com.ua:/home/bell/mysql/bk/work-select_list-4.1
-
bell@sanja.is.com.ua authored
-
bell@sanja.is.com.ua authored
into sanja.is.com.ua:/home/bell/mysql/bk/work-in-4.1
-
vva@eagle.mysql.r18.ru authored
into eagle.mysql.r18.ru:/home/vva/work/BUG_3160/mysql-4.1
-
vva@eagle.mysql.r18.ru authored
-
bell@sanja.is.com.ua authored
-
bell@sanja.is.com.ua authored
-
bell@sanja.is.com.ua authored
into sanja.is.com.ua:/home/bell/mysql/bk/mysql-4.1
-
vva@eagle.mysql.r18.ru authored
into eagle.mysql.r18.ru:/home/vva/work/BUG_2082/mysql-4.1
-
vva@eagle.mysql.r18.ru authored
into eagle.mysql.r18.ru:/home/vva/work/BUG_2082/mysql-4.1
-
vva@eagle.mysql.r18.ru authored
Q_QUERY_VERTICAL/Q_QYERY_HORIZONTAL in client/mysqltest.c (changed switch to ?:)
-
bell@sanja.is.com.ua authored
into sanja.is.com.ua:/home/bell/mysql/bk/mysql-4.1
-
gluh@gluh.mysql.r18.ru authored
into gluh.mysql.r18.ru:/home/gluh/mysql-4.1.clear
-
bell@sanja.is.com.ua authored
into sanja.is.com.ua:/home/bell/mysql/bk/work-lower_case-4.1
-
ram@gw.mysql.r18.ru authored
into gw.mysql.r18.ru:/usr/home/ram/work/4.1.b2885
-
bell@sanja.is.com.ua authored
into sanja.is.com.ua:/home/bell/mysql/bk/work-lower_case-4.1
-
vva@eagle.mysql.r18.ru authored
into eagle.mysql.r18.ru:/home/vva/work/BUG_2709/mysql-4.1
-
gluh@gluh.mysql.r18.ru authored
-
ram@gw.mysql.r18.ru authored
into gw.mysql.r18.ru:/usr/home/ram/work/4.1.b2885
-
bell@sanja.is.com.ua authored
into sanja.is.com.ua:/home/bell/mysql/bk/work-lower_case-4.1
-
bell@sanja.is.com.ua authored
into sanja.is.com.ua:/home/bell/mysql/bk/work-fix_fields-4.1
-
monty@mysql.com authored
-
- 15 Mar, 2004 18 commits
-
-
monty@mysql.com authored
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-4.1
-
monty@mysql.com authored
-
serg@serg.mylan authored
into serg.mylan:/usr/home/serg/Abk/mysql-4.1
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-4.1
-
konstantin@mysql.com authored
flaws list) TODO: * verify that no sequence of API calls produces SIGSEGV. That is, verify that mysql_stmt_init -> mysql_stmt_fetch is OK, or mysql_stmt_prepare -> mysql_stmt_fetch_column is OK and sets meaningful error. * remove alloc_stmt_fields call * revise stmt->state codes and statement states. * there are other items in prepared statements 'to fix' document. Done: - cleanups and comments - revision of prepared statement error codes. - mysql_stmt_prepare is now can always be called (that is, you can reprepare a statement) - new implementation of mysql_stmt_close and fetch cancellation
-
hf@deer.(none) authored
-
hf@deer.(none) authored
into deer.(none):/home/hf/work/mysql-4.1.clean
-
hf@deer.(none) authored
-
serg@serg.mylan authored
-
konstantin@mysql.com authored
exceed unsigned long limit.
-
vva@eagle.mysql.r18.ru authored
#2709 Affected Rows for ON DUPL. KEY undocumented, perheps illogical 1. added COPY_INFO::updated to work with it in 'insert .. on duplicate' instead of COPY_INFO::deleted 2. added affected rows to output of "info:" in mysqltest.c
-
konstantin@mysql.com authored
COM_EXECUTE packet" and #2795 "prepare + execute without bind_param crashes server" and #2473 "seg fault running tests/client_test.c": - length checking added to packet parser - default impelemntation of Item_param::set_param_func will work in case of malformed packet. No test cases are possible in our test suite, as there are no tests operating on protocol layer.
-
gluh@gluh.mysql.r18.ru authored
-
gluh@gluh.mysql.r18.ru authored
-
bell@sanja.is.com.ua authored
into sanja.is.com.ua:/home/bell/mysql/bk/work-fix_fields-4.1
-
gluh@gluh.mysql.r18.ru authored
-
bell@sanja.is.com.ua authored
into sanja.is.com.ua:/home/bell/mysql/bk/work-in-4.1
-