pem@mysql.comhem.se
95dcdde134
Fixed BUG#3287: Stored procedure handler scope outside of begin/end.
...
Backpatching overwrote already backpatched instructions, which made it
skip the hpop instruction; possibly not only a problem for handlers,
but this is one known case when it happened.
2004-04-05 17:01:19 +02:00
bell@sanja.is.com.ua
da44d11553
Merge sanja.is.com.ua:/home/bell/mysql/bk/mysql-5.0
...
into sanja.is.com.ua:/home/bell/mysql/bk/work-limit-5.0
2004-03-29 22:42:59 +03:00
bell@sanja.is.com.ua
9bd49d489c
after review patch
...
commant for function
2004-03-29 22:40:49 +03:00
pem@mysql.comhem.se
329013f99e
Fixed BUG#3287: Stored Procedure Case Statement Not SQL:2003 Compliant.
2004-03-29 12:29:06 +02:00
pem@mysql.comhem.se
52c820fbc5
Enforce standard declaration order in SPs.
...
Added new test cases for this, and adjusted old tests accordingly,
and new error codes and messages.
Fixed bugs in some tests (bug2673 and use test).
Added debug printing of instructions in SPs.
2004-03-29 11:16:45 +02:00
bell@sanja.is.com.ua
b3936e426d
aftermerge fix
2004-03-28 12:57:59 +03:00
bell@sanja.is.com.ua
e0c2ff9df7
merge
2004-03-27 15:59:48 +02:00
pem@mysql.comhem.se
5954e94fa7
Fixed BUG#3259: Stored procedure names are case sensitive.
...
Procedure names were unintentionally case-sensitive when read from the database
(but case-insensitive when fetched from the cache).
Note that the DB-part of qualified names is still case-sensitive (for consistency
with other usage in mysql).
2004-03-23 12:04:40 +01:00
pem@mysql.comhem.se
5476eb0709
WL#1366: Use the schema (db) associated with an SP.
...
Phase 4 (final): Remove associated stored procedures when a database is dropped.
2004-03-22 14:44:41 +01:00
pem@mysql.comhem.se
13987057f6
WL#1366: Use the schema (db) associated with an SP.
...
Phase 3: Made qualified names work for functions as well.
2004-03-19 19:01:54 +01:00
pem@mysql.com
786f823248
Merge
2004-03-18 15:08:17 +01:00
pem@mysql.com
d7e5bbd625
Merge mysql.com:/usr/local/bk/mysql-5.0
...
into mysql.com:/home/pem/work/mysql-5.0-merge
2004-03-17 12:11:04 +01:00
pem@mysql.comhem.se
0411f45801
Fix BUG#2674: Crash if return system variable in stored procedures.
...
Had to initialize some fields in lex before parsing an SP read from
mysql.proc.
2004-03-17 12:09:03 +01:00
sergefp@mysql.com
3d2794ae9a
Fix for Bug#3183
2004-03-15 23:11:58 +03:00
pem@mysql.comhem.se
6c6bbba007
WL#1366: Use the schema (db) associated with an SP.
...
Phase 2: Make SPs belong to a DB, and use qualified names.
As a side effect, using USE in an SP is no longer allowed.
(It just doesn't work otherwise.)
2004-03-11 17:18:59 +01:00
pem@mysql.com
91cc4b288e
Merge mysql.com:/usr/local/bk/mysql-5.0
...
into mysql.com:/home/pem/work/mysql-5.0
2004-03-02 16:01:02 +01:00
pem@mysql.comhem.se
1631ba625f
Fixed BUG#2777: Stored procedure doesn't observe definer's rights.
...
SQL SECURITY DEFINER must enforce reduced rights too, not just additional rights.
2004-03-02 11:52:19 +01:00
dlenev@brandersnatch.localdomain
3c58ae9e74
Fixed small race condition, when global query_id was modified
...
without proper locking.
2004-03-01 09:15:33 +03:00
pem@mysql.comhem.se
b205759949
WL#1366: Use the schema (db) associated with an SP.
...
Phase 1: Introduced sp_name class, for qualified name support.
2004-02-17 17:36:53 +01:00
pem@mysql.com
786e19e524
Merge mysql.com:/usr/local/bk/mysql-5.0
...
into mysql.com:/home/pem/work/mysql-5.0
2004-02-17 13:54:40 +01:00
pem@mysql.com
5f5da75c65
Merge mysql.com:/usr/local/bk/mysql-5.0
...
into mysql.com:/home/pem/work/mysql-5.0
2004-02-16 12:47:47 +01:00
lenz@mysql.com
1be033f62c
Merge lgrimmer@build.mysql.com:/home/bk/mysql-5.0
...
into mysql.com:/space/my/mysql-5.0
2004-02-16 12:10:54 +01:00
pem@mysql.comhem.se
8f410d5165
Post-merge fix.
2004-02-13 18:28:58 +01:00
pem@mysql.com
5faf244b30
Merge mysql.com:/home/pem/work/mysql-4.1
...
into mysql.com:/home/pem/work/mysql-5.0-merge
2004-02-13 17:39:00 +01:00
bar@bar.intranet.mysql.r18.ru
d0b456fead
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-13 18:04:08 +04:00
hf@deer.(none)
345dc4d1ab
This line missed in the fix #2208
2004-02-13 18:04:07 +04: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
konstantin@mysql.com
b865fb1cf3
manual merge, bug #2247
2004-02-13 00:50:03 +03:00
vva@eagle.mysql.r18.ru
c57ca85da5
fixed mistake after merge in mysql-test/r/mysqldump.result
2004-02-13 01:50:02 +04: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
pem@mysql.com
26955036ef
Merge mysql.com:/usr/local/bk/mysql-5.0
...
into mysql.com:/home/pem/work/mysql-5.0
2004-02-12 13:52:10 +01:00
hf@deer.(none)
0ac37473f9
Merge abotchkov@bk-internal.mysql.com:/home/bk/mysql-4.1
...
into deer.(none):/home/hf/work/mysql-4.1.1438
2004-02-12 16:50:27 +04:00
hf@deer.(none)
5e4a5cb44c
Fix for #1438 (mysql_info always returns 0)
2004-02-12 16:47:57 +04: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
lenz@mysql.com
7ba5f6f817
Merge lgrimmer@build.mysql.com:/home/bk/mysql-5.0
...
into mysql.com:/space/my/mysql-5.0
2004-02-12 12:50:47 +01:00
pem@mysql.comhem.se
f9e73c7716
Post-merge fixes.
2004-02-11 18:21:55 +01:00
dlenev@mysql.com
8e6a2e98ae
Merge bk-internal.mysql.com:/home/bk/mysql-4.1
...
into mysql.com:/home/dlenev/src/mysql-4.1-bg2248
2004-02-11 16:09:33 +03: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
hf@deer.(none)
f347208ac9
Addition to the fix for #2208
...
Made code shorter and more correct
2004-02-11 16:35:56 +04:00
dlenev@mysql.com
d38c4fcad0
Manual merge.
2004-02-11 15:10:54 +03:00
guilhem@mysql.com
590652a1bb
Merge gbichot@213.136.52.20:/home/bk/mysql-4.1
...
into mysql.com:/home/mysql_src/mysql-4.1
2004-02-11 12:33:25 +01: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
bar@bar.intranet.mysql.r18.ru
251bf4ab85
mysqlimport.c, mysqldump.c, mysqlcheck.c, mysql.cc:
...
No needs to load charset index if the character set is build-in.
2004-02-11 15:15:39 +04:00
dlenev@mysql.com
ef5652686d
Merge bk-internal.mysql.com:/home/bk/mysql-4.1
...
into mysql.com:/home/dlenev/src/mysql-4.1-bg2248
2004-02-11 12:09:48 +03:00