serg@serg.mylan
03ffb63f08
no dots in the error messages!
...
--disable-warning in union.test
2004-02-15 19:16:38 +01:00
serg@serg.mylan
abc9ef9770
Merge bk-internal:/home/bk/mysql-4.1/
...
into serg.mylan:/usr/home/serg/Abk/mysql-4.1
2004-02-15 18:35:06 +01:00
serg@serg.mylan
e9c46aaf80
REVOKE ALL PRIVILEGES, GRANT FROM user_list
...
is changed to a more consistent
REVOKE ALL PRIVILEGES, GRANT OPTION FROM user_list.
Bug #2642
2004-02-15 17:59:52 +01:00
Sinisa@sinisa.nasamreza.org
d43f102020
Merge sinisa@bk-internal.mysql.com:/home/bk/mysql-4.1
...
into sinisa.nasamreza.org:/mnt/work/mysql-4.1
2004-02-14 20:24:49 +02:00
hf@deer.(none)
e100530b3e
Fix for #2212 (mysql_change_user doesn't work in embedded library)
...
now it's working
2004-02-14 20:26:21 +04:00
Sinisa@sinisa.nasamreza.org
eb83bb374a
Merge sinisa@bk-internal.mysql.com:/home/bk/mysql-4.1
...
into sinisa.nasamreza.org:/mnt/work/mysql-4.1
2004-02-14 15:08:32 +02:00
bell@sanja.is.com.ua
7626ab603e
Merge sanja.is.com.ua:/home/bell/mysql/bk/mysql-4.1
...
into sanja.is.com.ua:/home/bell/mysql/bk/work-limit-4.1
2004-02-14 13:06:04 +02:00
vva@eagle.mysql.r18.ru
50fb56399a
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-14 02:28:19 +04:00
vva@eagle.mysql.r18.ru
48d4e33328
a little optimization in yylex
...
(case MY_LEX_USER_VARIABLE_DELIMITER for multichar strings)
and my_mbcharlen
2004-02-14 02:26:27 +04:00
serg@serg.mylan
01c2ca5b8a
Merge bk-internal:/home/bk/mysql-4.1/
...
into serg.mylan:/usr/home/serg/Abk/mysql-4.1
2004-02-13 15:30:00 +01:00
serg@serg.mylan
26c7003e37
small optimization
2004-02-13 15:27:58 +01:00
serg@serg.mylan
5914e5705c
my_atof is deleted
...
strtod from mit-threads is restored and cleaned up
2004-02-13 15:27:21 +01:00
bar@bar.intranet.mysql.r18.ru
3bdb96d33e
Bug #2699 UTF8 breaks primary keys for cols > 85 characters
2004-02-13 17:58:02 +04:00
hf@deer.(none)
a052909753
Merge abotchkov@bk-internal.mysql.com:/home/bk/mysql-4.1
...
into deer.(none):/home/hf/work/mysql-4.1.2211
2004-02-13 11:57:22 +04:00
hf@deer.(none)
c25fc5c664
Another fix for #2208
...
previous one had error
2004-02-13 11:56:36 +04:00
bell@sanja.is.com.ua
5ef05f4284
Merge sanja.is.com.ua:/home/bell/mysql/bk/mysql-4.1
...
into sanja.is.com.ua:/home/bell/mysql/bk/work-limit-4.1
2004-02-12 22:33:30 +02:00
vva@eagle.mysql.r18.ru
689ee0be98
Merge vvagin@bk-internal.mysql.com:/home/bk/mysql-4.1
...
into eagle.mysql.r18.ru:/home/vva/work/BUG_2593/mysql-4.1
2004-02-13 00:33:29 +04:00
vva@eagle.mysql.r18.ru
50076a5d09
Merge eagle.mysql.r18.ru:/home/vva/work/mysql.orig/clear/mysql-4.1
...
into eagle.mysql.r18.ru:/home/vva/work/BUG_2593/mysql-4.1
2004-02-13 00:31:39 +04:00
vva@eagle.mysql.r18.ru
13e04a85b7
some optimization in append_identifier (sql/sql_show.cc)
2004-02-13 00:28:00 +04:00
serg@serg.mylan
67fbc4d2b7
make all "artificial" syntax errors to report a place where they take place ("...syntax error ... near ...")
2004-02-12 18:37:15 +01:00
Sinisa@sinisa.nasamreza.org
96fe6fda95
Merge sinisa@bk-internal.mysql.com:/home/bk/mysql-4.1
...
into sinisa.nasamreza.org:/mnt/work/mysql-4.1
2004-02-12 16:48:33 +02:00
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
Sinisa@sinisa.nasamreza.org
125fb04b87
merge fixes
2004-02-11 19:15:02 +02: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
Sinisa@sinisa.nasamreza.org
451e423be4
Fixes for bugs #2508 and #2552
2004-02-10 21:34:25 +02: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