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

ODBC driver raises "unexpected end of input" for prepared string parameter from .NET application #3477

Closed
monetdb-team opened this issue Nov 30, 2020 · 0 comments
Labels
bug Client interfaces normal

Comments

@monetdb-team
Copy link

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

Date: 2014-04-24 21:50:26 +0200
From: Nik Schuiling <>
To: clients devs <>
Version: 11.17.13 (Jan2014-SP1)

Last updated: 2014-05-22 09:52:22 +0200

Comment 19776

Date: 2014-04-24 21:50:26 +0200
From: Nik Schuiling <>

User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.116 Safari/537.36
Build Identifier:

The following code causes the ODBC driver to raise a "unexpected end of input" exception:

using (OdbcCommand command = new OdbcCommand("INSERT INTO TOTAL_COUNTS VALUES (?, ?)", node.OdbcConnection, transaction))
{
command.Parameters.Add("?", OdbcType.NVarChar);
command.Parameters.Add("?", OdbcType.Int);
command.Prepare();

command.Parameters[0].Value = "157428";
command.Parameters[1].Value = 3337;
command.ExecuteNonQuery();

}

Schema of TOTAL_COUNTS table: CREATE TABLE TOTAL_COUNTS (ITEM varchar(7), SUPPORT int);

ODBC driver log is attached.

I've tried different OdbcTypes for parameter 0, but didn't succeed.

Reproducible: Always

Steps to Reproduce:

Run described code.

Part of ODBC error log:

SQLPrepareW 5452d48
SQLPrepare: "INSERT INTO TOTAL_COUNTS VALUES (?, ?)"
SQLFreeStmt 5452d48 SQL_RESET_PARAMS
SQLSetStmtAttrW 5452d48 SQL_ATTR_QUERY_TIMEOUT 1e
addStmtError 5452d48 HYC00 Optional feature not implemented 0
SQLGetInfoW 544da78 SQL_CONVERT_VARCHAR
SQLBindParameter 5452d48 1 1 SQL_C_WCHAR SQL_VARCHAR 7 0
SQLBindParameter 5452d48 2 1 SQL_C_SLONG SQL_INTEGER 10 0
SQLExecute 5452d48
SQLExecute 5452d48 execute 3 ('157428\000\000\000\000à´',3337)
addStmtError 5452d48 HY000 unexpected end of input
0
SQLGetDiagRecW Stmt 5452d48 1 0
SQLGetDiagRecW: [MonetDB][ODBC Driver 11.17.13]unexpected end of input
SQLGetDiagRecW Stmt 5452d48 2 0
SQLGetDiagRecW Stmt 5452d48 1 1024
SQLGetDiagRecW: [MonetDB][ODBC Driver 11.17.13]unexpected end of input
SQLGetDiagRecW Stmt 5452d48 2 1024
SQLGetInfoW 544da78 SQL_DRIVER_NAME
addDbcError 544da78 01004 String data, right truncated 0
SQLGetConnectAttrW 544da78 SQL_ATTR_CONNECTION_DEAD

Comment 19777

Date: 2014-04-24 21:50:59 +0200
From: Nik Schuiling <>

Created attachment 282
Full OBDC driver log

Attached file: odbc.log (application/octet-stream, 4122 bytes)
Description: Full OBDC driver log

Comment 19779

Date: 2014-04-25 16:05:23 +0200
From: MonetDB Mercurial Repository <>

Changeset 9f4ee3a5da21 made by Sjoerd Mullender sjoerd@acm.org in the MonetDB repo, refers to this bug.

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

Changeset description:

Stop at null bytes.
This hopefully fixes bug #3477.

Comment 19802

Date: 2014-05-06 10:14:50 +0200
From: @sjoerdmullender

Nik, can you test the (hopefully) fixed ODBC driver? I haven't been able to reproduce the problem, but I did implement what I think may well be a fix.

You can find ODBC driver installers at our nightly test page:
http://monetdb.cwi.nl/testweb/web/status.php?branch=Jan2014&n=1

Click on the files link near the top and then download the driver(s) you need.

Comment 19803

Date: 2014-05-06 14:35:12 +0200
From: Nik Schuiling <>

(In reply to comment 3)

Nik, can you test the (hopefully) fixed ODBC driver? I haven't been able to
reproduce the problem, but I did implement what I think may well be a fix.

You can find ODBC driver installers at our nightly test page:
http://monetdb.cwi.nl/testweb/web/status.php?branch=Jan2014&n=1

Click on the files link near the top and then download the driver(s) you
need.

Hi Sjoerd, fix confirmed. Thanks :).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Client interfaces normal
Projects
None yet
Development

No branches or pull requests

2 participants