Tim

In DBISAM I've always used the MEMO type for storing unstructured text, graphics, DBISAM tables etc. Is it OK to use the CLOB type for all of these or do I need to split text and the rest into CLOB and BLOB?

Roy Lambert

What is the memo equivalent in Elevate?  Is it a CLOB?

"Roy Lambert" <roy.lambert@skynet.co.uk> wrote in message
news:9BC0ADC3-4A68-4BD0-96F3-F2E89606E9AB@news.elevatesoft.com...
> Tim
>
> In DBISAM I've always used the MEMO type for storing unstructured text,
> graphics, DBISAM tables etc. Is it OK to use the CLOB type for all of
> these or do I need to split text and the rest into CLOB and BLOB?
>
> Roy Lambert

Roy,

Tim will need to verify, but CLOB is text (characters) only, while BLOB is
binary. So yes, you need to split into the relevant LOB (stands for Large
OBject..?)

Fons

"Roy Lambert" <roy.lambert@skynet.co.uk> schreef in bericht
news:9BC0ADC3-4A68-4BD0-96F3-F2E89606E9AB@news.elevatesoft.com...
> Tim
>
> In DBISAM I've always used the MEMO type for storing unstructured text,
> graphics, DBISAM tables etc. Is it OK to use the CLOB type for all of
> these or do I need to split text and the rest into CLOB and BLOB?
>
> Roy Lambert

Fons


In DBISAM it didn't matter wether you used memo or graphic or BLOB. Different names but the same under the bonnet (hood for Americans). I don't know what Tim's done with ElevateDB.

Roy Lambert

Hi Roy,

> In DBISAM it didn't matter wether you used memo or graphic or BLOB.
> Different names but the same under the bonnet (hood for Americans). I
> don't know what Tim's done with ElevateDB.

Either it's because of standard SQL rules he had to have two (almost) the
same types, or there is really something different about them for
optimization purposes. We'll have to wait untill Tim solves this puzzle  

Fons

BTW, I am Dutch, so it's neither bonnet nor hood, but motorkap...

Fons


>BTW, I am Dutch, so it's neither bonnet nor hood, but motorkap...

I love the way that translates into English. I have this vision of changing the kap to match the season - pointy, bright red and with a white pompom on the end.

Roy Lambert

Roy,

<< In DBISAM I've always used the MEMO type for storing unstructured text,
graphics, DBISAM tables etc. Is it OK to use the CLOB type for all of these
or do I need to split text and the rest into CLOB and BLOB? >>

CHARACTER LARGE OBJECT (character string type) and BINARY LARGE OBJECT
(binary string type) are not compatible types, so you need to split it.

The implementation of LOBs in EDB is pretty much according to the SQL
standard specification.

Ole Willy Tuv

Roy,

<<  In DBISAM I've always used the MEMO type for storing unstructured text,
graphics, DBISAM tables etc. Is it OK to use the CLOB type for all of these
or do I need to split text and the rest into CLOB and BLOB? >>

You should use a BLOB for any binary types, especially with looking forward
to Unicode implementations.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


>You should use a BLOB for any binary types, especially with looking forward
>to Unicode implementations.

I'll go Unicode only if dragged there kicking and screaming with no alternative! However, what's one more minor nightmare in the easy conversion from DBISAM to ElevateDB

Roy Lambert

Roy,

<< I'll go Unicode only if dragged there kicking and screaming with no
alternative! However, what's one more minor nightmare in the easy conversion
from DBISAM to ElevateDB >>

There is absolutely no difference whatsoever when using ElevateDB with
Unicode support vs. ElevateDB with ANSI support.   The differences are
completely masked for you by EDB.  You can still continue to use AnsiStrings
everywhere in your application and the Delphi compiler will handle the
conversion back and forth for you.

--
Tim Young
Elevate Software
www.elevatesoft.com