mapi_next_result skips over results (losing output)

[monetdb-team]

Date: 2010-12-06 15:38:52 +0100
From: @grobian
To: clients devs <>
Version: 1.40.1 (Oct2010) [obsolete]

Last updated: 2011-03-28 17:31:40 +0200

Comment 15294

Date: 2010-12-06 15:38:52 +0100
From: @grobian

% cat loss.sql
create table t (id int, v int);
alter table t add unique (v);

insert into t values (null, 2);
insert into t values (null, 2);

select count(*) from t;
select * from t;

drop table t;

% $INSTALL_DIR/bin/mclient -dtest loss.sql
operation successful
1 affected row
SQLException:assert:INSERT INTO: UNIQUE constraint 't.t_v_unique' violated
+------+------+
| id | v |
+======+======+
| null | 2 |
+------+------+
1 tuple

expected:
% $INSTALL_DIR/bin/mclient -dtest loss.sql
operation successful
operation successful
1 affected row
SQLException:assert:INSERT INTO: UNIQUE constraint 't.t_v_unique' violated
+------+
| L1 |
+======+
| 1 |
+------+
1 tuple
+------+------+
| id | v |
+======+======+
| null | 2 |
+------+------+
1 tuple
operation successful

Comment 15295

Date: 2010-12-06 15:44:04 +0100
From: @grobian

Changeset e09534da01d4 made by Fabian Groffen fabian@cwi.nl in the MonetDB repo, refers to this bug.

For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=e09534da01d4

Changeset description:

mapi_next_result: don't skip over non-tables and non-updates

Partial fix for bug #2743, this makes the second and third (from the
DROP TABLE) "operation successful" message appear in mclient's output.

Comment 15296

Date: 2010-12-06 16:00:34 +0100
From: @grobian

Changeset 58b029e73851 made by Fabian Groffen fabian@cwi.nl in the MonetDB repo, refers to this bug.

For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=58b029e73851

Changeset description:

read_into_cache: errors are not comments

Make sure errors aren't seen as comment-only blocks, such that results
aren't appended to them, causing them to disappear in the rendering,
because errors are mutual exclusive with anything else.
This fully fixes bug #2743

Comment 15650

Date: 2011-03-28 17:31:40 +0200
From: @sjoerdmullender

The Mar2011 version has been released.