15.07.2014 15:23, Tony Whyman wrote: > The criticism of the old API in the release notes appears valid
This criticism is valid not for API itself, but mostly for its internal implementation. API is fine, code under the hood is inadequate. Most of 16 bits limitation belongs to the Message API which is not used now. The rest has easy workarounds or don't limit performance at all (despite what is said in RN). "The trap with the XSQLDA solution is that it encapsulates both the location of the data and their format, making it possible to change location or format (or both) between fetch calls. Hence, the need for the BLR wrapping in every fetch call". Cheap trick. The first part is true, but it does not make true the rest. There is no need to send BLR on server on every fetch. Actually, there is no need to send BLR at all. Client library is clever enough to do data coercion (or throw an error). Status vector is, actually, just an implementation artifact and can be expanded to infinity with rather simple changes in client library's code. -- WBR, SD. ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
