Devart ODBC Driver for PostgreSQL - Access violation calling SP

Discussion of open issues, suggestions and bugs regarding usage of ODBC Drivers
Post Reply
gwold
Posts: 3
Joined: Fri 26 Mar 2021 18:55

Devart ODBC Driver for PostgreSQL - Access violation calling SP

Post by gwold » Fri 26 Mar 2021 19:06

I can successfully run a SELECT query against a table in my PostgreSQL database, but when I call a stored procedure (that also hits that same table) I get an access violation on SQLExecDirect:

Code: Select all

[Devart][ODBC][PostgreSQL]Access violation at address 004071CB in module 'DevartODBCPostgreSQL.dll'. Read of address 00B8FD17
Why's the SP call having an issue, please?

gwold
Posts: 3
Joined: Fri 26 Mar 2021 18:55

Re: Devart ODBC Driver for PostgreSQL - Access violation calling SP

Post by gwold » Mon 29 Mar 2021 17:00

Expanding on this, here's the statement I'm using:

Code: Select all

CALL app_lock_set(?, ?, ?, ?, ?, ?, ?, ?, ?, ?)
The first four parameters are input/output; the remainder are input. All are bound (SQLBindParameter), then SQLExecDirect is called, triggering the access violation.

This same C++ code (VS 2013 running on Windows Server 2012) executes the SP call successfully using the psqlODBC driver.

I've also captured the SQL trace, if that'd be of any help.

oleg0k
Devart Team
Posts: 190
Joined: Wed 11 Mar 2020 08:28

Re: Devart ODBC Driver for PostgreSQL - Access violation calling SP

Post by oleg0k » Thu 01 Apr 2021 12:45

Hello,
Unfortunately, this information is not enough to reproduce the issue. We need a sample project that demonstrates the incorrect behavior, as well as your DDL scripts for creating and populating the database objects.
Please send them through the form on our website: https://devart.com/company/contactform.html

wbr, Oleg
Devart Team

gwold
Posts: 3
Joined: Fri 26 Mar 2021 18:55

Re: Devart ODBC Driver for PostgreSQL - Access violation calling SP

Post by gwold » Thu 01 Apr 2021 16:10

Files sent via your contact form.

Post Reply