Re: Bug in SQLRowCount ?
| От | Johann Letzel |
|---|---|
| Тема | Re: Bug in SQLRowCount ? |
| Дата | |
| Msg-id | d644f2b8-47fb-49ba-aafe-27eb1be027c2@email.android.com обсуждение исходный текст |
| Ответ на | Re: Bug in SQLRowCount ? (Hiroshi Inoue <inoue@tpf.co.jp>) |
| Ответы |
Re: Bug in SQLRowCount ?
|
| Список | pgsql-odbc |
Hi !
Tanks for the reply.
But according to the ODBC API SQLRowCount should retrieve the number of affected rows by the statement.
Why does PostgreSQL gives a 1 and MSSQL the number of inserted/updated rows ?
Regards
Johann
Hiroshi Inoue <inoue@tpf.co.jp> schrieb:
Tanks for the reply.
But according to the ODBC API SQLRowCount should retrieve the number of affected rows by the statement.
Why does PostgreSQL gives a 1 and MSSQL the number of inserted/updated rows ?
Regards
Johann
Hiroshi Inoue <inoue@tpf.co.jp> schrieb:
(2013/01/17 18:31), j.letzel@t-online.de wrote:Hello !
I maintain a backend in a commercial context. The backend provides
access to MS SQLServer (via ODBC) and Oracle (via OCI). Now I want to
make it ready for PostgreSQL via ODBC.
For performance reasons we use bulk inserts/updates.
This is done in this manner:
SQLAllocStmt
SQLPrepare // insert into kfztest.KP values (?,?,...,?)
SQBindParameter // for each column
...
SQLSetStmtAttr // SQL_ATTR_PARAMSET_SIZE to 523
SQLSetStmtAttr // SQL_ATTR_PARAM_STATUS_PTR to an array of SQLSMALLINT
SQLSetStmtAttr // SQL_ATTR_PARAMS_PROCESSED_PTR to an SQLULEN variable
SQLExecute // ends with SQL_SUCCESS
SQLRowCount // delivers 1 !!!!
The driver gives individual row counts for each parameter set.
SQLGetInfo(.., SQL_PARAM_ARRAY_ROW_COUNTS) returns SQL_PARC_BATCH.
regards,
Hiroshi Inoue
В списке pgsql-odbc по дате отправления: