Well, that doesn't make it available to the code that needs it...
So add numRowsHint to the public portion of Dbi_Handle. Set it to
DBI_NUM_ROWS_UNKNOWN before passing it to the driver in Exec. Driver
may fill it in. Upper layers use it if available, but don't rely on
it.
On Fri, Feb 7, 2014 at 1
This used to work. I *think* what happened is it got overlooked when I
implemented the sqlite driver and had to change the driver interface
to accommodate it (sqlite doesn't return nrows - you have to step the
state machine yourself).
Maybe numRows should be added back as a *numRowsHint arg in the
For the time being, i've used (abused?) the public
Dbi_Handle->rowIdx to return in the DML case the
number of affected rows. This has the advantage,
that all data-structures are unchanged, and the
modifications are quite local.
-g
Am 06.02.14 14:12, schrieb Gustaf Neumann:
> Hi Stephen,
>
> in co
