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

Error in ODBC-Driver when using Prepared Statements #3397

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

Error in ODBC-Driver when using Prepared Statements #3397

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

Comments

@monetdb-team
Copy link

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

Date: 2013-11-14 11:18:46 +0100
From: Dieter <>
To: clients devs <>
Version: 11.15.17 (Feb2013-SP5)
CC: mayerd

Last updated: 2013-12-03 13:59:32 +0100

Comment 19331

Date: 2013-11-14 11:18:46 +0100
From: Dieter <>

User-Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0; MALC)
Build Identifier:

When using prepared INSERT-Statements "unkown error"-message is shown and
INSERT-Statements are not executed.

Reproducible: Always

Steps to Reproduce:

  1. Create the samples table in the database "voc"
    create table prices (currency char(3) ,
    valid_from char(8), price decimal(15,2));

  2. Define the ODBC-System-DSN: MonetDB

  3. Execute the VB-Script monetpara.vbs

Actual Results:

Error message "unbekannter Fehler" (means "unkown error") is displayed.

Expected Results:

3 records should be inserted via the prepared input statement.

Comment 19332

Date: 2013-11-14 11:20:33 +0100
From: Dieter <>

Created attachment 249
VB-Script for testing

Attached file: monetpara.vbs (text/plain, 1217 bytes)
Description: VB-Script for testing

Comment 19333

Date: 2013-11-14 14:41:34 +0100
From: @sjoerdmullender

Can you please create a log and attach it to this bug report.

To create a log, you need to start the application that uses the MonetDB ODBC driver with an extra environment variable. Probably the easiest way to do that is to start a cmd window (Start -> Run... -> cmd.exe) and in that window type

set ODBCDEBUG=C:....\odbc.log

and then start your application from this window.
The bit after the = should be the absolute pathname of a file you can write to. After the application is done it should contain a log of the complete interaction with the driver. Before attaching the file, please make sure it doesn't contain any sensitive information.

Comment 19335

Date: 2013-11-15 09:13:46 +0100
From: Dieter <>

Created attachment 250
ODBC logfile

ODBC log for error situation

Attached file: odbc.log (text/plain, 5701 bytes)
Description: ODBC logfile

Comment 19347

Date: 2013-11-20 10:59:12 +0100
From: @sjoerdmullender

Looks like this is due to an incorrect implementation of the (deprecated) SQLParamOptions function.

Comment 19348

Date: 2013-11-20 11:00:23 +0100
From: MonetDB Mercurial Repository <>

Changeset 53fd890a72af 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=53fd890a72af

Changeset description:

Fix implementation of SQLParamOptions function.
This should fix bug #3397.

Comment 19349

Date: 2013-11-20 11:10:36 +0100
From: @sjoerdmullender

With the fix I was able to run the test script. Without the fix, I wasn't.

Comment 19351

Date: 2013-11-21 09:40:59 +0100
From: Dieter <>

Thanks for your action on this issue.

Can you provide a precompiled Version of the corrected ODBC.dll for
32bit/64bit Windows 7-Plattform. I'd like to test it in my environment and give you a feedback.

Comment 19352

Date: 2013-11-21 11:21:48 +0100
From: @sjoerdmullender

You can try out the release candidate for the Feb2013-SP6 release at http://dev.monetdb.org/downloads/testing/.

Comment 19375

Date: 2013-12-03 13:59:32 +0100
From: @sjoerdmullender

Feb2013-SP6 has been released.

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

Successfully merging a pull request may close this issue.

None yet
1 participant