- 04 Sep, 2007 2 commits
-
-
df@pippilotta.erinye.com authored
into pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-5.0-build
-
df@pippilotta.erinye.com authored
into pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-5.0-build-work
-
- 29 Aug, 2007 7 commits
-
-
kent@kent-amd64.(none) authored
into mysql.com:/home/kent/bk/tmp/mysql-5.0-build
-
kent@mysql.com/kent-amd64.(none) authored
server-tools/instance-manager/pack.c server-tools/instance-manager/password.c server-tools/instance-manager/net_serv.cc Deleted BitKeeper soft links not needed
-
kent@kent-amd64.(none) authored
into mysql.com:/home/kent/bk/tmp/mysql-5.0-build
-
kent@mysql.com/kent-amd64.(none) authored
Deleted BitKeeper soft links not needed
-
kent@mysql.com/kent-amd64.(none) authored
Link with library "udf_example" depends on, needed for nmake libmysql.c: DBUG_ENTER need to be in declaration section
-
kent@kent-amd64.(none) authored
into mysql.com:/home/kent/bk/tmp/mysql-5.0-build
-
kent@mysql.com/kent-amd64.(none) authored
Flag changed name in icc 10
-
- 28 Aug, 2007 3 commits
-
-
mleich@four.local.lan authored
Bug#30418 "datadict" tests (all engines) fail: Dependency on the host name for ordering Bug#30420 "datadict" tests (all engines) fail: Release build has help tables loaded Bug#30438 "{memory,myisam,ndb}__datadict" tests fail: Use "InnoDB" without checking Bug#30440 "datadict" tests (all engines) fail: Character sets depend on configuration Attention: Only the build team can check if Bug#30440 is really fixed.
-
df@pippilotta.erinye.com authored
-
df@pippilotta.erinye.com authored
-
- 27 Aug, 2007 2 commits
-
-
df@pippilotta.erinye.com authored
-
into mysql.com:/data0/mysqldev/my/build-200708231546-5.0.48/mysql-5.0-release
-
- 25 Aug, 2007 1 commit
-
-
into a88-113-38-195.elisa-laajakaista.fi:/home/my/bk/mysql-5.0-marvel
-
- 24 Aug, 2007 9 commits
-
-
joerg@trift2. authored
into trift2.:/MySQL/M50/push-5.0
-
joerg@trift2. authored
1) Ensure "init_db.sql" and "test_db-sql" really get built. 2) Ensure the "*.def" files with NetWare linker options get distributed to the proper directories.
-
into mysql.com:/data0/mysqldev/my/build-200708231546-5.0.48/mysql-5.0-release
-
into a88-113-38-195.elisa-laajakaista.fi:/home/my/bk/mysql-5.0-marvel
-
into mysql.com:/data0/mysqldev/my/build-200708231546-5.0.48/mysql-5.0-release
-
joerg@trift2. authored
into trift2.:/MySQL/M50/push-5.0
-
joerg@trift2. authored
into trift2.:/MySQL/M50/push-5.0
-
joerg@trift2. authored
-
df@pippilotta.erinye.com authored
into pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-5.0-build
-
- 23 Aug, 2007 4 commits
-
-
gshchepa@bk-internal.mysql.com authored
into bk-internal.mysql.com:/users/gshchepa/mysql-5.0-opt
-
joerg@trift2. authored
into trift2.:/MySQL/M50/push-5.0
-
df@pippilotta.erinye.com authored
into pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-5.0.48
-
df@pippilotta.erinye.com authored
into pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-5.0.48
-
- 22 Aug, 2007 4 commits
-
-
joerg@trift2. authored
1) We do not provide the "isam" table handler in 5.0 and up (different from "myisam" !), so we do not need the ".def" files for the "isam"-specific tools. 2) Use "basename" to get the base name of a file, not a harder-to-read sed expression.
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/5.0-opt
-
jani@hynda.mysql.fi authored
into hynda.mysql.fi:/home/my/mysql-5.0-marvel
-
gshchepa/uchum@gleb.loc authored
Killing a SELECT query with KILL QUERY or KILL CONNECTION causes a server crash if the query cache is enabled. Normal evaluation of a query may be interrupted by the KILL QUERY/CONNECTION statement, in this case the mysql_execute_command function returns TRUE, and the thd->killed flag has true value. In this case the result of the query may be cached incompletely (omitting call to query_cache_insert inside the net_real_write function), and next call to query_cache_end_of_result may lead to server crash. Thus, the query_cache_end_of_result function has been modified to abort query cache in the case of killed thread.
-
- 21 Aug, 2007 8 commits
-
-
joerg@trift2. authored
into trift2.:/MySQL/M50/push-5.0
-
jani@hynda.mysql.fi authored
into hynda.mysql.fi:/home/my/mysql-5.0-marvel
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/5.0-opt
-
thek@adventure.(none) authored
into adventure.(none):/home/thek/Development/cpp/mysql-5.0-runtime
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/5.0-opt
-
gluh@mysql.com/eagle.(none) authored
-
gluh@eagle.(none) authored
into mysql.com:/home/gluh/MySQL/Merge/5.0-opt
-
thek@adventure.(none) authored
Although the query cache doesn't support retrieval of statements containing column level access control, it was still possible to cache such statements thus wasting memory. This patch extends the access control check on the target tables to avoid caching a statement with column level restrictions. Views are excepted and can be cached but only retrieved by super user account.
-