- 13 Feb, 2004 2 commits
- 12 Feb, 2004 8 commits
-
-
unknown authored
include/mysql.h: Auto merged libmysql/libmysql.c: Auto merged tests/client_test.c: manual merge
-
unknown authored
mysql-test/r/mysqldump.result: fixed mistake after merge
-
unknown authored
into eagle.mysql.r18.ru:/home/vva/work/BUG_2593/mysql-4.1 sql/sql_lex.cc: Auto merged
-
unknown authored
into eagle.mysql.r18.ru:/home/vva/work/BUG_2593/mysql-4.1 sql/mysql_priv.h: Auto merged sql/sql_lex.cc: Auto merged sql/sql_show.cc: Auto merged
-
unknown authored
sql/sql_show.cc: some optimization in append_identifier
-
unknown authored
into deer.(none):/home/hf/work/mysql-4.1.1438
-
unknown authored
libmysqld/lib_sql.cc: mysql.info set to the right value
-
unknown authored
"MySQL server does not detect if garbage chara at the end of query" Allow the parser to see the garbage characters. Garbage should cause the parser to report an error. sql/sql_lex.cc: Return END_OF_INPUT when at the end of the input buffer. Allows the parser to determine if there is junk after a \0 character. sql/sql_parse.cc: Undo 1.314.1.1 04/02/11 12:32:42 guilhem@mysql.com sql/sql_prepare.cc: Undo 1.73 04/02/11 12:32:42 guilhem@mysql.com
-
- 11 Feb, 2004 11 commits
-
-
unknown authored
into mysql.com:/home/dlenev/src/mysql-4.1-bg2248 include/mysql.h: Auto merged libmysql/libmysql.c: Auto merged
-
unknown authored
into bar.intranet.mysql.r18.ru:/usr/home/bar/mysql-4.1
-
unknown authored
CONVERT3 was removed, it was for test purposes, and rather harmful.
-
unknown authored
into deer.(none):/home/hf/work/mysql-4.1.2208 sql/sql_parse.cc: Auto merged
-
unknown authored
Made code shorter and more correct libmysql/client_settings.h: cli_next_result removed libmysql/libmysql.c: cli_next_result removed
-
unknown authored
-
unknown authored
into mysql.com:/home/mysql_src/mysql-4.1
-
unknown authored
"MySQL server does not detect if garbage chars at the end of query": Detect garbage chars at the end of the query or at the end of a query for a prepared statement (which happens if mysql_real_query() or mysql_prepare() were called with a too big 'length' parameter (bigger than the real intended length of the query: then we receive a query + garbage characters from the client). This resulted in garbage chars written into the binlog. Now instead the client receives something like: 'You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near '!stmt' at line 1' i.e. the server is pointing at the weird tail of the query (this '!stmt' are the garbage chars sent by the client). All tests pass, except mysqldump.test and ctype_utf8.test but they failed before the patch. sql/sql_parse.cc: Detect garbage chars at the end of the query (which happens if mysql_real_query() was called with a too big 'length' parameter (bigger than the real intended length of the query: then we receive a query + garbage characters from the client). sql/sql_prepare.cc: Detect garbage chars at the end of the query (which happens if mysql_prepare() was called with a too big 'length' parameter (bigger than the real intended length of the query: then we receive a query + garbage characters from the client). tests/client_test.c: The change to sql_parse.cc and sql_prepare.cc rightfully gives many syntax errors to tests/client_test.c which is full of mysql_prepare(mysql, "SHOW TABLES", 100). Correcting all these commands.
-
unknown authored
No needs to load charset index if the character set is build-in. client/mysql.cc: No needs to load charset index if the character set is build-in. client/mysqlcheck.c: No needs to load charset index if the character set is build-in. client/mysqldump.c: No needs to load charset index if the character set is build-in. client/mysqlimport.c: No needs to load charset index if the character set is build-in.
-
unknown authored
into mysql.com:/home/dlenev/src/mysql-4.1-bg2248
-
unknown authored
into deer.(none):/home/hf/work/mysql-4.1.2208
-
- 10 Feb, 2004 19 commits
-
-
unknown authored
into mysql.com:/home/mysql_src/mysql-4.1
-
unknown authored
added setting of 'neg' in Item_param::set_time() (looks like the only forgotten member). It's the second place I find where 'neg' was forgotten. The symptom was unexpected negative times in the binary log when running tests/client_test.c (test_date() in fact): # at 43009 #040210 15:46:42 server id 1 log_pos 43009 Query thread_id=1 exec_time=0 error_code=0 SET TIMESTAMP=1076424402; INSERT INTO test_date VALUES('2000-01-10 11:16:20','-11:16:20' etc sql/item.cc: Don't forget to copy 'neg'.
-
unknown authored
into eagle.mysql.r18.ru:/home/vva/work/BUG_2592/mysql-4.1
-
unknown authored
in sql/sql_lex.cc sql/sql_lex.cc: code cleanup of processing MY_LEX_USER_VARIABLE_DELIMITER
-
unknown authored
into mysql.com:/home/mysql_src/mysql-4.1
-
unknown authored
into mysql.com:/home/dlenev/src/mysql-4.1-bg2248
-
unknown authored
-
unknown authored
FreeBSD "ps" detection usually failed, in 90% cases, on FreeBSD-5.1. This change should work fine under 5.x and 4.x, and I believe in 3.x. too. configure.in: FreeBSD "ps" detection usually failed, in 90% cases. Thi
-
unknown authored
into deer.(none):/home/hf/work/mysql-4.1.2208 sql/sql_class.h: Auto merged sql/sql_parse.cc: Auto merged
-
unknown authored
It was together with the previous but. This test tends to prove it.
-
unknown authored
into bar.intranet.mysql.r18.ru:/usr/home/bar/mysql-4.1
-
unknown authored
into eagle.mysql.r18.ru:/home/vva/work/BUG_2592/mysql-4.1 sql/sql_lex.cc: Auto merged
-
unknown authored
mysql-test/r/mysqldump.result: correcting result after merge
-
unknown authored
client/mysqldump.c: Auto merged mysql-test/r/mysqldump.result: e
-
unknown authored
mysql-test/t/mysqldump.test: added skiped newline to the end of file
-
unknown authored
Don't show PSEUDO_THREAD_ID in SHOW VARIABLES because: - we don't want people to discover this variable as it could never do good to set it (it was designed for use by mysqlbinlog only, so that a thread can have several temp tables of the same name at the same time) - if we show it in SHOW VARIABLES, Mysql Administrator will display it and this will force us to put a description, so all MySQL Administrator user will be aware of this variable, some may have the idea to set it with a SET command, and then it will cause bad things. The variable is still settable, and still visible with SELECT @@. sql/set_var.cc: Don't show PSEUDO_THREAD_ID in SHOW VARIABLES because: - we don't want people to discover this variable as it could never do good to set it (it was designed for use by mysqlbinlog only, so that a thread can have several temp tables of the same name at the same time) - if we show it in SHOW VARIABLES, Mysql Administrator will display it and this will force us to put a description, so all MySQL Administrator user will be aware of this variable, some may have the idea to set it with a SET command, and then it will cause bad things. The variable is still settable, and still visible with SELECT @@.
-
unknown authored
Done clean-up in prep stmt API functions: 1) Removed some checks that were performed only in debug version were making debug version more tolerable to user errors than production (and thus caused problems for example masking some bugs). 2) Also removed some other checks to make prep stmt API consistent with the rest of C API (this also in line with general politics - make checks in only those places where errors are very common and hard to spot). include/mysql.h: Removed CHECK_EXTRA_ARGUMENTS define since it is no longer used anywhere. libmysql/libmysql.c: Added check that will cause mysql_fetch() to bark then it is used without calling mysql_execute() before. Removed checks that were performed only in debug version and caused problems since they were making debug version more tolerable to user errors than production. Also removed some other checks to make prep stmt API consistent in this regard with the rest of C API (this also in line with general politics - make checks in only those places where errors are very common and hard to spot). tests/client_test.c: Updated tests to reflect removal of some checks in prep stmt API. Removed lines that caused bug #2473 to pop up, should be added as separate test with the fix for this bug. Added test for bug#2248 "mysql_fetch without prior mysql_execute hangs"
-
unknown authored
caused UDF functions to segmenation fault when they tried to print an error during wrong usage.
-
unknown authored
BitKeeper/etc/logging_ok: Logging to logging@openlogging.org accepted
-