Bug with remote tables in transactions

Hi,

We encounter a bug with remote tables as part of transactions:

sql>CREATE REMOTE TABLE rmt_tbl (id int, name varchar(20)) ON ‘mapi:monetdb://remote.host.url:50000/dbname/scm1/l_tbl monetdb://remote.host.url:50000/dbname/scm1/l_tbl’; operation successful sql>BEGIN TRANSACTION; auto commit mode: off sql>DROP TABLE rmt_tbl; operation successful sql>ROLLBACK; auto commit mode: on sql>DROP TABLE if exists rmt_tbl; no such table: ‘sys.rmt_tbl’ sql>

It seems that after rollback the table exists in the catalogue but it does not actually exists so that drop table fails even if we have ‘if exists’ This happens only with remote tables.

Best, Yannis