09.06.2015 07:13, Claudio Valderrama C. wrote: > > Ideas? We could add a new info tag to return the internal ROWS_AFFECTED value, so that ISQL would not need to rely on separate I/U/D counters.
Given that ISQL already uses the new API, maybe we could even surface such an info request directly via the dedicated API method rather than via the isc_info_* tag (or just map the former to the latter internally). Dmitry ------------------------------------------------------------------------------ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
