Re: MySQL 4.1.11 has been released

2005-04-06 Thread Michael Stassen 
On Apr 6, 2005, at 2:12 PM, Michael Stassen wrote:
On Apr 5, 2005, at 11:37 PM, Matt Wagner wrote:
Hi,
A new version of MySQL Community Edition 4.1.11 Open Source database
management system has been released. It is now available in source and
binary form for a number of platforms from our download pages at
http://dev.mysql.com/downloads/ and mirror sites.
The good news:
mysql compiles cleanly for me (Mac OS X 10.3.8) and passes all tests.

   Bugs fixed:

 * Fixed   a  bug  in  my_print_defaults  that  made  it  ignore
   the --defaults-extra-file and --defaults-file options.
The bad news:
Although the description is wrong (--defaults-file works, 
--defaults-extra-file does not), I believe this would be bug #9136 
.  Unless I'm missing 
something, this has not been fixed.

  ~: my_print_defaults mysqld
  --key_buffer=32M
  ~: my_print_defaults -c /etc/de.cnf mysqld
  --max_allowed_packet=2M
  --key_buffer=64M
  ~: my_print_defaults -e /etc/de.cnf mysqld
  --key_buffer=32M
Enjoy!
   Matt
--
Matt Wagner, Production Engineer
MySQL AB, www.mysql.com
Northfield, MN, USA
Michael
I did a little more digging.  Bug #9136 says the fix is in a patch to 
mysys/default.c referenced in . 
 Looking at my copy of the source, this patch has NOT been applied to 
mysql-4.1.11.  I went ahead and applied the patch to my 4.1.11 source 
and re-compiled.  This build also passes all tests, and now I get

  ~: my_print_defaults mysqld
  --key_buffer=32M
  ~: my_print_defaults -c /etc/de.cnf mysqld
  --max_allowed_packet=2M
  --key_buffer=64M
  ~: my_print_defaults -e /etc/de.cnf mysqld
  --key_buffer=32M
  --max_allowed_packet=2M
  --key_buffer=64M
As you can see, with the patch, my_print_defaults now works as expected.
Michael
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: MySQL 4.1.11 has been released

2005-04-06 Thread Michael Stassen 
On Apr 5, 2005, at 11:37 PM, Matt Wagner wrote:
Hi,
A new version of MySQL Community Edition 4.1.11 Open Source database
management system has been released. It is now available in source and
binary form for a number of platforms from our download pages at
http://dev.mysql.com/downloads/ and mirror sites.
The good news:
mysql compiles cleanly for me (Mac OS X 10.3.8) and passes all tests.

   Bugs fixed:

 * Fixed   a  bug  in  my_print_defaults  that  made  it  ignore
   the --defaults-extra-file and --defaults-file options.
The bad news:
Although the description is wrong (--defaults-file works, 
--defaults-extra-file does not), I believe this would be bug #9136 
.  Unless I'm missing something, 
this has not been fixed.

  ~: my_print_defaults mysqld
  --key_buffer=32M
  ~: my_print_defaults -c /etc/de.cnf mysqld
  --max_allowed_packet=2M
  --key_buffer=64M
  ~: my_print_defaults -e /etc/de.cnf mysqld
  --key_buffer=32M
Enjoy!
   Matt
--
Matt Wagner, Production Engineer
MySQL AB, www.mysql.com
Northfield, MN, USA
Michael
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

MySQL 4.1.11 has been released

2005-04-05 Thread Matt Wagner 
Hi,

A new version of MySQL Community Edition 4.1.11 Open Source database
management system has been released. It is now available in source and
binary form for a number of platforms from our download pages at
http://dev.mysql.com/downloads/ and mirror sites.

Note that not all mirror sites may be up-to-date at this point. If you
cannot find this version on a particular mirror, please try again later or
choose another download site.

This is a bug fix release for the current production series.

Please refer to our bug database at http://bugs.mysql.com/ for more details
about the individual open and resolved bugs in this version.

