mirror/mariadb
1
0
Fork 0
mirror of https://github.com/MariaDB/server.git synced 2025-01-20 05:52:27 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
10833 commits 2784 branches 343 tags 1.6 GiB
Commit graph

5520 commits

Author SHA1 Message Date
acurtis@pcgem.rdg.cyberkinetica.com
a316e2f9e5 Bug#2703 
"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.
 2004-02-12 12:01:27 +00:00
bar@bar.intranet.mysql.r18.ru
7d361a6c20 Merge abarkov@bk-internal.mysql.com:/home/bk/mysql-4.1 
into bar.intranet.mysql.r18.ru:/usr/home/bar/mysql-4.1
 2004-02-11 16:55:44 +04:00
bar@bar.intranet.mysql.r18.ru
4e77123079 Bug 2701: Function CHARSET() inconsistency 
CONVERT3 was removed, it was for test purposes,
and rather harmful.
 2004-02-11 16:53:39 +04:00
hf@deer.(none)
77e9444530 Merge abotchkov@bk-internal.mysql.com:/home/bk/mysql-4.1 
into deer.(none):/home/hf/work/mysql-4.1.2208
 2004-02-11 16:36:33 +04:00
guilhem@gbichot2.local
e450acc71c Fix for BUG#2703 
"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.
 2004-02-11 12:32:47 +01:00
hf@deer.(none)
e5c2b42d75 Merge abotchkov@bk-internal.mysql.com:/home/bk/mysql-4.1 
into deer.(none):/home/hf/work/mysql-4.1.2208
 2004-02-11 11:01:05 +04:00
guilhem@mysql.com
f8f0c212f3 Merge gbichot@213.136.52.20:/home/bk/mysql-4.1 
into mysql.com:/home/mysql_src/mysql-4.1
 2004-02-10 23:48:17 +01:00
guilhem@gbichot2.local
7db22b1ed3 Fix for prepared statements: 
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
 2004-02-10 23:47:34 +01:00
vva@eagle.mysql.r18.ru
7be0954e12 Merge vvagin@bk-internal.mysql.com:/home/bk/mysql-4.1 
into eagle.mysql.r18.ru:/home/vva/work/BUG_2592/mysql-4.1
 2004-02-11 00:56:35 +04:00
vva@eagle.mysql.r18.ru
34fb646fb4 code cleanup of processing MY_LEX_USER_VARIABLE_DELIMITER 
in sql/sql_lex.cc
 2004-02-11 00:47:18 +04:00
guilhem@mysql.com
9de2005834 Merge gbichot@213.136.52.20:/home/bk/mysql-4.1 
into mysql.com:/home/mysql_src/mysql-4.1
 2004-02-10 16:33:07 +01:00
konstantin@mysql.com
94c71f4bf8 Another implementation of send_eof() cleanup 2004-02-10 18:33:06 +03:00
hf@deer.(none)
d7e3b89ce9 Merge abotchkov@bk-internal.mysql.com:/home/bk/mysql-4.1 
into deer.(none):/home/hf/work/mysql-4.1.2208
 2004-02-10 19:33:04 +04:00
bar@bar.intranet.mysql.r18.ru
0a1ceb667c Merge abarkov@bk-internal.mysql.com:/home/bk/mysql-4.1 
into bar.intranet.mysql.r18.ru:/usr/home/bar/mysql-4.1
 2004-02-10 19:33:03 +04:00
vva@eagle.mysql.r18.ru
da8f78a0ad Merge vvagin@bk-internal.mysql.com:/home/bk/mysql-4.1 
into eagle.mysql.r18.ru:/home/vva/work/BUG_2592/mysql-4.1
 2004-02-10 19:33:02 +04:00
vva@eagle.mysql.r18.ru
fd03264469 Merge 2004-02-10 18:56:43 +04:00
guilhem@gbichot2.local
75e7765798 Follow-up of a discussion on dev-docs@ : 
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 @@.
 2004-02-10 15:14:48 +01:00
jani@ua141d10.elisa.omakaista.fi
0c6a0b9a31 Wrong type of an argument was sent to my_printf_error(), which 
caused UDF functions to segmenation fault when they tried to
print an error during wrong usage.
 2004-02-10 13:36:21 +00:00
jani@ua141d10.elisa.omakaista.fi
1ce9ae5429 An include was missing. 2004-02-10 13:11:55 +00:00
hf@deer.(none)
348bd98e48 Fix for #2208 (multi-query returns wrong result in embedded library) 
now we execute only one first select during mysql_real_query
others - during 'mysql_next_result'
 2004-02-10 17:09:59 +04:00
bar@bar.intranet.mysql.r18.ru
5219fc269b http://bugs.mysql.com/bug.php?id=2368 
Multibyte charsets do not check that incoming data is well-formed
 2004-02-10 15:42:46 +04:00
bell@sanja.is.com.ua
bccca8f7cb Merge sanja.is.com.ua:/home/bell/mysql/bk/mysql-4.1 
into sanja.is.com.ua:/home/bell/mysql/bk/work-derived2-4.1
 2004-02-10 02:24:10 +02:00
