11.03.2014 14:04, Adriano dos Santos Fernandes wrote: > A possible solution may be to separate offset calculation from > IMessageMetadata.
Quoting one movie, "offsets are not important, only data is important". Leave offsets to engine, if it cannot work other way, but save users from them. User program usually already have data kept in a set of variables. It can easily provide pointers to them (as it is done now with SQLDA API). Copying them somewhere is a bit harder, but also acceptable. Calculate offsets, allocate buffer and then copy - a definite overkill. It isn't "easy to use" kind of API. In all known to me DBMS APIs a programmer provide pointers to data to client library. And it is a right thing from performance POV: pointers are copied better than memory buffers. -- WBR, SD. ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
