> Hope that makes thinks clearer.

It did, thank you. I did not notice the stuff displayed in the Tasks
pane, Column Details



> Since EDBManager is simply a Delphi app it has to read the full BLOB
> data to attempt to display the first characters.

You mean the BLOB size, because it is not displaying anything else, it
just shows the BLOB size. I always thought the blob size would be in
the table (.DAT) and the blob content would be in the blob table
(.BLB), perhaps this is not the case for EDB ?


regards
Lucian

> Lucian could just look at the NULL flag to determine

*I* don't have a problem in my app, thank you very much I said a
few times already that I noticed *EDB manager slow paint* and thought
I'd mention in here. Roy cleared that up and now I see what all those
options do.

Even though I was running EDB for many months, well since I got it ...
I never thought to check any of those options before (I usually expect
stuff from the box to run as smooth as posible with its default
options. If users want to see more, let them check those checkboxes ...
I don't think most people care about BLOB size).


That's all
Lucian

Lucian,

> If users want to see more, let them check those checkboxes ...
> I don't think most people care about BLOB size).

In general edb-manager is not an end-user application. It's certainly
designed for developers.

Uli

> In general edb-manager is not an end-user application. It's certainly
> designed for developers.

From Tim's POV ... we all are end-users
Lucian

Lucian,

<< *I* don't have a problem in my app, thank you very much >

Sorry, I phrased that awkwardly.

<< Even though I was running EDB for many months, well since I got it ... I
never thought to check any of those options before (I usually expect
> stuff from the box to run as smooth as posible with its default options.
> If users want to see more, let them check those checkboxes ... I don't
> think most people care about BLOB size). >>

Well, the default DBGrid behavior is to indicate the existence of BLOB data
via a (BLOB) vs. (Blob) textual representation, so we are trying to have the
default mirror what a developer would expect relative to what they would
seen in a VCL application (mainly because the majority of our customers are
VCL developers).

--
Tim Young
Elevate Software
www.elevatesoft.com

Lucian

>> Hope that makes thinks clearer.
>
>It did, thank you. I did not notice the stuff displayed in the Tasks
>pane, Column Details

Good.

>> Since EDBManager is simply a Delphi app it has to read the full BLOB
>> data to attempt to display the first characters.
>
>You mean the BLOB size, because it is not displaying anything else, it
>just shows the BLOB size. I always thought the blob size would be in
>the table (.DAT) and the blob content would be in the blob table
>(.BLB), perhaps this is not the case for EDB ?

I was going to write "Not unless you create a column and store that when you load the blob." but I don't know. It depends on how Tim has implemented blob/clob storage.

Roy Lambert [Team Elevate]

Roy,

<< I was going to write "Not unless you create a column and store that when
you load the blob." but I don't know. It depends on how Tim has implemented
blob/clob storage. >>

The BLOB size is stored in the row, but that's not the problem.  The problem
is that the standard TBlobField component uses a bland "open BLOB, read to
the end of the BLOB stream, close BLOB" procedure to get the BLOB size, and
there's no way for us to change this for normal EDB usage.  However, there
may be a way to get around this specifically in the EDB Manager, so I'll
check on that further.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

> << I was going to write "Not unless you create a column and store that
> when you load the blob." but I don't know. It depends on how Tim has
> implemented blob/clob storage. >>
>
> The BLOB size is stored in the row, but that's not the problem.  The
> problem is that the standard TBlobField component uses a bland "open BLOB,
> read to the end of the BLOB stream, close BLOB" procedure to get the BLOB
> size, and there's no way for us to change this for normal EDB usage.
> However, there may be a way to get around this specifically in the EDB
> Manager, so I'll check on that further.
>

I am not intending to learn the fish to swim, but can BLOB size be changed
without editing and posting it? If not, then, IMHO, there is no reason to
determine BLOB size each time when reading the record.

Iztok Lajovic

I wanted to say 'I am not intending to teach the fish to swim', sorry

Iztok Lajovic

"Iztok Lajovic" <iztok.lajovic@amis.net> je napisal v sporocilo
news:D78C73E9-B512-449B-BA1D-4487A3ED14EB@news.elevatesoft.com ...
> Tim,
>
>> << I was going to write "Not unless you create a column and store that
>> when you load the blob." but I don't know. It depends on how Tim has
>> implemented blob/clob storage. >>
>>
>> The BLOB size is stored in the row, but that's not the problem.  The
>> problem is that the standard TBlobField component uses a bland "open
>> BLOB, read to the end of the BLOB stream, close BLOB" procedure to get
>> the BLOB size, and there's no way for us to change this for normal EDB
>> usage. However, there may be a way to get around this specifically in the
>> EDB Manager, so I'll check on that further.
>>
>
> I am not intending to learn the fish to swim, but can BLOB size be changed
> without editing and posting it? If not, then, IMHO, there is no reason to
> determine BLOB size each time when reading the record.
>
> Iztok Lajovic
>
>
>

Iztok,

<< I am not intending to learn the fish to swim, >>

That's a good saying - I'll have to remember it.  (and no problem, I
know that you meant teach).

<< but can BLOB size be changed without editing and posting it? If not,
then, IMHO, there is no reason to determine BLOB size each time when reading
the record. >>

I understand, but again, we don't control this - it is controlled by the
db.pas unit that comes with Delphi and the common TBlobField functionality.
Internally, EDB only stores a new BLOB size when a BLOB is loaded, modified,
and then saved.

--
Tim Young
Elevate Software
www.elevatesoft.com