MySQL Community Server 5.6.27 has been released

[Hery Ramilison]

Dear MySQL users,

MySQL Server 5.6.27, a new version of the popular Open Source
Database Management System, has been released. MySQL 5.6.27 is
recommended for use on production systems.

For an overview of what's new in MySQL 5.6, please see

http://dev.mysql.com/doc/refman/5.6/en/mysql-nutshell.html

For information on installing MySQL 5.6.27 on new servers or upgrading
to MySQL 5.6.27 from previous MySQL releases, please see

  http://dev.mysql.com/doc/refman/5.6/en/installing.html

MySQL Server is available in source and binary form for a number of
platforms from our download pages at

  http://dev.mysql.com/downloads/

Not all mirror sites may be up to date at this point in time, so if you
can't find this version on some mirror, please try again later or choose
another download site.

We welcome and appreciate your feedback, bug reports, bug fixes,
patches, etc:

  https://wikis.oracle.com/display/mysql/Contributing

The following section lists the changes in the MySQL 5.6 since
the release of MySQL 5.6.26. It may also be viewed
online at

http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-27.html

Enjoy!

Changes in MySQL 5.6.27 (2015-09-30):

   Functionality Added or Changed

 * InnoDB: The new innodb_numa_interleave read-only
   configuration option allows you to enable the NUMA
   interleave memory policy for allocation of the InnoDB
   buffer pool. When innodb_numa_interleave is enabled, the
   NUMA memory policy is set to MPOL_INTERLEAVE for the
   mysqld process. After the InnoDB buffer pool is
   allocated, the NUMA memory policy is set back to
   MPOL_DEFAULT. This option is only available on
   NUMA-enabled systems.
   Thanks to Stewart Smith for the patch. (Bug #18871046,
   Bug #72811)

 * yaSSL was upgraded to version 2.3.8. (Bug #21888925)

 * RPM .spec files were updated so that MySQL Server builds
   from source RPM packages will include the proper files to
   take advantage of operating system NUMA capabilities.
   This introduces a runtime dependency on libnuma.so.1. RPM
   and yum detect this and refuse to install if that library
   is not installed. (Bug #21775221)

 * yaSSL was upgraded to version 2.3.7d. This fixes a
   connection-failure issue when used with the thread pool
   plugin. (Bug #20774956)

   Bugs Fixed

 * InnoDB: Reloading a table that was evicted while empty
   caused an AUTO_INCREMENT value to be reset. (Bug
   #21454472, Bug #77743)

 * InnoDB: Memory allocation sanity checks were added to the
   memcached code. (Bug #21288106)

 * InnoDB: A memcached flush_all command raised an
   assertion. A function that starts a transaction was
   called from within assertion code. (Bug #21239299, Bug
   #75199)

 * InnoDB: A data corruption occurred on ARM64. GCC builtins
   did not issue the correct fences when setting or
   unsetting the lock word. (Bug #21102971, Bug #76135)

 * InnoDB: Server shutdown was delayed waiting for the purge
   thread to exit. To avoid this problem, the number of
   calls to trx_purge() was reduced, and the trx_purge()
   batch size was reduced to 20. (Bug #21040050)

 * InnoDB: In READ COMMITTED mode, a REPLACE operation on a
   unique secondary index resulted in a constraint
   violation. Thanks to Alexey Kopytov for the patch. (Bug
   #21025880, Bug #76927)

 * InnoDB: The IBUF_BITMAP_FREE bit indicated that there was
   more free space in the leaf page than was actually
   available. (Bug #20796566)

 * InnoDB: Setting lower_case_table_names=0 on a
   case-insensitive file system could result in a hang
   condition when running an INSERT INTO ... SELECT ... FROM
   tbl_name operation with the wrong tbl_name letter case.
   An error message is now printed and the server exits when
   attempting to start the server with
   --lower_case_table_names=0 on a case-insensitive file
   system. (Bug #20198490, Bug #75185)

 * InnoDB: The server failed to start with an
   innodb_force_recovery setting greater than 3. InnoDB was
   set to read-only mode before redo logs were applied.
   DROP TABLE is now supported with an innodb_force_recovery
   setting greater than 3. (Bug #19779113)

 * InnoDB: The trx_sys_read_pertable_file_format_id()
   function reported the wrong file format. (Bug #19206671)

 * Partitioning: CREATE TABLE statements that used an
   invalid function in a subpartitioning expression did not
   always fail gracefully as expected. (Bug #20310212)

 * Partitioning: Error handling for failed
   partitioning-related ALTER TABLE operations against
   non-partitioned tables was not performed correctly (Bug
   #20284744)

 * Partitioning: ALTER TABLE when executed from a stored
   procedure did not always work correctly with tables
   partitioned by RANGE. 

Re: Relational query question

[Divesh Kamra]

It better to LEFT join rather then NOT IN




On Wed, Sep 30, 2015 at 6:00 PM, Mogens Melander 
wrote:

> Maybe not the most optimal, but (probably) the most simple:
>
> SELECT * FROM fruit
> where id not in (select fruit from purchase
> where customer=1);
>
> 1, 'Apples'
> 3, 'Oranges'
>
>
> On 2015-09-30 00:01, Richard Reina wrote:
>
>> If I have three simple tables:
>>
>> mysql> select * from customer;
>> +++
>> | ID | NAME   |
>> +++
>> |  1 | Joey   |
>> |  2 | Mike   |
>> |  3 | Kellie |
>> +++
>> 3 rows in set (0.00 sec)
>>
>> mysql> select * from fruit;
>> ++-+
>> | ID | NAME|
>> ++-+
>> |  1 | Apples  |
>> |  2 | Grapes  |
>> |  3 | Oranges |
>> |  4 | Kiwis   |
>> ++-+
>> 4 rows in set (0.00 sec)
>>
>> mysql> select * from purchases;
>> ++-+--+
>> | ID | CUST_ID | FRUIT_ID |
>> ++-+--+
>> |  2 |  3 |   2   |
>> |  3 |  1 |   4   |
>> |  4 |  1 |   2   |
>> |  5 |  2 |   1   |
>> ++-+--+
>>
>> I am having trouble understanding a relational query. How can I select
>> those fruits that Joey has not purchased?
>>
>
> --
> Mogens
> +66 8701 33224
>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
>
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:http://lists.mysql.com/mysql
>
>