bell@sanja.is.com.ua
0aa7a4b4ea after merge & valgrind test fixes (BUG#2120) 2004-02-10 02:18:22 +02:00
konstantin@mysql.com
8ec790ec8d Merge bk-internal.mysql.com:/home/bk/mysql-4.1 
into mysql.com:/home/kostja/mysql/mysql-4.1-root
 2004-02-09 16:40:20 +03:00
konstantin@oak.local
12f687db70 switch off SERVER_MORE_RESULTS_EXISTS, but 
don't set other flags: it breaks future extensions
 2004-02-09 16:26:38 +03:00
bell@sanja.is.com.ua
ff0a6e9686 Merge sanja.is.com.ua:/home/bell/mysql/bk/mysql-4.1 
into sanja.is.com.ua:/home/bell/mysql/bk/work-derived2-4.1
 2004-02-09 15:01:51 +02:00
monty@mysql.com
cc78e2d97a Ensure that result from date_format() is binary 
Removed warnings from test suite
 2004-02-09 13:59:41 +01:00
bell@sanja.is.com.ua
74a9ca1991 ufter revview fix (BUG#2120) 2004-02-09 14:44:03 +02:00
monty@mysql.com
3e35cce54d merge 2004-02-09 12:35:01 +01:00
monty@mysql.com
06432eac36 Added --compact to mysqlbinlog 
Fixed output from mysqlbinlog when using --skip-comments
Fixed warnings from valgrind
Fixed ref_length when used with HEAP tables
More efficent need_conversion()
Fixed error handling in UPDATE with not updateable tables
Fixed bug in null handling in CAST to signed/unsigned
 2004-02-09 12:31:03 +01:00
bell@sanja.is.com.ua
b99d13582b Merge sanja.is.com.ua:/home/bell/mysql/bk/mysql-4.1 
into sanja.is.com.ua:/home/bell/mysql/bk/work-derived2-4.1
 2004-02-09 12:10:12 +02:00
vva@eagle.mysql.r18.ru
cc1ff3c479 fixed bug #2592 mysqldump doesn't quote "tricky" names correctly 2004-02-07 02:22:12 +04:00
bar@bar.intranet.mysql.r18.ru
d13ad0822e Problem fix: 
http://bugs.mysql.com/bug.php?id=2366
Wrong utf8 behaviour when data is trancated
 2004-02-06 16:59:25 +04:00
monty@mysql.com
480b082cf4 merge 2004-02-05 18:14:48 +01:00
vva@eagle.mysql.r18.ru
d200443bed Merge vvagin@bk-internal.mysql.com:/home/bk/mysql-4.1 
into eagle.mysql.r18.ru:/home/vva/work/BUG_2310/mysql-4.1
 2004-02-05 18:59:13 +04:00
vva@eagle.mysql.r18.ru
4fbc147b2f code and comments cleanup 2004-02-05 18:58:10 +04:00
monty@mysql.com
6bfede9639 Added SQL_SELECT::cleanup() to make it easier to reuse SQL_SELECT item's for sub selects. Needed for proper fix for bug #2479. 
Added 'select_to_file' class to be able to merge identical code for select_export and select_dump
 2004-02-05 10:22:08 +01:00
acurtis@pcgem.rdg.cyberkinetica.com
d0d54abcf2 Bug#2634 
Emit "TYPE=" for 4.0 and 3.23 compatible modes
 2004-02-05 02:30:28 +00:00
konstantin@mysql.com
7e9944d3d5 cleanup: #ifdef DELETE_ITEMS removed 2004-02-03 23:34:31 +03:00
bar@bar.intranet.mysql.r18.ru
8f1b5b48cc Bug #2619 ucs2 LIKE comparison fails in some cases 2004-02-03 18:14:23 +04:00
ram@gw.mysql.r18.ru
c4728c276a Code cleanup: 
we don't need opt_range.h and opt_range.cc files at all.
 2004-02-03 14:35:24 +04:00
ram@gw.mysql.r18.ru
8eb590a71e Merge rkalimullin@bk-internal.mysql.com:/home/bk/mysql-4.1 
into gw.mysql.r18.ru:/usr/home/ram/work/4.1.b2419
 2004-02-03 12:47:34 +04:00
vva@eagle.mysql.r18.ru
a44bb8a660 Merge vvagin@bk-internal.mysql.com:/home/bk/mysql-4.1 
into eagle.mysql.r18.ru:/home/vva/work/BUG_2438/mysql-4.1
 2004-02-03 01:19:04 +04:00
vva@eagle.mysql.r18.ru
9762c5d7b6 Merge eagle.mysql.r18.ru:/home/vva/work/mysql.orig/clear/mysql-4.1 
into eagle.mysql.r18.ru:/home/vva/work/BUG_2438/mysql-4.1
 2004-02-03 01:16:08 +04:00
vva@eagle.mysql.r18.ru
45b85c10c3 changed allocation of st_table::insert_values 
from table->mem_root to thd->mem_root 
(fixed bug #2438 "Runaway memory consumption")
 2004-02-03 01:07:43 +04:00
ram@gw.mysql.r18.ru
f231d9826b just tried to find all 'skipp' and replace it with 'skip'. 2004-02-02 20:25:39 +04:00
ram@gw.mysql.r18.ru
3243678040 Merge rkalimullin@bk-internal.mysql.com:/home/bk/mysql-4.1 
into gw.mysql.r18.ru:/usr/home/ram/work/4.1.b2419
 2004-02-02 19:33:45 +04:00
ram@gw.mysql.r18.ru
f16dfb9d36 Added a comment for NULL range creation. 2004-02-02 19:32:49 +04:00
bar@bar.intranet.mysql.r18.ru
e2ffbc1a6a Indexes can be used for optimization if the operation 
collation is the same with the index collation.
 2004-02-02 17:50:14 +04:00
igor@rurik.mysql.com
8a3e00a05b preload.result, key_cache.result, preload.test, key_cache.test, sql_yacc.yy: 
Fixed bug #2602 in CACHE INDEX, LOAD INDEX
 2004-02-02 00:19:51 -08:00