"Helen Borrie" <helebor@...> wrote in message
news:5.1.0.14.0.20020117233647.03e60ec0@......

>
> You ought to be able to use a blob as an input to a stored procedure. The

InterBase docs say you can't. This is Borland's workaround for a bug in the
re-storage of blob data from stored procedures. I believe the bug was fixed
in Firebird quite long time ago - Claudio, can you confirm?

The bug was specific to blob copying (using insert from select) inside a
stored procedure. It was easy to solve it: open an email, get the code from
Ann, start MSDEV, load the engine's code, paste, save and recompile.
;-)
I'm not aware of an evident bug when passing blob as parameters from
outside, other than the blob should be already a valid one or the operation
doesn't make sense. I don't know why Borland recommended against such
practice. I passed blobs back and forth in procedure parameters in IB4.2,
for example.

C.
--
Claudio Valderrama C. - http://www.cvalde.com - http://www.firebirdSql.org
Independent developer
Owner of the Interbase® WebRing