Problem on calling procedures with ADODB

Поиск
Список
Период
Сортировка
От Kamil ADEM
Тема Problem on calling procedures with ADODB
Дата
Msg-id 994c12dd0d6348d389246fda802fff07@exmbx03.ofis.int
обсуждение исходный текст
Ответы Re: Problem on calling procedures with ADODB  (Adrian Grucza <adrian.grucza@iress.com>)
Список pgsql-odbc

Hello,

 

We porting a Windows MFC application from MSSQLServer to PostgreSQL and trying to use psqlODBC driver with Microsoft ADODB.

We are currently performing the migration steps of our C sources and got stuck on an issue and thought to ask for your help.

 

We use Microsoft ADODB on Windows to access the database and cannot change this interface in short time. To access Postgres we changed the connection string accordingly. (e.g. “Driver= {PostgreSQL ANSI};”)

On calling Postgres procedures we have the following code sample:

_CommandPtr pCommand;

pCommand->CommandType = adCmdStoredProc;

pCommand->CommandText = _bstr_t(“sp_TEST”);

pCommand->Parameters->Refresh();

pCommand->Execute(NULL, NULL, adCmdStoredProc | adExecuteNoRecords);

The Execute() method generates the command: “SELECT * FROM sp_TEST(…)” instead of “CALL sp_TEST(…)”. This is appropriate for Postgres functions, but there must be a way to call procedures also.

Do you know such a reported issue?  Do you know a way to change this behaviour? Should we use a different driver? Should we get rid of procedures and convert our MSSQL stored procedures to Postgres functions?

 

We would be grateful if you can guide us to the right solution.

Thanks in advance.

 

Best regards,

 

Kamil Adem

Aqvila Software Yazılım A.Ş.

 

 

 

В списке pgsql-odbc по дате отправления:

Предыдущее
От: Andreas Beier
Дата:
Сообщение: Re: Excel ODBC query loosing parameter when returning the query result directly to a pivot table.
Следующее
От: Adrian Grucza
Дата:
Сообщение: Re: Problem on calling procedures with ADODB