- 09 Oct, 2007 2 commits
-
-
anozdrin/alik@station. authored
-
anozdrin/alik@station. authored
into station.:/mnt/raid/alik/MySQL/devel/5.1-rt-merged
-
- 08 Oct, 2007 1 commit
-
-
malff@lambda.hsd1.co.comcast.net. authored
-
- 07 Oct, 2007 1 commit
-
-
kostja@bodhi.(none) authored
into bodhi.(none):/opt/local/work/mysql-5.1-runtime
-
- 05 Oct, 2007 1 commit
-
-
anozdrin/alik@station. authored
when used in a VIEW. The problem was that wrong function (create_tmp_from_item()) was used to create a temporary field for Item_func_sp. The fix is to use create_tmp_from_field().
-
- 04 Oct, 2007 5 commits
-
-
joerg@trift2. authored
into trift2.:/MySQL/M51/push-5.1
-
joerg@trift2. authored
into trift2.:/MySQL/M50/push-5.0
-
jperkin@production.mysql.com authored
into production.mysql.com:/usersnfs/jperkin/bk/build/5.1
-
jperkin@production.mysql.com authored
into production.mysql.com:/usersnfs/jperkin/bk/bug-27692/5.0
-
jperkin@production.mysql.com authored
were accidentally removed during a previous rototill of this code. Fixes bug#27692. While it can be argued we should strive to provide a 'secure by default' installation, this happens to be the setup currently documented in the manual as the default, so defer changes that improve security out of the box to a co-ordinated effort later on. For now, make a note about the test databases and anonymous user in mysql_install_db and recommend that mysql_secure_installation be ran for users wishing to remove these defaults. [..re-commit of previously lost change..]
-
- 02 Oct, 2007 1 commit
-
-
Updated variable size arrays to use vector like Jonas did for 5.1 so that my build would not break
-
- 01 Oct, 2007 6 commits
-
-
kent@kent-amd64.(none) authored
into mysql.com:/home/kent/bk/make-install/mysql-5.1-build
-
kent@mysql.com/kent-amd64.(none) authored
Added special handling of "mysql_install_db" and "mysql.server" scripts, find executables relative to the current directory.
-
anozdrin/alik@station. authored
succ. mysql_change_user() call. Use 2 bytes for character set number.
-
joerg@trift2. authored
into trift2.:/MySQL/M51/push-5.1
-
joerg@trift2. authored
into trift2.:/MySQL/M50/push-5.0
-
joerg@trift2. authored
Add the cleanup by dropping the database 'track' in test "rpl_bug31076".
-
- 30 Sep, 2007 1 commit
-
-
anozdrin/alik@station. authored
-
- 29 Sep, 2007 7 commits
-
-
joerg@trift2. authored
into trift2.:/MySQL/M51/push-5.1
-
anozdrin/alik@station. authored
-
davi@moksha.local authored
into moksha.local:/Users/davi/mysql/push/bugs/21136-regression
-
davi@moksha.local authored
caused a few tests to fail because the thd->extra_lock wasn't being set to NULL after the table was unlocked. This poses a serious problem because later attempts to access thd->extra_lock (now a dangling pointer) will probably result in a crash (undefined behavior) -- and that's what actually happens in some test cases. The solution is to set the select_create::m_plock pointee to NULL, which means that thd->extra_lock is set to NULL when the lock data is not for a temporary table.
-
df@pippilotta.erinye.com authored
into pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-5.1-build
-
df@pippilotta.erinye.com authored
into pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-5.1-build
-
df@pippilotta.erinye.com authored
-
- 28 Sep, 2007 7 commits
-
-
anozdrin/alik@station. authored
into station.:/mnt/raid/alik/MySQL/devel/bug-30472/5.1-rt-bug30472
-
davi@moksha.local authored
the sql_class.h file.
-
davi@moksha.local authored
When CREATE TEMPORARY TABLE .. SELECT is invoked from a stored function which in turn is called from CREATE TABLE SELECT causes a memory leak because the inner create temporary table overrides the outter extra_lock reference when locking the table. The solution is to simply not overrride the extra_lock by only using the extra_lock for a non-temporary table lock.
-
anozdrin/alik@station. authored
insert_id after succ. mysql_change_user() call. See also WL 4066. This bug reveals two problems: - the problem on the client side which was described originally; - the problem in protocol / the server side: connection context on client and server should be like after mysql_real_connect() and be consistent. The server however just resets character set variables to the global defaults. The fix seems to be as follows: - extend the protocol so that the client be able to send character set information in COM_CHANGE_USER command; - change the server so that it understands client character set in the command; - change the client: - reset character set to the default value (which has been read from the configuration); - send character set in COM_CHANGE_USER command.
-
joerg@trift2. authored
into trift2.:/MySQL/M51/push-5.1 This is mysql-5.1.22-rc.
-
joerg@trift2. authored
Bug #30759 mysql_install_db fails to set $extra_bindir properly in all cases.
-
anozdrin/alik@station. authored
insert_id after succ. mysql_change_user() call. Supply a correct packet length to dispatch command.
-
- 27 Sep, 2007 8 commits
-
-
kent@kent-amd64.(none) authored
into mysql.com:/home/kent/bk/make-dist-stable/mysql-5.1-build
-
kent@mysql.com/kent-amd64.(none) authored
Handle pstack like other optional directories Check if a directory exists relative to $srcdir
-
joerg@trift-lap.fambruehe authored
into trift-lap.fambruehe:/MySQL/M51/antony-5.1
-
kent@mysql.com/kent-amd64.(none) authored
Use custom 'pkgduppdir' mysql.server.sh: The server is installed in 'libexecdir'
-
kent@kent-amd64.(none) authored
into mysql.com:/home/kent/bk/make-install/mysql-5.1-build
-
df@pippilotta.erinye.com authored
into pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-5.1-build
-
df@pippilotta.erinye.com authored
into pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-5.1-build
-
df@pippilotta.erinye.com authored
into pippilotta.erinye.com:/shared/home/df/mysql/build/mysql-5.0-build
-