- 12 Oct, 2002 1 commit
-
-
Sinisa@sinisa.nasamreza.org authored
-
- 09 Oct, 2002 7 commits
-
-
lenz@mysql.com authored
from manual texi
-
lenz@mysql.com authored
-
serg@serg.mysql.com authored
-
serg@serg.mysql.com authored
into serg.mysql.com:/usr/home/serg/Abk/mysql-4.0
-
serg@serg.mysql.com authored
-
lenz@mysql.com authored
- currently, "make distcheck" fails - this needs to be investigated before the next release
-
lenz@mysql.com authored
into mysql.com:/space/my/mysql-4.0-automake
-
- 08 Oct, 2002 10 commits
-
-
tfr@beta.frontier86.ee authored
into beta.frontier86.ee:/stuff/bk/mysql-4.0
-
tfr@beta.frontier86.ee authored
Contrib overhaul
-
lenz@mysql.com authored
into mysql.com:/space/my/mysql-4.0-automake
-
vva@genie.(none) authored
-
bell@sanja.is.com.ua authored
into sanja.is.com.ua:/home/bell/mysql/work-4.0
-
bell@sanja.is.com.ua authored
-
arjen@fred.bitbike.com authored
-
arjen@fred.bitbike.com authored
-
arjen@fred.bitbike.com authored
-
arjen@fred.bitbike.com authored
-
- 07 Oct, 2002 8 commits
-
-
bell@sanja.is.com.ua authored
FN_NO_CASE_SENCE used instead of __WIN__ in table name handling of quary cache
-
paul@teton.kitebird.com authored
-
Sinisa@sinisa.nasamreza.org authored
-
Sinisa@sinisa.nasamreza.org authored
into sinisa.nasamreza.org:/mnt/work/mysql-4.0
-
Sinisa@sinisa.nasamreza.org authored
-
mwagner@work.mysql.com authored
into work.mysql.com:/d1/users/mwagner/work/bk/mysql-4.0
-
mwagner@work.mysql.com authored
-
paul@teton.kitebird.com authored
-
- 06 Oct, 2002 1 commit
-
-
paul@teton.kitebird.com authored
manual.texi missing from the syntax diagram.
-
- 05 Oct, 2002 2 commits
-
-
paul@teton.kitebird.com authored
-
Sinisa@sinisa.nasamreza.org authored
-
- 04 Oct, 2002 1 commit
-
-
jani@rhols221.adsl.netsonic.fi authored
-
- 03 Oct, 2002 2 commits
-
-
lenz@mysql.com authored
into mysql.com:/space/my/mysql-4.0-automake
-
serg@serg.mysql.com authored
-
- 02 Oct, 2002 8 commits
-
-
arjen@fred.bitbike.com authored
-
Administrador@light. authored
-
heikki@hundin.mysql.fi authored
InnoDB does allow a foreign key constraint name to be specified
-
heikki@hundin.mysql.fi authored
InnoDB does allow a foreign key constraint name to be specified, though it is not used in any way
-
paul@teton.kitebird.com authored
into teton.kitebird.com:/home/paul/mysql-4.0
-
paul@teton.kitebird.com authored
-
monty@hundin.mysql.fi authored
-
lenz@mysql.com authored
up-to-date BK changelog instead of sql/ChangeLog, add LICENSE if available)
-