On 21/06/2012 09:56, Dmitry Yemanov wrote: >> I don't consider isc_segment/isc_segstr_eof as really errors, and surely >> they should not be thrown when working with C++. >> >> So I think getSegment must be adapted to return ISC_STATUS code and have >> the returnLength parameter. > If we're about to change this, I'd rather prefer to not treat them as > status values at all. Let's make Blob::getSegment() returning int and > declare these two values as special ones, similarly to fetch(). And they > don't have to be equal to the status values numerically, we could > replace them in the upper layers (old API).
Ok. > BTW, Statement::fetch() doesn't have to return 100 either. It could > return boolean true/false and be replaced with 100 in the old API only. Legacy servers can also return 101 (for READ BLOB), but this is probably not a problem, since this statement will never return 100. Adriano ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
