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.
----- Original Message -----
From: "Christopher Powers" <Christopher.Powers@stripped>
To: "Ann W. Harrison" <ann@stripped>
Cc: "Philip Stoev" <pstoev@stripped>; <falcon@stripped>
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
> Falcon Storage Engine Mailing List
> For list archives: http://lists.mysql.com/falcon
> To unsubscribe: