Skip to content
New issue

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

Prepared statements fail on execution with message 'Symbol type not found' #3680

monetdb-team opened this issue Nov 30, 2020 · 0 comments


Copy link

@monetdb-team monetdb-team commented Nov 30, 2020

Date: 2015-03-10 16:56:55 +0100
From: Robin Cijvat <<robin.cijvat>>
To: SQL devs <>
Version: 11.19.9 (Oct2014-SP2)
CC: @njnes

Last updated: 2015-05-07 12:37:43 +0200

Comment 20700

Date: 2015-03-10 16:56:55 +0100
From: Robin Cijvat <<robin.cijvat>>

User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.76 Safari/537.36
Build Identifier:

On the current default branch, the following problem occurs (copied from mclient):

sql>create table t (s string);
operation successful (2.350ms)
sql>prepare select * from t where s = ?;
execute prepared statement using: EXEC 13(...)
| type | digits | scale | schema | table | column |
| clob | 0 | 0 | | t | s |
| clob | 0 | 0 | null | null | null |
2 tuples (0.388ms)
sql>exec 13('foo');
symbol type not found
sql>exec 13(clob 'foo');
syntax error, unexpected CLOB in: "exec 13(clob"
sql>exec 13(string 'foo');
syntax error, unexpected CLOB in: "exec 13(string"
sql>exec 13(cast('foo' as string));
symbol type not found
sql>exec 13(cast('foo' as clob));
symbol type not found

Reproducible: Always

Steps to Reproduce:

See SQL in field

Actual Results:

I get the error messages shown in the details field

Comment 20707

Date: 2015-03-11 17:02:12 +0100
From: @njnes

fixed, ie don't throw away the prepared statement when recompile is impossible

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant