Subject | Re: Number of Rows updated |
---|---|
Author | Jason Lee |
Post date | 2001-01-26T21:53:43Z |
This was posted earlier to the firebird list, which was not the right
list, so I continue my question here:
Ann Harrison wrote:
to be isc_info_sql_records, but that's a total guess. Assuming this is
right type to pass (to isc_dsql_sql_info(), right? ;), I'm not sure how
to interpret the results. Here's what I'm getting (in hex dump form):
17 1D 00 0F 04 00 00 00 00 00 10 04 00 00 00 00 00 04 00 00 00 00 00 0E
04 00 00 00 00 00 01 01
The buffer I'm passing is 256 chars long. That should be long enough,
but that's also a total guess. Thanks a lot!
--
Jason Lee | Under the aegis of The Living God, I trust and love
Programmer/Analyst | with certainty. Under the aegis of The Living God, I
www.rri-medtech.com | live and breathe eternity! -- Mortal
list, so I continue my question here:
Ann Harrison wrote:
> At 12:45 PM 1/26/2001 -0600, you wrote:I'm looking at this call now, and then type I need to pass would appear
>
>> I need to know if any rows were affected by a given update or delete
>> statement. In our system, if an update or delete is executed, and no
>> rows are affected, we need to communicate that to the calling code.
>> Is this possible with IB? It works under ODBC and OCI, but I can't
>> see in the IB dox if this is supported. Thanks!
>
>
> Look at the SQL statement info call.
to be isc_info_sql_records, but that's a total guess. Assuming this is
right type to pass (to isc_dsql_sql_info(), right? ;), I'm not sure how
to interpret the results. Here's what I'm getting (in hex dump form):
17 1D 00 0F 04 00 00 00 00 00 10 04 00 00 00 00 00 04 00 00 00 00 00 0E
04 00 00 00 00 00 01 01
The buffer I'm passing is 256 chars long. That should be long enough,
but that's also a total guess. Thanks a lot!
--
Jason Lee | Under the aegis of The Living God, I trust and love
Programmer/Analyst | with certainty. Under the aegis of The Living God, I
www.rri-medtech.com | live and breathe eternity! -- Mortal