- 13 Dec, 2005 1 commit
-
-
ramil@mysql.com authored
-
- 12 Dec, 2005 2 commits
-
-
ramil@mysql.com authored
-
ramil@mysql.com authored
into mysql.com:/usr/home/ram/work/mysql-5.0-release
-
- 11 Dec, 2005 2 commits
-
-
kent@mysql.com authored
into mysql.com:/Users/kent/mysql/bk/mysql-5.0-release
-
kent@mysql.com authored
Removed Visual Studio 6 project files, as they are not maintained
-
- 09 Dec, 2005 5 commits
-
-
ramil@mysql.com authored
-
ramil@mysql.com authored
-
kent@mysql.com authored
into mysql.com:/Users/kent/mysql/bk/mysql-5.0-release
-
kent@mysql.com authored
Removed --text from grep, not portable
-
knielsen@mysql.com authored
-
- 08 Dec, 2005 4 commits
-
-
knielsen@mysql.com authored
into mysql.com:/usr/local/mysql/mysql-5.0-release
-
kent@mysql.com authored
into mysql.com:/Users/kent/mysql/bk/mysql-5.0-release
-
kent@mysql.com authored
Bug#14960, reverted code to make symdir work on Windows symlink.test: Disabled test case on Windows
-
knielsen@mysql.com authored
-
- 07 Dec, 2005 10 commits
-
-
dlenev@mysql.com authored
-
jimw@mysql.com authored
into mysql.com:/home/jimw/my/mysql-5.0-release
-
dlenev@mysql.com authored
current SP tables locking make impossible view security" with main tree.
-
dlenev@mysql.com authored
into mysql.com:/home/dlenev/src/mysql-5.0-bg11555-2
-
dlenev@mysql.com authored
into mysql.com:/home/dlenev/src/mysql-5.0-bg11555-2
-
dlenev@mysql.com authored
impossible view security". We should not expose names of tables which are explicitly or implicitly (via routine or trigger) used by view even if we find that they are missing. So during building of list of prelocked tables for statement we track which routines (and therefore tables for these routines) are used from views. We mark elements of LEX::routines set which correspond to routines used in views by setting Sroutine_hash_entry::belong_to_view member to point to TABLE_LIST object for topmost view which uses routine. We propagate this mark to all routines which are used by this routine and which we add to this set. We also mark tables used by such routine which we add to the list of tables for prelocking as belonging to this view.
-
serg@serg.mylan authored
-
timour@mysql.com authored
into mysql.com:/home/timka/mysql/src/5.0-2486
-
jimw@mysql.com authored
-
jimw@mysql.com authored
into mysql.com:/home/jimw/my/mysql-5.0-clean
-
- 06 Dec, 2005 12 commits
-
-
jimw@mysql.com authored
statement that generated a warning. (Bug #15510)
-
jimw@mysql.com authored
into mysql.com:/home/jimw/my/mysql-5.0-clean
-
konstantin@mysql.com authored
prepared statement execute
-
serg@serg.mylan authored
into serg.mylan:/usr/home/serg/Abk/mysql-5.0
-
aivanov@mysql.com authored
into mysql.com:/home/alexi/innodb-ss/mysql-5.0-ss52
-
aivanov@mysql.com authored
to crash". Changes from snapshot innodb-5.0-ss52. Note that buf_block_t::index should be protected by btr_search_latch or an s-latch or x-latch on the index page. btr_search_drop_page_hash_index(): Read block->index while holding btr_search_latch and use the cached value in the loop. Remove some redundant assertions. Also fix 13778. When FOREIGN_KEY_CHECKS=0 we still need to check that datatypes between foreign key references are compatible. Also added test cases to 9802.
-
serg@serg.mylan authored
-
timour@mysql.com authored
into mysql.com:/home/timka/mysql/src/5.0-2486
-
pem@mysql.com authored
Changed variable type and added comment in sp.c.
-
pem@mysql.com authored
into mysql.com:/usr/home/pem/bug14233/mysql-5.0
-
stewart@mysql.com authored
into mysql.com:/home/stewart/Documents/MySQL/5.0/bug15512
-
stewart@mysql.com authored
-
- 05 Dec, 2005 4 commits
-
-
serg@serg.mylan authored
-
joerg@mysql.com authored
into mysql.com:/M50/mysql-5.0
-
mleich@mysql.com authored
into mysql.com:/home/matthias/Arbeit/mysql-5.0/src-Z
-
joerg@mysql.com authored
-