From: Philip Stoev Date: October 19 2008 9:03pm Subject: Re: Odd new error message since today's pull from 6.0 List-Archive: http://lists.mysql.com/falcon/81 Message-Id: <0446776D5D2B4BAC823BE22B66A67833@Philips> MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit What happened is that the default binary log format for the server has been changed to STATEMENT, from a previous default of, I think, MIXED. By default the binary log is not enabled, so the default logging format does not matter and Falcon works. The relevant mysqld startup option is --mysqld=--binlog-format=ROW . I am not sure if changing the default binary logging format was a conscious decision and if people thought about the impact this will have on Falcon. Interested parties may pursue this further, I wont. Philip Stoev ----- Original Message ----- From: "Christopher Powers" To: "Ann W. Harrison" Cc: "Philip Stoev" ; Sent: Saturday, October 18, 2008 7:06 PM Subject: Re: Odd new error message since today's pull from 6.0 > Ann, did you ever resolve this? > > Ann W. Harrison wrote: >> Philip Stoev wrote: >>> This script does only CREATE TABLE and single-row INSERT IGNORE , so >>> whatever it is , it is not good. >>> >> >> Yup. The problem is insert ignore, as this case shows ... >> >> >> mysql> create database awh; >> Query OK, 1 row affected (0.02 sec) >> >> mysql> use awh; >> Database changed >> mysql> create table t1 (f1 integer) engine=Falcon; >> Query OK, 0 rows affected (0.19 sec) >> >> mysql> insert ignore into t1 (f1) values (5); >> ERROR 1598 (HY000): Binary logging not possible. >> Message: Statement-based format required for this statement, but >> not allowed by this combination of engines >> mysql> >> >> Sigh. >> >> >> Ann >> > > -- > Falcon Storage Engine Mailing List > For list archives: http://lists.mysql.com/falcon > To unsubscribe: > http://lists.mysql.com/falcon?unsub=philip.stoev@stripped > >