Subject | Re: [IBO] MON$SQL_TEXT Blob column in MON$STATEMENTS table |
---|---|
Author | Geoff Worboys |
Post date | 2012-04-28T13:39:06Z |
Carlos H. Cantu wrote:
talking about MON$ columns. In all other situations IBO will
only carry temporary blob ids for blobs it has created itself
(and so already has loaded on the client side). I am not
aware of any other case where IBO gets temporary blob-ids
from the server (or we'd have hit this problem before now).
The particular column causing a problem is essentially a
potentially large (several kB), but usually quite small
(what is your average SQL statement size? Maybe < 256b?).
Still, perhaps such auto-load could be yet another session
setting or something - just in case. Note that auto-load or
not auto-load, the situation (now we understand it) is still
able to be placed in the developers control. For example
the developer could using a cursor so that even if auto-load
happened it would be one row at a time.
--
Geoff Worboys
Telesis Computing Pty Ltd
> Not sure if I understood the problem very well, but autoloadingJason will correct me if I am wrong, but AFAIK we are only
> blobs worries me in the case of a C/S connection over internet.
> FB protocol is already very bad in this scenario.
talking about MON$ columns. In all other situations IBO will
only carry temporary blob ids for blobs it has created itself
(and so already has loaded on the client side). I am not
aware of any other case where IBO gets temporary blob-ids
from the server (or we'd have hit this problem before now).
The particular column causing a problem is essentially a
potentially large (several kB), but usually quite small
(what is your average SQL statement size? Maybe < 256b?).
Still, perhaps such auto-load could be yet another session
setting or something - just in case. Note that auto-load or
not auto-load, the situation (now we understand it) is still
able to be placed in the developers control. For example
the developer could using a cursor so that even if auto-load
happened it would be one row at a time.
--
Geoff Worboys
Telesis Computing Pty Ltd