NOTE: Due to a procedural error during the release builds, the MySQL Max and
commercial MySQL Cluster packages will be delayed by a few hours before
fully syncing with our download mirrors.

Changes in release 4.1.11:

   Functionality added or changed:
 * ONLY_FULL_GROUP_BY no longer is included in the ANSI composite SQL
   mode. (Bug #8510)
 * mysqld_safe will create the directory where the UNIX socket file is
   to be located if the directory does not exist. This applies only to
   the last component of the directory pathname. (Bug #8513)
 * The coercibility for the return value of functions such as USER()
   or VERSION() now is ``system constant'' rather than ``implicit.''
   This makes  these  functions  more coercible than column values
   so that comparisons  of the two do not result in Illegal mix of
   collations errors. COERCIBILITY() was modified to accommodate
   this new coercibility value. See section 12.8.3 Information
   Functions.
 * User  variable coercibility has been changed from ``coercible''
   to ``implicit.'' That is, user variables have the same coercibility
   as column values.
 * NULL  now is considered more coercible than string constants.
   This resolves some Illegal mix of collations conflicts.
 * Modified the parser to allow SELECT statements following the
   UNION keyword to be subqueries in parentheses. (Bug #2435)
 * For  slave replication servers started with --replicate-*
   options, statements that should not be replicated according those
   options no longer are written to the slave's general query log.
   (Bug #8297)
 * Added SQL_NOTES session variable to cause Note-level warnings not
   to be recorded. (Bug #6662)
 * InnoDB: Commit after every 10,000 copied rows when executing
   CREATE INDEX, DROP INDEX or OPTIMIZE TABLE, which are internally
   implemented as ALTER  TABLE. This makes it much faster to recover
   from an aborted operation.
 * Added a new global system variable slave_transaction_retries: If
   the replication slave SQL thread fails to execute a transaction
   because of an InnoDB deadlock or exceeded InnoDB's
   innodb_lock_wait_timeout or NDBCluster's
   TransactionDeadlockDetectionTimeoutor
   TransactionInactiveTimeout,  it  automatically
   retries slave_transaction_retries times before stopping with an
   error. The default in MySQL 4.1 is 0. You must explicitly set the
   value greater than 0 to enable the ``retry'' behavior. (In MySQL
   5.0.3 or newer, the default is 10.) (Bug #8325)
 * Added --with-big-tables compilation option to configure.
   (Previously it was necessary to pass -DBIG_TABLES to the compiler
   manually in order to enable large table support.) See section
   2.8.2 Typical configure Options for details.
 * Added configuration directives !include and !includedir for
   including option files and searching directories for option files.
   See section 4.3.2 Using Option Files for usage.

   Bugs fixed:
 * Fixed a server crash caused by use of NOW() is a subquery.
   (Bug #8824)
 * Fixed problems with static variables to allow building on Fedora
   Core 3. (Bug #6554)
 * Some  user  variables  were  not  being  handled with ``implicit''
   coercibility. (Bug #9425)
 * Setting the max_error_count system variable to 0 resulted in a
   setting of 1. (Bug #9072)
 * Fixed a collation coercibility problem that caused a union between
   binary and non-binary columns to fail. (Bug #6519)
 * Fixed a problem with the tee command in mysql that resulted in mysql
   crashing. (Bug #8499)
 * On Windows, create shared memory objects with the proper access
   rights to  make  them usable when the client and server are running
   under different accounts. (Bug #8226)
 * Bundled zlib in the source distribution was upgraded to 1.2.2.
   (Bug #9118)
 * Fixed server crash resulting from queries that combined SELECT
   DISTINCT, SUM(), and ROLLUP. (Bug #8615)
 * Incorrect  results were returned from queries that combined
   SELECT DISTINCT, GROUP BY , and ROLLUP. (Bug #8616)
 * Fixed a bug that under certain circumstances could allow a