We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Date: 2012-11-28 10:11:08 +0100 From: @hannesmuehleisen To: SQL devs <> Version: 11.13.5 (Oct2012-SP1) CC: @hannesmuehleisen, @njnes
Last updated: 2013-01-22 09:29:06 +0100
Date: 2012-11-28 10:11:08 +0100 From: @hannesmuehleisen
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/537.19 (KHTML, like Gecko) Chrome/25.0.1323.1 Safari/537.19 Build Identifier:
While investigating Bug #3184, a problem in MonetDB was discovered. The following sequence of commands produces an unexpected result:
(login, CREATE TABLE T (a INT);)
sSET TIME ZONE INTERVAL '+01:00' HOUR TO MINUTE; Xauto_commit 0 Xreply_size 250 sPREPARE DELETE FROM t;; ( &5 0 0 6 0 % .prepare, .prepare, .prepare, .prepare, .prepare, .prepare table_name % type, digits, scale, schema, table, column name % varchar, int, int, str, str, str type % 0, 1, 1, 0, 0, 0 length ) sexec 0(); sCOMMIT; sPREPARE INSERT INTO t VALUES(?); sexec 1(42); sCOMMIT; Xrelease 1 sPREPARE DELETE FROM t;; ( &2 1 -1 ) Now, the last response is obviously not the expected one for the PREPARE statement.
Reproducible: Always
Response code &2
Normal PREPARE response, code &5
Date: 2012-11-28 10:11:44 +0100 From: @hannesmuehleisen
Created attachment 161 MAPI log file containing issue
Attached file: monet_1354093401387.log (text/plain, 3376 bytes) Description: MAPI log file containing issue
Date: 2012-11-28 10:12:20 +0100 From: @hannesmuehleisen
Created attachment 162 Sequence of JDBC calls in Java that provoke the bug
Attached file: MonetBugExposer.java (application/octet-stream, 852 bytes) Description: Sequence of JDBC calls in Java that provoke the bug
Date: 2012-12-03 10:23:41 +0100 From: @njnes
found a bug in the logics for query caching vs prepare/exec. Could you add the test?
Date: 2012-12-03 10:39:11 +0100 From: @njnes
Changeset bc7daa96d11e made by Niels Nes niels@cwi.nl in the MonetDB repo, refers to this bug.
For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=bc7daa96d11e
Changeset description:
fixed bug #3199
Date: 2013-01-22 09:29:06 +0100 From: @sjoerdmullender
Oct2012-SP3 has been released.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Date: 2012-11-28 10:11:08 +0100
From: @hannesmuehleisen
To: SQL devs <>
Version: 11.13.5 (Oct2012-SP1)
CC: @hannesmuehleisen, @njnes
Last updated: 2013-01-22 09:29:06 +0100
Comment 18169
Date: 2012-11-28 10:11:08 +0100
From: @hannesmuehleisen
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/537.19 (KHTML, like Gecko) Chrome/25.0.1323.1 Safari/537.19
Build Identifier:
While investigating Bug #3184, a problem in MonetDB was discovered. The following sequence of commands produces an unexpected result:
(login, CREATE TABLE T (a INT);)
sSET TIME ZONE INTERVAL '+01:00' HOUR TO MINUTE;
Xauto_commit 0
Xreply_size 250
sPREPARE DELETE FROM t;;
(
&5 0 0 6 0
% .prepare, .prepare, .prepare, .prepare, .prepare, .prepare table_name
% type, digits, scale, schema, table, column name
% varchar, int, int, str, str, str type
% 0, 1, 1, 0, 0, 0 length
)
sexec 0();
sCOMMIT;
sPREPARE INSERT INTO t VALUES(?);
sexec 1(42);
sCOMMIT;
Xrelease 1
sPREPARE DELETE FROM t;;
(
&2 1 -1
)
Now, the last response is obviously not the expected one for the PREPARE statement.
Reproducible: Always
Steps to Reproduce:
Actual Results:
Response code &2
Expected Results:
Normal PREPARE response, code &5
Comment 18170
Date: 2012-11-28 10:11:44 +0100
From: @hannesmuehleisen
Created attachment 161
MAPI log file containing issue
Comment 18171
Date: 2012-11-28 10:12:20 +0100
From: @hannesmuehleisen
Created attachment 162
Sequence of JDBC calls in Java that provoke the bug
Comment 18227
Date: 2012-12-03 10:23:41 +0100
From: @njnes
found a bug in the logics for query caching vs prepare/exec. Could you add the test?
Comment 18229
Date: 2012-12-03 10:39:11 +0100
From: @njnes
Changeset bc7daa96d11e made by Niels Nes niels@cwi.nl in the MonetDB repo, refers to this bug.
For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=bc7daa96d11e
Changeset description:
Comment 18362
Date: 2013-01-22 09:29:06 +0100
From: @sjoerdmullender
Oct2012-SP3 has been released.
The text was updated successfully, but these errors were encountered: