InnoDB does allow a foreign key constraint name to be specified, though it is not used in any way
Docs/manual.texi:
InnoDB does allow a foreign key constraint name to be specified, though it is not used in any way
Don't require UPDATE_ACL for REPLACE
Docs/manual.texi:
Changelog
configure.in:
Fix for building shared libraries with a patched glibc
sql/sql_parse.cc:
Don't require UPDATE_ACL for REPLACE
- added some missing changelog entries to the 4.0.5 changelog
- applied small fix to configure.in from monty (already applied manually
to configure.in of the 4.0.4 release source files - not relevant for
normal builds anyway)
Docs/manual.texi:
- added missing changelog entries
- added the 4.0.4 release date
configure.in:
- bumped up version number to 4.0.5-beta, now that the 4.0.4 builds
are done
- applied fix from Monty to be able to build shared libraries even
when the the static NSS libraries are installed. This patch has already
been applied to the released 4.0.4 sources to work around a local build
problem, but has not been checked in yet.
Clarified FOREIGN KEY syntax, added a note that CREATE TABLE causes an InnoDB commit if binlogging is used, added InnoDB version history
Docs/manual.texi:
Clarified FOREIGN KEY syntax, added a note that CREATE TABLE causes an InnoDB commit if binlogging is used, added InnoDB version history
into hundin.mysql.fi:/my/bk/mysql-4.0
configure.in:
Auto merged
BitKeeper/deleted/.del-global.h~e80d28157acfdcb5:
Auto merged
Docs/manual.texi:
Auto merged
client/mysqlbinlog.cc:
Auto merged
sql/mysqld.cc:
Auto merged
Clean out 'Graphical clients' section of the contributed software section
Docs/manual.texi:
Clean out 'Graphical clients' section of the contributed software section
BitKeeper/etc/logging_ok:
Logging to logging@openlogging.org accepted
Accept zero dates without warnings
Docs/manual.texi:
ChangeLog
sql/sql_acl.cc:
Compare hostnames case insensitive
sql/time.cc:
Accept zero dates without warnings
- mysql.spec.sh: MySQL-Max now requires MySQL >= 4.0 to avoid version
mismatches (people were mixing MySQL 3.23 and 4.0 RPMs)
Docs/manual.texi:
- Added Changelog entry
support-files/mysql.spec.sh:
- MySQL-Max now requires MySQL >= 4.0 to avoid version mismatching
manual.texi and QUICK are not mutually exclusive).
Docs/manual.texi:
DELETE grammer was not quite right (LOW_PRIORITY
and QUICK are not mutually exclusive).
Only write short usage if one starts mysqldump without any options
Added query cache on windows
Added error message if one can't read privilege tables
Docs/manual.texi:
Changelog
VC++Files/bdb/bdb.dsp:
Updated project files for 4.0.4
VC++Files/client/mysqlclient.dsp:
Updated project files for 4.0.4
VC++Files/innobase/innobase.dsp:
Updated project files for 4.0.4
VC++Files/mysqlbinlog/mysqlbinlog.dsp:
Updated project files for 4.0.4
VC++Files/mysys/mysys.dsp:
Updated project files for 4.0.4
VC++Files/perror/perror.dsp:
Updated project files for 4.0.4
VC++Files/sql/mysqld.dsp:
Updated project files for 4.0.4
client/mysqldump.c:
Only write short usage if one starts mysqldump without any options
include/config-win.h:
Added query cache on windows
libmysql/libmysql.def:
Removed old depricated functions from windows dll
sql/ha_innodb.cc:
Added missing defines
sql/set_var.cc:
Code cleanup
sql/sql_acl.cc:
Added error message if one can't read privilege tables
sql/sql_cache.h:
Changed some C linkage functions to C++ functions (portability fix)
sql/sql_class.cc:
Safety fix
