- 10 Sep, 2004 6 commits
-
-
bell@sanja.is.com.ua authored
-
bell@sanja.is.com.ua authored
-
bell@sanja.is.com.ua authored
into sanja.is.com.ua:/home/bell/mysql/bk/work-show-5.0
-
bell@sanja.is.com.ua authored
-
pem@mysql.comhem.se authored
Dropping the table was not the real problem, the problem was with errors occuring within error handlers.
-
dlenev@brandersnatch.localdomain authored
Added previously missing sql_trigger.cc file to embedded library.
-
- 09 Sep, 2004 10 commits
-
-
bell@sanja.is.com.ua authored
into sanja.is.com.ua:/home/bell/mysql/bk/work-show-5.0
-
bell@sanja.is.com.ua authored
-
dlenev@mysql.com authored
into mysql.com:/home/dlenev/src/mysql-5.0-1218-a
-
dlenev@brandersnatch.localdomain authored
-
pem@mysql.comhem.se authored
-
dlenev@mysql.com authored
-
bell@sanja.is.com.ua authored
-
monty@mysql.com authored
-
monty@mysql.com authored
-
monty@mysql.com authored
Fixed (together with Guilhem) bugs in mysqlbinlog regarding --offset Prefix addresses with 0x for easier comparisons of debug logs Fixed problem where MySQL choosed index-read even if there would be a much better range on the same index This fix changed some 'index' queries to 'range' queries in the test suite Don't create 'dummy' WHERE clause for trivial WHERE clauses where we can remove the WHERE clause. This fix removed of a lot of 'Using where' notes in the test suite. Give NOTE instead of WARNING if table/function doesn't exists when using DROP IF EXISTS Give NOTE instead of WARNING for safe field-type conversions
-
- 08 Sep, 2004 5 commits
-
-
dlenev@brandersnatch.localdomain authored
After review and after merge fixes.
-
pem@mysql.comhem.se authored
Easy to prevent crash, but the question was how to treat this case? We ended up implementing the "global" SPs (i.e. with no associated db), which were planned but left unresolved when SPs moved into dbs. So now things like "call .p()" work too.
-
pem@mysql.comhem.se authored
Althought techically not a but (as it's functioning as designed), it was decided that the design should be changed. Some users have a problem with dates being '0000-00-00' and the SQL standard specifies that the modification date should be the same as the creation date at creation.
-
dlenev@mysql.com authored
-
bell@sanja.is.com.ua authored
-
- 07 Sep, 2004 6 commits
-
-
bell@sanja.is.com.ua authored
-
bell@sanja.is.com.ua authored
-
pem@mysql.comhem.se authored
-
bell@sanja.is.com.ua authored
-
dlenev@brandersnatch.localdomain authored
Mostly needed for Monty for him getting notion what needed for triggers from new .FRM format. Things to be done: - Right placement of trigger's invocations - Right handling of errors in triggers (including transaction rollback) - Support for priviliges - Right handling of DROP/RENAME table (hope that it will be handled automatically with merging of .TRG into .FRM file) - Saving/restoring some information critical for trigger creation and replication with their definitions (e.g. sql_mode, creator, ...) - Replication Already has some known bugs so probably not for general review.
-
bell@sanja.is.com.ua authored
-
- 06 Sep, 2004 6 commits
-
-
cps@silver_beast.(none) authored
into silver_beast.(none):/home/cps/mysql/devel/im/default_patch/mysql-5.0
-
bell@sanja.is.com.ua authored
-
cps@silver_beast.(none) authored
into silver_beast.(none):/home/cps/mysql/devel/im/default_patch/mysql-5.0
-
cps@silver_beast.(none) authored
final 0 of the string.
-
monty@mysql.com authored
(Includes merge of arena code in 4.1 and 5.0)
-
bell@sanja.is.com.ua authored
-
- 05 Sep, 2004 2 commits
-
-
cps@silver_beast.(none) authored
into silver_beast.(none):/home/cps/mysql/devel/im/default_patch/mysql-5.0
-
cps@silver_beast.(none) authored
-
- 04 Sep, 2004 5 commits
-
-
monty@mysql.com authored
-
bell@sanja.is.com.ua authored
-
monty@mysql.com authored
-
bell@sanja.is.com.ua authored
into sanja.is.com.ua:/home/bell/mysql/bk/work-5.0
-
monty@mysql.com authored
-