jimw@mysql.com
2904f4d0a4
Merge mysql.com:/home/jimw/my/mysql-5.0-8444
...
into mysql.com:/home/jimw/my/mysql-5.0-clean
2005-03-01 15:25:17 -08:00
pem@mysql.comhem.se
54a2448bce
Fixed BUG#8760: Stored Procedures: Invalid SQLSTATE is allowed in
...
a DECLARE ? HANDLER FOR stmt.
2005-02-28 18:07:06 +01:00
paul@snake-hub.snake.net
c2507d88f5
Fix badly spelled symbol.
2005-02-23 13:15:03 -06:00
jimw@mysql.com
7baab10ebb
Include a timestamp on the 'ready for connections' message by printing it
...
using sql_print_information() instead of directly to stdout. (Bug #8444 )
2005-02-22 18:09:35 -08:00
serg@serg.mylan
fd828e5b4d
manually merged
2005-02-14 21:50:09 +01:00
pem@mysql.comhem.se
2c26ebe359
WL#2130: Table locking for stored FUNCTIONs
...
Collect all tables and SPs refered by a statement, and open all tables
with an implicit LOCK TABLES. Do find things refered by triggers and views,
we open them first (and then repeat this until nothing new is found), before
doing the actual lock tables.
2005-02-08 20:52:50 +01:00
serg@serg.mylan
852f2e0aba
small Makefile.am cleanup
...
clean: targets removed
generated *.h files moved to include/
2005-01-28 17:14:03 +01:00
serg@serg.mylan
3c5060981f
query_id and my_xid -> ulonglong
...
fix for binlog+autocommit+tclog
comments, style fixes
2005-01-27 22:38:56 +01:00
ram@gw.mysql.r18.ru
84f0b1eeee
Merge rkalimullin@bk-internal.mysql.com:/home/bk/mysql-5.0
...
into gw.mysql.r18.ru:/usr/home/ram/work/5.0.b6999
2005-01-21 12:10:19 +04:00
bar@mysql.com
5ed1b14464
errmsg.txt:
...
Adding Shift-JIS error messages
for Japanese Windows distributions.
Thanks to Serg for help with a perl program
to merge 4.1 messages into 5.0 format :)
2005-01-20 15:33:21 +04:00
bar@mysql.com
07be090e6e
errmsg.txt:
...
Minor fix after character set conversion.
2005-01-20 13:08:16 +04:00
bar@mysql.com
1650728655
errmsg.txt:
...
new file
2005-01-20 12:37:02 +04:00
ram@gw.mysql.r18.ru
92545cb3a9
ER_WARN_DATA_TRUNCATED replaced with WARN_DATA_TRUNCATED.
2005-01-19 16:24:06 +04:00
ram@gw.mysql.r18.ru
c24c023e8c
A fix (bug #6999 : Traditional: Wrong SQLSTATE returned for string truncation).
2005-01-19 12:04:35 +04:00
serg@serg.mylan
1034677f94
XA (not completely polished out yet)
2005-01-16 13:16:23 +01:00
anjuta@arthur.local
224fcd4717
Merge
2005-01-13 19:14:10 +02:00
paul@kite-hub.kitebird.com
231632e34f
user_limits.result:
...
Fix test result affected by error message rewording.
errmsg.txt:
Reword error messages.
set_var.cc:
Reorder variables.
mysqld.cc:
Reorder options.
2005-01-12 20:38:05 -06:00
shuichi@mysql.com
852d74a68e
renamed charset name 'eucjp_ms' to 'eucjpms'
2005-01-12 02:58:15 -08:00
shuichi@mysql.com
3126e82291
added new character set - cp932, eucjp_ms
2005-01-11 17:45:36 -08:00
acurtis@pcgem.rdg.cyberkinetica.com
b1e30904d5
WL#925 - Privileges for stored routines
...
Implement fine-grained control over access to stored procedures
Privileges are cached (same way as existing table/column privs)
2004-12-23 10:46:24 +00:00
anjuta@arthur.local
f56efde6a3
Merge anna@bk-internal.mysql.com:/home/bk/mysql-5.0
...
into arthur.local:/my/mysql-5.0-clean
2004-12-17 22:16:30 +02:00
lenz@mysql.com
750f3937d7
- typo fix
2004-12-17 18:00:05 +01:00
lenz@mysql.com
63534a3d98
- make sure to include sql/share/errmsg.txt into the source distribution
2004-12-17 17:46:46 +01:00
anjuta@arthur.local
31d51d04a9
Removed several erroneous error messages in different languages in errmsg.txt
2004-12-17 01:32:06 +02:00
anjuta@arthur.local
44cfef92d1
Removed incorrect messages; fixed serbian messages.
2004-12-16 21:21:13 +02:00
bar@mysql.com
f6b1f5dec1
errmsg.txt:
...
My attempt N3
2004-12-16 18:44:38 +04:00
gluh@gluh.mysql.r18.ru
6372efa7da
Fix for bug#7212: information_schema: "Can't find file" errors if storage engine gone(after review)
2004-12-16 16:31:36 +03:00
anjuta@arthur.local
53db34f992
Added missing errmsg.txt
2004-12-13 23:28:24 +02:00
anjuta@arthur.local
f9451974be
WL#1051, more maintanable error messages.
2004-12-13 22:51:54 +02:00
serg@serg.mylan
319546d5f0
create/drop/rename user cleanup
2004-11-27 23:07:30 +01:00
ingo@mysql.com
cb53411b47
WL#2050 - CREATE USER and DROP USER and RENAME USER
...
Added new commands CREATE USER and RENAME USER.
Changed behaviour of DROP USER.
Changed an error messages for the new commands.
2004-11-25 21:55:49 +01:00
bell@sanja.is.com.ua
072d38eb12
merge
2004-11-21 20:08:12 +02:00
bell@sanja.is.com.ua
8ded2093e6
postreview changes
2004-11-21 16:35:42 +02:00
bell@sanja.is.com.ua
d76db8b999
marge
2004-11-13 19:45:36 +02:00
bell@sanja.is.com.ua
7210195f1e
now my_printf_error is not better then my_error, but my_error call is shorter
...
used only one implementation of format parser of (printf)
fixed multistatement
2004-11-13 19:35:51 +02:00
monty@mysql.com
addd1a0da8
Merge with 4.1
2004-11-12 19:58:24 +02:00
serg@serg.mylan
e20732b073
typos in error messages fixed
2004-11-12 16:41:53 +01:00
bell@sanja.is.com.ua
1555469b64
merge
2004-11-12 15:36:31 +02:00
bell@sanja.is.com.ua
0ef0b030a5
merge
2004-11-11 21:18:10 +02:00
guilhem@mysql.com
09da85338c
no new message in 4.1 (causes merge issues with 5.0). Using ER_UNKNOW_ERROR and hardcoded message string instead.
2004-11-11 00:00:17 +01:00
guilhem@mysql.com
6cd218cc56
WL#1596 "make mysqldump --master-data --single-transaction able to do online dump of InnoDB AND report reliable
...
binlog coordinates corresponding to the dump".
The good news is that now mysqldump can be used to get an online backup of InnoDB *which works for
point-in-time recovery and replication slave creation*. Formerly, mysqldump --master-data --single-transaction
used to call in fact mysqldump --master-data, so the dump was not an online dump (took big lock all time of dump).
The only lock which is now taken in this patch is at the beginning of the dump: mysqldump does:
FLUSH TABLES WITH READ LOCK; START TRANSACTION WITH CONSISTENT SNAPSHOT; SHOW MASTER STATUS; UNLOCK TABLES;
so the lock time is in fact the time FLUSH TABLES WITH READ LOCK takes to return (can be 0 or very long, if
a table is undergoing a huge update).
I have done some more minor changes listed in the paragraph of mysqldump.c.
WL#2237 "WITH CONSISTENT SNAPSHOT clause for START TRANSACTION":
it's a START TRANSACTION which additionally starts a consistent read on all
capable storage engine (i.e. InnoDB). So, can serve as a replacement for
BEGIN; SELECT * FROM some_innodb_table LIMIT 1; which starts a consistent read too.
2004-11-10 17:56:45 +01:00
monty@mysql.com
afbe601302
merge with 4.1
2004-10-29 19:26:52 +03:00
bell@sanja.is.com.ua
dff05eb951
merge
2004-10-28 11:02:48 +03:00
pem@mysql.comhem.se
2c428ca09d
Fixed BUG#6030: Stored procedure has no appropriate DROP privilege.
...
...and no ALTER privilege either.
For now, only the definer and root can drop or alter an SP.
2004-10-22 20:29:06 +02:00
bell@sanja.is.com.ua
4714a6e744
errors without code removed
...
net_printf/send_error calls replaced by my_error family functions
-1/1 (sent/unsent) error reporting removed
(WL#2133)
2004-10-20 04:04:37 +03:00
bell@sanja.is.com.ua
a78f817d20
merge
2004-10-05 13:41:51 +03:00
monty@mishka.local
5eca078b19
merge
2004-10-05 01:10:23 +03:00
bell@sanja.is.com.ua
9062e99ee6
merge
2004-10-04 13:56:48 +03:00
monty@mishka.local
be4ca46fbe
More fixes for strict mode:
...
More tests.
Better error messages.
Fixed bug when checking if we updated all needed columns for INSERT.
Give an error if we encounter a wrong float value during parsing.
Don't print DEFAULT for columns without a default value in SHOW CREATE/SHOW FIELDS.
Fixed UPDATE IGNORE when using STRICT mode.
2004-10-02 22:20:08 +03:00
bell@sanja.is.com.ua
013512abab
merge
2004-09-29 17:10:17 +03:00