Subject | Re: AW: [firebird-support] Blob Problem |
---|---|
Author | Helen Borrie |
Post date | 2005-02-01T12:13:33Z |
At 12:53 PM 1/02/2005 +0100, you wrote:
string with a blob - they are different types altogether. A "text blob"
just happens to be a blob that the engine will try to recognise as being
text. You can write a BLOB of any size, if your API interface handles it,
insert into atable (id, blobcol)
values(?, ?)
If your interface passes an integer in parameter 0 and a blob in parameter
1, the blob can be any size. If parameter 1 is passed as a string, it must
not exceed 32,565 bytes. Once a "string" hits the server, it is cast as a
varchar before being chopped up into blob segments, that are stored one by
one into a blob. 32565 bytes is the maximum size of a varchar...
./heLen
>HiHe is talking about passing a string to a blob, I believe. Don't confuse a
>
> > You should not try to insert text longer than 32,765 bytes
> > into a blob using a string as input. If IBExpert lets you
> > insert longer strings, then IBExpert has a bug that will
> > cause an overflow exception in the database.
>
>I do not understand this.
>What is blob subtype text then for? If not for long strings?
>How should we handle those?
>I do not want to transform my texts into byte arrays and store those...
string with a blob - they are different types altogether. A "text blob"
just happens to be a blob that the engine will try to recognise as being
text. You can write a BLOB of any size, if your API interface handles it,
insert into atable (id, blobcol)
values(?, ?)
If your interface passes an integer in parameter 0 and a blob in parameter
1, the blob can be any size. If parameter 1 is passed as a string, it must
not exceed 32,565 bytes. Once a "string" hits the server, it is cast as a
varchar before being chopped up into blob segments, that are stored one by
one into a blob. 32565 bytes is the maximum size of a varchar...
./heLen