Subject | Re: [IBO] Invalid Blob ID's with IBOQuery |
---|---|
Author | pb.software |
Post date | 2012-03-08T21:38:27Z |
Jason,
I every bit aware what each subtype does and what it is used for, been doing this for a very long time. I don't think you understood me.
I am declaring a blob field in firebird as a text blob field because I am going to save large amounts of text in that field. Inside delphi when I create the field, persitent, it is created as a widememo and when you connect a dbmemo to it the invalid blob id happens, text blob field to a db memo with ftwidememo. Now if I change the subtype of the persistent blob field to ftblob as if it was linked to a "binary blob", which it is not, it displays the text perfectly and can be modified. If I try to modify the text on a field declared as ftwidememo linked to a text blob field I get an invalid blob id.
The ftBlob field as far as I can remember works with both subtypes of blobs, to get rid of this invalid blob id error I had to change the field type to ftBlob for text blob fields. If I use ftwidememo it crashes the application, more of Invalid Blob ID ISC error 335544...
Pedro
I every bit aware what each subtype does and what it is used for, been doing this for a very long time. I don't think you understood me.
I am declaring a blob field in firebird as a text blob field because I am going to save large amounts of text in that field. Inside delphi when I create the field, persitent, it is created as a widememo and when you connect a dbmemo to it the invalid blob id happens, text blob field to a db memo with ftwidememo. Now if I change the subtype of the persistent blob field to ftblob as if it was linked to a "binary blob", which it is not, it displays the text perfectly and can be modified. If I try to modify the text on a field declared as ftwidememo linked to a text blob field I get an invalid blob id.
The ftBlob field as far as I can remember works with both subtypes of blobs, to get rid of this invalid blob id error I had to change the field type to ftBlob for text blob fields. If I use ftwidememo it crashes the application, more of Invalid Blob ID ISC error 335544...
Pedro
--- In IBObjects@yahoogroups.com, "IBO Support List" <supportlist@...> wrote:
>
> Sub-type 1 means text.
> Sub-type 0 means binary.
>
> If you wish to store binary data in a blob, do not use sub-type 1. If IBO
> allowed this in the past, it was not intentional on my part.
>
> Jason
>
> -----Original Message-----
> From: IBObjects@yahoogroups.com [mailto:IBObjects@yahoogroups.com] On Behalf
> Of pb.software
> Sent: 08 March 2012 10:12 AM
> To: IBObjects@yahoogroups.com
> Subject: [IBO] Invalid Blob ID's with IBOQuery
>
> There is a problem with the TIBOQuery and blob fields. I have spend two days
> dealing with this problem at all levels until I finally discovered the
> problem.
>
> I dont understand why a blob field declared as "BLOB SUB_TYPE 1 SEGMENT SIZE
> 80 CHARACTER SET NONE COLLATE NONE" is created in IBO as a widememo field.
> It should be created as a TBlobFiled with blobtype of ftwidememo but better
> yet just a plain ftblobtype which can read any blob format.
>
> If I declare a blob field as "BLOB SUB_TYPE 0 SEGMENT SIZE 80" to save
> binary files, pictures, etc. I can still save text in it and display it. I
> have never had problems with a plain ftblob type field. This was not the
> behavior of IBO before, more specific TIBO Class.
>
> The ftwidememo implementation is not very compatible with some components
> which will throw an invalid BLOB ID saving a text memo into a blob field of
> "BLOB SUB_TYPE 1 SEGMENT SIZE 80 CHARACTER SET NONE COLLATE NONE" while as I
> discovered after two days if I change the field type manually or create the
> in code as:
>
> qFilesFILE_COMMENTS := TBlobField.Create(Self);
>
> It works as expected. Can someone shed some light on this and why are
> persistent fields being created as widememo instead of regular ftblob?
>
> Thanks in advance, Pedro.
>