Commit graph

5 commits

Author SHA1 Message Date
lukem
1dfc0898a6 Don't install mysql.server as part of the client.
Bump PKGREVISION.
Fixes part of PR [pkg/19936].
2003-01-20 23:20:36 +00:00
martti
aaa9d6358b Updated mysql-client to 3.23.49
* Don't give warning for statement that is only a comment; This is
  needed for mysqldump --disable-keys to work.
* Fixed unlikely caching bug when doing a join without keys. In this case
  the last used field for a table always returned NULL.
* Added options to make LOAD DATA LOCAL INFILE more secure.
* Added --xml option to mysqldump for producing XML output.
* Changed to use autoconf 2.52 (from autoconf 2.13)
* Fixed bug in complicated join with const tables.
* Added internal safety checks for InnoDB.
* Some InnoDB variables was always shown in SHOW VARIABLES as OFF on
  high-byte-first systems (like sparc).
* Fixed problem with one thread using an InnoDB table and another thread
  doing an ALTER TABLE on the same table. Before that, mysqld could crash
  with an assertion failure in row0row.c, line 474.
* Tuned the InnoDB SQL optimizer to favor more often index searches over
  table scans. SELECT queries will now also generally run faster on all
  platforms.
* If MySQL binlogging is used, InnoDB now prints after crash recovery the
  latest MySQL binlog name and the offset InnoDB was able to recover to.
  This is useful, for example, when resynchronizing a master and a slave
  database in replication.
* Added better error messages to help in installation problems of
  InnoDB tables.
* One can now recover also MySQL temporary tables which have become
  orphaned inside the InnoDB tablespace.
* InnoDB now prevents a FOREIGN KEY declaration where the signedness is
  not the same in the referencing and referenced integer columns.
* Calling SHOW CREATE TABLE or SHOW TABLE STATUS could cause memory
  corruption and make mysqld to crash. Especially at risk was mysqldump,
  because it calls frequently SHOW CREATE TABLE.
* If inserts to several tables containing an auto-inc column were wrapped
  inside one LOCK TABLES, InnoDB asserted in lock0lock.c.
* In 3.23.47 we allowed several NULLS in a UNIQUE secondary index for an
  InnoDB table. But CHECK TABLE was not relaxed: it reports the table as
  corrupt. CHECK TABLE no longer complains in this situation.
* SHOW GRANTS now shows REFERENCES instead of REFERENCE.
2002-03-18 14:17:38 +00:00
seb
66111c6d15 Introduce new framework for handling info files generation and installation.
Summary of changes:
- removal of USE_GTEXINFO
- addition of mk/texinfo.mk
- inclusion of this file in package Makefiles requiring it
- `install-info' substituted by `${INSTALL_INFO}' in PLISTs
- tuning of mk/bsd.pkg.mk:
    removal of USE_GTEXINFO
    INSTALL_INFO added to PLIST_SUBST
    `${INSTALL_INFO}' replace `install-info' in target rules
    print-PLIST target now generate `${INSTALL_INFO}' instead of `install-info'
- a couple of new patch files added for a handful of packages
- setting of the TEXINFO_OVERRIDE "switch" in packages Makefiles requiring it
- devel/cssc marked requiring texinfo 4.0
- a couple of packages Makefiles were tuned with respect of INFO_FILES and
  makeinfo command usage

See -newly added by this commit- section 10.24 of Packages.txt for
further information.
2002-02-18 15:14:00 +00:00
martti
b76b9b039d Updated mysql-{client,server} to 3.23.47. This is a bug-fix release, a
complete (and a too-long to be included here) ChangeLog can be found at:

http://www.mysql.com/documentation/mysql/bychapter/manual_News.html#News-3.23.x
2002-01-08 14:09:37 +00:00
zuntum
0ca28723fb Move pkg/ files into package's toplevel directory 2001-11-01 00:11:36 +00:00
Renamed from databases/mysql-client/pkg/PLIST (Browse further)