- 16 Jul, 2005 8 commits
-
-
konstantin@mysql.com authored
-
konstantin@mysql.com authored
into mysql.com:/media/sda1/mysql/mysql-5.0-merge
-
georg@lmy002.wdf.sap.corp authored
-
georg@lmy002.wdf.sap.corp authored
into lmy002.wdf.sap.corp:/home/georg/work/mysql-5.0
-
bell@sanja.is.com.ua authored
into sanja.is.com.ua:/home/bell/mysql/bk/work-bug6-5.0
-
georg@lmy002.wdf.sap.corp authored
Moved mysql_set_character_set function to client.c Changed function prototype for mysql_set_character_set (as suggested by Konstantin)
-
brian@zim.(none) authored
into zim.(none):/home/brian/mysql/foo-5.0
-
brian@zim.(none) authored
-
- 15 Jul, 2005 32 commits
-
-
konstantin@mysql.com authored
into mysql.com:/opt/local/work/mysql-4.1-root
-
reggie@linux.site authored
into linux.site:/home/reggie/bk/bug7403
-
konstantin@mysql.com authored
of system vars at PREPARE time": implement a special Item to handle system variables. This item substitutes itself with a basic constant containing variable value at fix_fields.
-
evgen@moonbone.local authored
than in previous 4.1.x Wrongly applied optimization were adding NOT NULL constraint which results in rejecting valid rows and reduced result set. The problem was that add_notnull_conds() while checking subquery were adding NOT NULL constraint to left joined table, to which, normally, optimization don't have to be applied.
-
bell@sanja.is.com.ua authored
-
bell@sanja.is.com.ua authored
into sanja.is.com.ua:/home/bell/mysql/bk/work-bug6-5.0
-
bell@sanja.is.com.ua authored
correct value of CURRENT_USER() in SP with "security definer" (BUG#7291)
-
reggie@linux.site authored
into linux.site:/home/reggie/bk/mysql-5.0
-
brian@zim.(none) authored
-
pem@mysql.com authored
-
pem@mysql.com authored
into mysql.com:/home/pem/work/mysql-5.0
-
tomas@poseidon.ndb.mysql.com authored
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-5.0
-
pem@mysql.com authored
using @@var_name in proc Made sure we don't lose the tokenizer state when swapping lex in during SET parsing.
-
pem@mysql.com authored
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-5.0
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-5.0
-
georg@lmy002.wdf.sap.corp authored
test_client_character_set
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-5.0
-
georg@lmy002.wdf.sap.corp authored
into lmy002.wdf.sap.corp:/home/georg/work/mysql-5.0
-
georg@lmy002.wdf.sap.corp authored
When all rows are fetched subsequent calls to mysql_stmt_fetch return now MYSQL_NO_DATA instead of errorcode 1.
-
reggie@linux.site authored
into linux.site:/home/reggie/bk/bug7403
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-4.1-new
-
tomas@poseidon.ndb.mysql.com authored
-
tomas@poseidon.ndb.mysql.com authored
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-4.1-new
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-4.1-release
-
ramil@mysql.com authored
into mysql.com:/usr/home/ram/work/mysql-5.0
-
ramil@mysql.com authored
-
ramil@mysql.com authored
-
tomas@poseidon.ndb.mysql.com authored
+ added close of some fd's + debug prints
-
tomas@poseidon.ndb.mysql.com authored
In 4.1 the connection to the management server _must_ stay, that is how we ensure that the nodeids are reserved correctly
-