- 29 May, 2006 2 commits
-
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.0-maint
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.0-maint
-
- 24 May, 2006 2 commits
-
-
elliot@mysql.com authored
into mysql.com:/home/emurphy/src/bk-clean/mysql-5.0-bug19394
-
svoj@april.(none) authored
into april.(none):/home/svoj/devel/mysql/BUG18233/mysql-5.0
-
- 23 May, 2006 16 commits
-
-
cmiller@zippy.(none) authored
into zippy.(none):/home/cmiller/work/mysql/mysql-5.0--bug11151
-
msvensson@neptunus.(none) authored
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.0
-
cmiller@zippy.(none) authored
not transaction-safe for stored procedures. Related to Bug#11151.
-
msvensson@neptunus.(none) authored
-
msvensson@neptunus.(none) authored
-
msvensson@neptunus.(none) authored
-
svoj@april.(none) authored
into april.(none):/home/svoj/devel/mysql/BUG18233/mysql-5.0
-
knielsen@mysql.com authored
into mysql.com:/usr/local/mysql/mysql-5.0
-
msvensson@neptunus.(none) authored
- In function 'handle_grant_struct' when searching the memory structures for an entry to modify, convert all entries here host.hostname is NULL to "" and compare that with the host passed in argument "user_from". - A user created with hostname "" is stored in "mysql.user" table as host="" but when loaded into memory it'll be stored as host.hostname NULL. Specifiying "" as hostname means that "any host" can connect. Thus is's correct to turn on allow_all_hosts when such a user is found. - Review and fix other places where host.hostname may be NULL.
-
msvensson@neptunus.(none) authored
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.0
-
msvensson@neptunus.(none) authored
-
gluh@eagle.intranet.mysql.r18.ru authored
transfer NO_DEFAULT_VALUE_FLAG flag to new field
-
msvensson@neptunus.(none) authored
- Unlock the mutex after looking at rli->events_till_abort - Already fixed in 5.1 so it will be null merged.
-
gluh@eagle.intranet.mysql.r18.ru authored
show view definition to users that have the needed privilleges
-
- 22 May, 2006 10 commits
-
-
igor@rurik.mysql.com authored
into rurik.mysql.com:/home/igor/dev/mysql-5.0-0
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-5.0-main
-
gkodinov@mysql.com authored
into mysql.com:/home/kgeorge/mysql/5.0/B18745
-
knielsen@mysql.com authored
-
igor@rurik.mysql.com authored
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-5.0-main
-
tomas@poseidon.ndb.mysql.com authored
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-5.0-main
-
stewart@mysql.com authored
into mysql.com:/home/stewart/Documents/MySQL/5.0/main
-
gkodinov@mysql.com authored
Moved the InnoDB related test from func_group.test to innodb_mysql.test
-
- 21 May, 2006 4 commits
-
-
holyfoot@mysql.com authored
into mysql.com:/home/hf/work/mysql-5.0.mrg
-
pekka@mysql.com authored
-
igor@rurik.mysql.com authored
into rurik.mysql.com:/home/igor/dev/mysql-5.0-0
-
igor@rurik.mysql.com authored
When a CREATE TABLE command created a table from a materialized view id does not inherit default values from the underlying table. Moreover the temporary table used for the view materialization does not inherit those default values. In the case when the underlying table contained ENUM fields it caused misleading error messages. In other cases the created table contained wrong default values. The code was modified to ensure inheritance of default values for materialized views.
-
- 20 May, 2006 4 commits
-
-
kent@mysql.com authored
-
kent@mysql.com authored
into mysql.com:/Users/kent/mysql/bk/mysql-5.0-new
-
kent@mysql.com authored
-
kent@mysql.com authored
Always compile position independent
-
- 19 May, 2006 2 commits
-
-
jimw@mysql.com authored
into mysql.com:/home/jimw/my/mysql-5.0-clean
-
msvensson@devsrv-b.mysql.com authored
into devsrv-b.mysql.com:/users/msvensson/mysql-5.0
-