Subject | Re: Invalid Blob ID when inserting blob? |
---|---|
Author | phil_hhn |
Post date | 2005-08-04T07:13:29Z |
--- In Firebird-Java@yahoogroups.com, "Roman Rokytskyy"
<rrokytskyy@a...> wrote:
do I raise a bug report, or is this problem now resolved in 2.0
anyway?
Cheers
<rrokytskyy@a...> wrote:
> > I never intend to call execute() twice on the same preparedstatement
> > (without clearing parameter(s) if re-using); but in this case -although
> > it's accidental - I'm wondering (only out of curiousity) what'sgoing on
> > internally here? Can someone explain the mechanism?opened for
>
> When you save a blob, a blob with a temporary ID is created and
> write (you cannot read from it, it is like OutputStream). Thistemporary ID
> is used in the INSERT statement. Then, when statement is executed(or on
> commit, I do not remember exactly), temporary ID is converted intopermanent
> one. When you tried to use this temporary ID for the second timeFirebird
> reported simply that ID is wrong, since no temporary blob exists.have
>
> Now, why didn't JayBird complain earlier? That's a bug, you should
> something "Not all parameters were set" or something similar. Pleasefill a
> bug report and I will take care of it before JayBird 2.0 is out.Hi Roman, I've been meaning to follow this up for a long time. Where
>
> Roman
do I raise a bug report, or is this problem now resolved in 2.0
anyway?
Cheers