From: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
---|---|
To: | Johann Letzel <j(dot)letzel(at)t-online(dot)de> |
Cc: | Hiroshi Inoue <inoue(at)tpf(dot)co(dot)jp>, pgsql-odbc(at)postgresql(dot)org |
Subject: | Re: Bug in SQLRowCount ? |
Date: | 2013-01-17 17:03:01 |
Message-ID: | 50F82EC5.60701@vmware.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
On 17.01.2013 16:05, Johann Letzel wrote:
> 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 ?
According to this:
http://msdn.microsoft.com/en-us/library/windows/desktop/ms711818%28v=vs.85%29.aspx,
both behaviors are permitted. When the driver returns SQL_PARC_BATCH,
when you call SQLGetInfo(conn, SQL_PARAM_ARRAY_ROW_COUNTS, ... ), the
driver returns a separate row count for each parameter (PostgreSQL).
When it returns SQL_PARC_NO_BATCH, it returns a single row count that's
the sum of all parameters (MSSQL). In a portable application, you need
to call SQLGetInfo, and deal with both behaviors.
- Heikki
From | Date | Subject | |
---|---|---|---|
Next Message | Sandeep Thakkar | 2013-01-21 11:28:57 | Error connecting psqlODBC to PostgreSQL |
Previous Message | Johann Letzel | 2013-01-17 14:05:41 | Re: Bug in SQLRowCount ? |