USE_PKGINSTALL is "YES". bsd.pkg.install.mk will no longer automatically
pick up a INSTALL/DEINSTALL script in the package directory and assume that
you want it for the corresponding *_EXTRA_TMPL variable.
- Remove extraneous bits in the INSTALL script snippet and let the
framework execute the script at post-install time.
- Use OWN_DIRS_PERMS instead of MAKE_DIRS_PERMS for ${MYSQL_DATADIR} thus
save a DEINSTALL script snippet and its handling.
now and not NetBSD-*-arm32. Changes include one or more of:
- Change MACHINE_ARCH == arm32 to also match arm
- Where ONLY_FOR_PLATFORM includes NetBSD-*-arm32, add NetBSD-*-arm
- Where BROKEN or worked around for arm gcc bugs, set USE_GCC3
The last may shake out a few more broken packages the next bulk build.
have it be automatically included by bsd.pkg.mk if USE_PKGINSTALL is set
to "YES". This enforces the requirement that bsd.pkg.install.mk be
included at the end of a package Makefile. Idea suggested by Julio M.
Merino Vidal <jmmv at menta.net>.
- add support for MYSQL_USER and MYSQL_GROUP (user & group to run database as)
- change ownership of $MYSQL_DATADIR to ${MYSQL_USER}:${MYSQL_GROUP} 700
- fix safe_mysqld to send all output to the error log and to NOT output
random messages to the tty it was started on.
- display a MESSAGE reminding people to change the password of the
mysql 'root' user.
- bump PKGREVISION (to 3.23.49nb2)
The automatic truncation in gensolpkg doesn't work for packages which
have the same package name for the first 5-6 chars.
e.g. amanda-server and amanda-client would be named amanda and amanda.
Now, we add a SVR4_PKGNAME and use amacl for amanda-client and amase for
amanda-server.
All svr4 packages also have a vendor tag, so we have to reserve some chars
for this tag, which is normaly 3 or 4 chars. Thats why we can only use 6
or 5 chars for SVR4_PKGNAME. I used 5 for all the packages, to give the
vendor tag enough room.
All p5-* packages and a few other packages have now a SVR4_PKGNAME.
Disable the mysql-test stuff entirely.
Sync mysql-client's patch-af with mysql-server's.
Changes in release 3.23.39
--------------------------
* If one dropped and added an `AUTO_INCREMENT' column, the
`AUTO_INCREMENT' sequence wasn't reset.
* `CREATE .. SELECT' now creates not unique indexes delayed.
* Fixed problem where `LOCK TABLES table_name READ' followed by
`FLUSH TABLES' put a exclusive lock on the table.
* `REAL' @variables with was represented with 2 digits when
converted to strings.
* Fixed problem that client 'hung' when `LOAD TABLE FROM MASTER'
failed.
* Running `myisamchk --fast --force' will no longer repair tables
that only had the open count wrong.
* Added functions to handle symbolic links to make life easier in
4.0.
* We are now using the `-lcma' thread library on HP-UX 10.20 to get
*MySQL* more stable on HP-UX.
* Fixed problem with `IF()' and number of decimals in the result.
* Fixed date-part extraction functions to work with dates where day
and/or month is 0.
* Extended argument length in option files from 256 to 512 chars.
* Fixed problem with shutdown when `INSERT DELAYED' was waiting for
a `LOCK TABLE'.
* Fixed coredump bug in InnoDB when tablespace was full.
* Fixed problem with `MERGE' tables and big tables (> 4G) when using
`ORDER BY'.
Changes in release 3.23.38
--------------------------
* Fixed a bug when `SELECT' from `MERGE' table sometimes results in
incorrectly ordered rows.
* Fixed a bug in `REPLACE()' when using the ujis character set.
* Applied Sleepycat BDB patches 3.2.9.1 and 3.2.9.2.
* Added option `--skip-stack-trace' to `mysqld'.
* `CREATE TEMPORARY' now works with `InnoDB' tables.
* `InnoDB' now promotes sub keys to whole keys.
* Added option `CONCURRENT' to `LOAD DATA'.
* Better error message when slave `max_allowed_packet' is too low to
read a very long log event from the master.
* Fixed bug when too many rows where removed when using `SELECT
DISTINCT ... HAVING'.
* `SHOW CREATE TABLE' now returns `TEMPORARY' for temporary tables.
* Added `Rows_examined' to slow query log.
* Fixed problems with function returning empty string when using
together with a group functions and a `WHERE' that didn't match
any rows.
* New program `mysqlcheck'.
* Added database name to output for administrative commands like
`CHECK', `REPAIR', `OPTIMIZE'.
* Lots of portability fixes for InnoDB.
* Changed optimizer so that queries like `SELECT * FROM
table_name,table_name2 ... ORDER BY key_part1 LIMIT #' will use
index on `key_part1' instead of `filesort'.
* Fixed bug when doing `LOCK TABLE to_table WRITE,...; INSERT INTO
to_table... SELECT ...' when `to_table' was empty.
* Fixed bug with `LOCK TABLE' and BDB tables.
Changes in release 3.23.37
--------------------------
* Fixed a bug when using `MATCH' in `HAVING' clause.
* Fixed a bug when using `HEAP' tables with `LIKE'.
* Added `--mysql-version' to `safe_mysqld'
* Changed `INNOBASE' to `InnoDB' (because the `INNOBASE' name was
already used). All `configure' options and `mysqld' start options
are now using `innodb' instead of `innobase'. This means that you
have to change any configuration files where you have used
`innobase' options before upgrading to this version!
* Fixed bug when using indexes on `CHAR(255) NULL' columns.
* Slave thread will now be started even if `master-host' is not set,
as long as `server-id' is set and valid `master.info' is present
* Partial updates (terminated with kill) are now logged with a
special error code to the binary log. Slave will refuse to execute
them if the error code indicates the update was terminated
abnormally, and will have to be recovered with `SET
SQL_SLAVE_SKIP_COUNTER=1; SLAVE START' after a manual sanity
check/correction of data integrity.
* Fixed bug that erroneously logged a drop of internal temporary
table on thread termination to the binary log - bug affected
replication.
* Fixed a bug in `REGEXP()' on 64-bit machines.
* `UPDATE' and `DELETE' with `WHERE unique_key_part IS NULL' didn't
update/delete all rows.
* Disabled `INSERT DELAYED' for tables that support transactions.
* Fixed bug when using date functions on `TEXT'/`BLOB' column with
wrong date format.
* UDFs now also work on Windows. (Patch by Ralph Mason)
* Fixed bug in `ALTER TABLE' and `LOAD DATA INFILE' that disabled
key-sorting. These commands should now be faster in most cases.
* Fixed performance bug where reopened tables (tables that had been
waiting for `FLUSH' or `REPAIR') would not use indexes for the
next query.
* Fixed problem with `ALTER TABLE' to Innobase tables on FreeBSD.
* Added `mysqld' variables `myisam_max_sort_file_size' and
`myisam_max_extra_sort_file_size'.
* Initialize signals early to avoid problem with signals in Innobase.
* Applied patch for the `tis620' character set to make comparisons
case-independent and to fix a bug in `LIKE' for this character set.
*NOTE*: All tables that uses the `tis620' character set must be
fixed with `myisamchk -r' or `REPAIR TABLE' !
* Added `--skip-safemalloc' option to `mysqld'.
Changes in release 3.23.36
--------------------------
* Fixed a bug that allowed you to use database names containing a `.'
character. This fixes a serious security issue when `mysqld' is
run as root.
* Fixed bug when thread creation failed (could happen when doing a
LOT of connections in a short time).
* Fixed some problems with `FLUSH TABLES' and `TEMPORARY' tables.
(Problem with freeing the key cache and error `Can't reopen
table...').
* Fixed a problem in Innobase with other character sets than `latin1'
and another problem when using many columns.
* Fixed bug that caused a core dump when using a very complex query
involving `DISTINCT' and summary functions.
* Added `SET TRANSACTION ISOLATION LEVEL ...'
* Added `SELECT ... FOR UPDATE'.
* Fixed bug where the number of affected rows was not returned when
`MySQL' was compiled without transaction support.
* Fixed a bug in `UPDATE' where keys weren't always used to find the
rows to be updated.
* Fixed a bug in `CONCAT_WS()' where it returned wrong results.
* Changed `CREATE ... INSERT' and `INSERT ... SELECT' to not allow
concurrent inserts as this could make the binary log hard to
repeat. (Concurrent inserts are enabled if you are not using the
binary or update log).
* Changed some macros to be able to use fast mutex with glibc 2.2.
included by both mysql-server/Makefile and mysql-client/Makefile.
* Remove some unnecessary patches from mysql-client.
* Remove build dependency on autoconf as we don't really need to use it.
* Improve detection of native readline library.
* Provide INSTALL/DEINSTALL scripts to perform initial database setup and
to remind the package administrator to remove unnecessary directories upon
package removal.
* Use complete path to chown in various installed scripts. Fixes pkg/12725.
* Install server manpages with the server package. Fixes pkg/12724.
first component is now a package name+version/pattern, no more
executable/patchname/whatnot.
While there, introduce BUILD_USES_MSGFMT as shorthand to pull in
devel/gettext unless /usr/bin/msgfmt exists (i.e. on post-1.5 -current).
Patch by Alistair Crooks <agc@netbsd.org>
-lpthread found in library search path, use explicit path to library.
Noticed by hubertf.
When OPSYS == NetBSD, force use of included mit-pthreads.
Bumb version to "nb1".
Enable use of tcp_wrappers in the server.
BDB and Innobase table types are not configured in, so no transaction
support yet.
The 3.23 release has several major features that are not present
in previous versions. We have added new table types: MyISAM, a new
ISAM library which is tuned for SQL and supports large files; BDB,
which uses the Berkeley DB library from Sleepycat Software to
implement transaction-safe tables; INNOBASE, which uses the Innobase
database backend to implement transaction-safe tables. The 3.23
release also includes support for database replication between a
master and many slaves, full-text indexing, and much more.
For a detailed list of changes see appendix E of the online
documentation at http://www.mysql.com/.
The replication code and BerkeleyDB code is still not as tested
and as the rest of the code, so we will probably need to do a couple
of future releases of 3.23 with small fixes for this part of the
code. As long as you don't use these features, you should be quite
safe with MySQL 3.23!
Note that the above doesn't mean that replication or Berkeley DB
doesn't work; We have done a lot of testing of all code, including
replication and BDB without finding any problems. It only means
that not as many users uses this code as the rest of the code and
because of this we are not yet 100 % confident in this code.
This includes a security fix for the remote password checking protocol.
Other wise it's just the regular bunch of bugfixes. See appendix D of
the manual.
There are a bunch of bug fixes to the server. For a complete list see
the documentation.
Also, get rid of USE_GMAKE. The normal make works just fine.
Delete a whole bunch of patches that have been integrated into the
distribution.
Update the mit-pthreads patches to use _C_LABEL where appropriate so that
mit-pthreads works on ELF and a.out for the affected platforms.
