Unexpected transaction behavior

[Chris Slominski]

When there is an ongoing (repeatable read) transaction on an InnoDB table; which is adding rows to the table:

In another session I can do the following without blocking. This sees the table with none of the rows added as expected.

select chan_id,name,type,adel,size,(active&request) AS active from channels where alert=1 and host='devl05'

However the following will block until the other transaction is complete; where the select clause is identical to the one above. Why?

create temporary table alert engine=Innodb select ...