Hi!

I want to realize a local tables as in our DBISAM products (these temp tables created for faster access (process
something) and for decrease network usage).

But I'm confused a little bit, because options are multiplied now.
In the DBISAM product I created a link to user tempdir, and for new local tables I generate uid filename.

But there are many options.

1.) Temporary table.
This is a memory table representation in EDB (except this not placed in memory)?
When the table destroyed? On client destroy?

2.) Memory database.
As I see this DB placed fully in the memory with all things.
I want to ask that this mode have "flushing to disk" capability or it can fullfill the memory if I working with many data
(OM error)?

My experience was that if more processes are ask for new files, sometimes the "Exists" not working and I got error.
So I search for a possibility to handle tables simply, but without memory limitations.

Thanks for your help:
  dd

durumdara

>1.) Temporary table.
>This is a memory table representation in EDB (except this not placed in memory)?
>When the table destroyed? On client destroy?

Its removed either when you delete it, or the app closes normally.

>2.) Memory database.
>As I see this DB placed fully in the memory with all things.
>I want to ask that this mode have "flushing to disk" capability or it can fullfill the memory if I working with many data
>(OM error)?

Depends what you mean by "flushing to disk". They use RAM and swop file, but that's it. There's no option to simply say "save to disk", but you could use the normal SQL process CREATE TABLE AS


Roy Lambert [Team Elevate]

<< 1.) Temporary table.
This is a memory table representation in EDB (except this not placed in
memory)? When the table destroyed? On client destroy? >>

A temporary table is destroyed when the last reference to the database in
which it was created is released.  So, basically on the last
TEDBDatabase.Close for a given physical database.

<< 2.) Memory database.
As I see this DB placed fully in the memory with all things.
I want to ask that this mode have "flushing to disk" capability or it can
fullfill the memory if I working with many data
(OM error)? >>

If there's any chance that you could cause a memory issue with too much
data, then you should just use a temporary table.  Temporary tables are very
fast and you don't have to worry about using too much memory.

--
Tim Young
Elevate Software
www.elevatesoft.com