- 06 Sep, 2005 4 commits
-
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.0
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.0
-
msvensson@neptunus.(none) authored
- Update test cases
-
ndbdev@dl145b.mysql.com authored
-
- 05 Sep, 2005 22 commits
-
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.0
-
msvensson@neptunus.(none) authored
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.0
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-4.1
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/bug12959/my50-bug12959
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/bug12959/my41-bug12959
-
tulin@dl145b.mysql.com authored
into dl145b.mysql.com:/home/ndbdev/mysql-4.1
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/bug12959/my50-bug12959
-
msvensson@neptunus.(none) authored
-
tulin@dl145b.mysql.com authored
added parseable printout in ndb_restore
-
evgen@moonbone.local authored
Test case for bug #12859 group_concat in subquery cause incorrect not null.
-
ramil@mysql.com authored
into mysql.com:/usr/home/ram/work/mysql-5.0
-
tulin@dl145b.mysql.com authored
-
ramil@mysql.com authored
into mysql.com:/usr/home/ram/work/4.1.b4214
-
ramil@mysql.com authored
-
msvensson@neptunus.(none) authored
-
msvensson@neptunus.(none) authored
TRASH macro confliciting with TRASH in my_sys.h
-
joerg@mysql.com authored
-
joerg@mysql.com authored
-
tulin@dl145b.mysql.com authored
-
tulin@dl145b.mysql.com authored
+ added option to dumpe rest of page after exnd of data
-
jan@hundin.mysql.fi authored
into hundin.mysql.fi:/home/jan/new/mysql-5.0
-
- 04 Sep, 2005 4 commits
-
-
heikki@hundin.mysql.fi authored
Fix bug #12308 : do not roll back the whhole transaction in a lock wait timeout error, just roll back the latest SQL statement; note that the locks set in the latest SQL statements remain, as InnoDB does not know what locks were set in which SQL statement
-
brian@zim.(none) authored
-
heikki@hundin.mysql.fi authored
Better comments about auto-inc and SHOW TABLE STATUS
-
heikki@hundin.mysql.fi authored
Fix bug #12973 : set the table handle field auto_increment_value if ::info() is called with the flag HA_STATUS_AUTO
-
- 03 Sep, 2005 7 commits
-
-
jimw@mysql.com authored
into mysql.com:/home/jimw/my/mysql-5.0-clean
-
jimw@mysql.com authored
into mysql.com:/home/jimw/my/mysql-5.0-clean
-
heikki@hundin.mysql.fi authored
Add a sanity check to page_rec_is_comp; a new univ.i macro UNIV_RELEASE_NOT_YET_STABLE controls such sanity checks that we will remove after the release is stable enough
-
heikki@hundin.mysql.fi authored
Fix a wrong debug assert in the previous patch
-
heikki@hundin.mysql.fi authored
Add more comments to row_search_for_mysql() and remove the ugly double use of the variable rec in that function
-
heikki@hundin.mysql.fi authored
into hundin.mysql.fi:/home/heikki/mysql-5.0
-
jonas@eel.(none) authored
into eel.(none):/home/jonas/src/mysql-4.1-push
-
- 02 Sep, 2005 3 commits
-
-
konstantin@mysql.com authored
into mysql.com:/home/kostja/mysql/mysql-5.0-dsql3
-
konstantin@mysql.com authored
The idea of the patch is to separate statement processing logic, such as parsing, validation of the parsed tree, execution and cleanup, from global query processing logic, such as logging, resetting priorities of a thread, resetting stored procedure cache, resetting thread count of errors and warnings. This makes PREPARE and EXECUTE behave similarly to the rest of SQL statements and allows their use in stored procedures. This patch contains a change in behaviour: until recently for each SQL prepared statement command, 2 queries were written to the general log, e.g. [Query] prepare stmt from @stmt_text; [Prepare] select * from t1 <-- contents of @stmt_text The chagne was necessary to prevent [Prepare] commands from being written to the general log when executing a stored procedure with Dynamic SQL. We should consider whether the old behavior is preferrable and probably restore it. This patch refixes Bug#7115, Bug#10975 (partially), Bug#10605 (various bugs in Dynamic SQL reported before it was disabled).
-
heikki@hundin.mysql.fi authored
Fix bug #12947 : a consistent read could return inconsistent results; this bug was introduced in 5.0.5
-