On 12/09/13 14:45, Mark Rotteveel wrote: >> Yes. For open_blob only p_resp_object is returned. > I thought I saw it also returns something in p_resp_data (currently > ignored by Jaybird), but I was too busy to look deeper into that. Any idea > what it could be, maybe info on the opened blob, which would save me a > round trip :).
As far as I can see from server code - nothing else. >>> Now this may seem trivial as I already have the blob id because >>> I used it to open the blob, but the existing implementation in Jaybird >>> (and >>> in the .NET provider) make some assumptions with regard to the blob id > in >>> the response which are correct for op_create_blob(2), but seem to be >>> wrong >>> for an op_open_blob(2). >> Yes. now I understand a problem. If in open_blob jaybird is trying to >> use p_resp_blob_id (which is actually garbage), wrong assumption is >> sooner of all too delicate word here :) This looks more like a bug. > As nothing is done with the value after opening, it doesn't actually > introduce a bug; this piece of code has been there for over 10 years, so > I'd expect someone to have triggered it already ;), that or it is a bug > that has side effects that are too subtle to notice. > Yes, certainly reopening already opened blob is not the often-most operation :) ------------------------------------------------------------------------------ Sponsored by Intel(R) XDK Develop, test and display web and hybrid apps with a single code base. Download it for free now! http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
